# Appointment reminder acceptance worksheet
RevSet Labs | October 5, 2026
Guide: https://revsetlabs.com/resources/appointment-booking/
Use controlled test records. Do not include customer personal data in a public report.

For each case record: event identifier, event version, appointment type, full local date/time, named zone, confirmed calendar state, expected message, actual message, scheduled send time, responsible owner, result, correction and retest.

1. Service visit: message shows the property-local arrival window, not an exact arrival promise.
2. Traveling owner: display the property's zone explicitly; verify any second-zone equivalent.
3. Callback: message states phone call and does not imply a technician visit.
4. Seasonal clock change: test appointments before and after transition with the named zone.
5. Ambiguous or missing local time: reject ambiguity and obtain a valid confirmed slot.
6. Short-notice booking: avoid sending an overdue reminder immediately after confirmation.
7. Reschedule requested: pause stale reminders; create an owned scheduling task.
8. Reschedule confirmed: one current appointment; old messages cancelled; new confirmation accurate.
9. Cancellation: cancel pending reminders and preserve the historical outcome.
10. Dispatch delay: name an owner for the update; do not invent a revised arrival estimate.
11. Delivery failure: visible exception, owned recovery, no assumption the customer saw the message.
12. Customer reply or opt-out: respect preferences and route the reply; prevent inappropriate queued messages.
13. Calendar unavailable: no booking confirmation without a verified reservation.
14. Duplicate event notification: do not send the same confirmation twice.

Release only after expected calendar state, message and owner agree. Retain failures, not just successful examples. Review unresolved replies daily under a named owner.

Track: incorrect-time messages; stale reminders; unresolved scheduling requests; delivery failures; appointments due; attendance recorded; unknown outcomes. A sent text is not evidence of attendance or revenue.