# Appointment reminder workflow — fictional example

Status: template, not a live implementation or no-show study.

## Script
Identify the business using its approved disclosure. Verify the intended person without exposing appointment details to another person. Read the current saved date/time only after the required checks. Ask whether they want to confirm attendance, cancel, reschedule or speak to staff. Confirm a change only after the booking system saves it.

## States
Attendance confirmed updates the existing event. Cancellation requires a saved cancellation. Reschedule must verify the new slot and preserve the original if the change fails. Callback confirmation requires a saved task. Declined and wrong person stop the approved automated flow.

## Acceptance cases
- Wrong person: no appointment details disclosed.
- Already cancelled: no reminder based on stale data.
- Ambiguous time: clarification before update.
- Duplicate reminder: no duplicate event.
- Slot conflict: no false reschedule confirmation.
- Timeout after write: reconcile the event identity.
- Staff unavailable: honest fallback.

For each case record reference timestamp, event ID, expected action, observed action, system proof and reviewer. No customer result is implied.