The playbook
Appointment Reminders: Metrics and Measurement
Measure appointment reminders by defining attended appointments from confirmed bookings precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Pull time, location, and preparation from the current booking record. Test what happens after rescheduling or cancellation. A reminder should reduce uncertainty and provide a usable change path, rather than make the recipient reply to an unmonitored address.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | attended appointments from confirmed bookings |
| Unit | What one customer or opportunity record or completed outcome represents |
| Included records | The scope identified by booking ID and time zone |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | sales manager |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as confirm time zone location and preparation details. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For appointment reminders, explain the condition before applying that calculation. If the question is whether the team can stop reminders when the appointment changes, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If time zone changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying booking ID records are complete.
- Look for this known failure: sending reminders with outdated times after a reschedule.
- Verify that the process still includes: offer a straightforward way to reschedule or cancel.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, use the current booking record as the message source. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about attended appointments from confirmed bookings, not a favorable-looking number.
Make communication preferences and conversation status visible to the responsible owner. An automated action should not continue blindly after a meaningful reply or a request to stop. Route uncertain cases to a person.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now