# Appointment reminders vs appointment rescheduling: choosing the right workflow

Compare appointment reminders and appointment rescheduling using the same source packet, distinct useful outputs, and a reviewable Righthand brief.

By Righthand Team · 2026-10-13

Source: https://www.righthand.ai/blog/appointment-reminders-vs-appointment-rescheduling

## Quick answer

Use appointment reminders to prepare accurate information about an existing booking. Use rescheduling to prepare a change request and eligible alternatives while preserving the current booking until a change is confirmed.

The practical test is the question your reviewer needs answered. Start both workflows from the same dated input packet, then judge the usefulness of their different outputs. Righthand can help prepare either draft from owner-provided records or an approved read view; the reviewer retains authority over decisions and external actions.

## Compare the same input

Use this shared packet: One service calendar snapshot with appointment IDs, current start times and zones, service durations, staff, customer preferences, approved availability, and owner-supplied change rules. Keep stable identifiers, source links, and a cutoff so another person can reproduce the comparison. Missing information stays explicitly unknown rather than becoming an invented fact.

| Workflow | Useful output | Review owner |
| --- | --- | --- |
| Appointment reminders | Reminder drafts tied to current booking details and allowed contact preferences | The scheduling owner |
| Appointment rescheduling | Change-review packet with requested move, eligible options, conflicts, and confirmation needs | The scheduling owner |

Acuity documents separate events for appointments scheduled, rescheduled, and canceled. These states should remain distinct in a booking workflow. The [official Acuity appointment events reference](https://developers.acuityscheduling.com/docs/webhooks) supports this specific distinction; the rest of the example is a suggested operating practice, not a universal provider feature or requirement.

## Illustrative worked comparison

Illustratively, a customer requests a Tuesday appointment move to Thursday. The reminder draft still reflects the existing Tuesday booking. Rescheduling proposes verified Thursday options and records the request, but the Tuesday booking remains current until an authorized change and its result are confirmed.

Keep assumptions beside the conclusions they affect. The reviewer should see which decision each draft supports without reopening every source.

## Delegation brief for both workflows

> Use only the approved input packet described above, with its recorded cutoff. First, prepare reminder drafts for existing bookings, preserving appointment IDs and the current source time zones. Separately, prepare rescheduling options only from approved availability and change rules, keeping requested changes separate from confirmed changes. Use America/Los_Angeles for the review deadline and preserve the original dates and time zones. Run this comparison once and return both drafts in this conversation by Friday at 3 PM Pacific for The scheduling owner to review. Include source IDs, missing inputs, assumptions, and a next step with an owner. Do not send messages, modify records, make purchases, or approve decisions. If access is unavailable or the packet contradicts itself, report that limitation before completing the affected section.

## Check the result

Re-read the appointment before any later authorized send or change. Verify duration, staff eligibility, time zone, and conflict checks; a suggested slot is not a reserved slot.

A completed draft is evidence of preparation, not evidence that its recommended action occurred. The owner should accept or revise the outputs before any separate execution request. For a recurring version, specify the next input window, review deadline, and destination rather than reusing an old snapshot silently.

## Failure and recovery

A stale snapshot can show a slot that another customer has taken. Mark the options provisional, refresh the approved calendar view, and prepare new options rather than promising the old slot.

This example concerns administrative service bookings. Do not give medical guidance, contact customers, move appointments, waive fees, or override booking policies without explicit approval.

## FAQ

### Should I use both workflows?

Use both when the outputs answer distinct questions that are currently useful. Start with the smaller deliverable when review capacity is limited; preserve the shared source packet so the second can be prepared later without guessing.

### Does delegation require a native integration?

An approved export or owner-prepared packet can support the first comparison. A live read or later write requires verified connection tools and the appropriate permission; a catalog entry alone does not establish either.

Use [Righthand Docs](https://docs.righthand.ai) for delegation and permission guidance, check available [integrations](/integrations), and review [Pricing](/pricing) before expanding the task.