How to Track WhatsApp Appointment Reminder Delivery

To track a WhatsApp appointment reminder, save the message ID when you send it and use status updates to see whether delivery was reported. Record the customer’s confirmation separately. If delivery is still unclear near the appointment, send the booking to a staff follow-up queue.

Keep reminder delivery separate from appointment confirmation

A status webhook is a notification your integration receives when WhatsApp reports a change to an outgoing message. Store the message ID returned by the API against the appointment and match subsequent status updates to that ID. Keep the appointment’s own state, such as booked, confirmed or rescheduled, in a separate field. Meta’s message status documentation.

  • Accepted: Your send request returned a message ID. Record it and wait for a status update.
  • Sent: WhatsApp reported sending the message. Keep tracking delivery.
  • Delivered: WhatsApp reported delivery. Continue to show the appointment as awaiting a reply if your workflow requires confirmation.
  • Read: A read event was reported. A confirmation still requires an explicit customer action.
  • Failed: Review the reported error details where provided and decide whether staff need to intervene.

For a reminder with a confirmation button, process the customer’s reply separately from status updates. Meta’s interactive template documentation.

Set up one clear follow-up workflow

  1. Save each attempt. Store the appointment reference, scheduled appointment time, send time, message ID and latest known status. If you send another reminder, keep its message ID separate so the previous attempt’s late events do not overwrite it.
  2. Handle repeated and late events. Make processing the same status event twice harmless. Keep event timestamps and prevent an older sent event from rolling a delivered record back. If you receive conflicting states, flag the attempt for review.
  3. Choose a cut-off tied to the appointment. For example, a Mysore equipment service centre could review unresolved reminders two hours before an engineer is due to leave. Label reminders with no useful status by the cut-off as “Delivery unconfirmed”. On a quiet test day, verify that a missing webhook creates a staff task without immediately sending another message.
  4. Give the task an owner. Include the booking reference, appointment time, latest status and any actionable error. Ask staff to check whether the booking has been cancelled or changed before using the customer’s permitted follow-up channel.

A Bengaluru training centre could follow the same pattern for scheduled orientation calls. Both are hypothetical examples. Set the cut-off around your team’s operating hours and the time it takes to act.

Test the workflow before using it on real bookings

Use a test booking and a phone your team controls. Send a reminder, record the returned ID, and compare the status events with what appears on the phone. If you use a confirmation button, press it and check that the booking state changes only when the reply is processed.

Then simulate a failed status, a repeated event, an event arriving late and a missing update. Cancel a test appointment shortly before the cut-off and confirm that an old reminder cannot create a fresh follow-up task. Keep customer phone numbers and appointment details out of shared screenshots and unnecessary logs.

Frequently asked questions

Should we resend if there is no delivery update?

Check the message ID, webhook logs and appointment status first. A missing update may reflect a reporting problem. Resending immediately can create duplicate reminders.

What if the dashboard says delivered but the customer has not confirmed?

Keep the reminder marked delivered and the booking marked as awaiting confirmation. Use the agreed follow-up process if the booking needs an explicit reply.

How do we report reminder delivery?

Count unique reminder attempts by message ID. Report delivered, failed and unresolved attempts separately. Track customer confirmations by appointment so retries do not inflate the booking count.