Appointment Confirmation & Reminder Sequence

Id

RLR-29

Link

5

Link Name

Booking + Handoff

Role

workflow

Loop Step

Repair

Purpose

Increase attendance by making every scheduled appointment clear, confirmed, easy to prepare for, and easy to reschedule — through a configurable confirmation and reminder sequence that never double-messages the prospect across systems.

Consolidation Note

This resource absorbs and materially improves the prior public 'Appointment Confirmation Script' (a two-message confirmation + 24-hour reminder shown in the Lead-to-Appointment Rescue Kit). That narrow two-message asset becomes the immediate-confirmation and 24-hour-reminder touches inside this fuller, configurable sequence. The public Rescue Kit page remains the outward-facing explainer and is not modified.

Governing Principle

A booked appointment is not a confirmed appointment. Confirmation and reminders convert a reserved time into an attended one by making the appointment unmistakable, prepared-for, and easy to reschedule — without spamming the prospect or contradicting one system with another.

Configurability

Note

Do not require every business to use every touch. Each touch is independently enable/disable and its timing is editable. The operator selects the touches that fit the appointment type, channel permissions, and lead value.

Every Touch Optional Except Immediate Confirmation

true

Editable Timing

true

Editable Channel Selection

true

Touch Schema

Fields

touch_id; timing; channel; objective; message; owner; required_data; stop_condition

Sequence

Confirmation Content

Note

Include where relevant; omit fields that do not apply to the appointment type.

Fields

prospect_name; appointment_type; date; time; timezone; assigned_person_or_team; location_or_meeting_method; preparation_requirements; contact_information; reschedule_instructions

Reschedule Path

Required

true

Note

Every confirmation and reminder must offer an easy reschedule and cancel path. A prospect who can reschedule in one step is retained; a prospect forced to no-show to escape a bad time is lost.

Deduplication Rules

Note

Prevent duplicate or contradictory reminders across multiple systems.

Rules

designate one system of record for reminder sending per appointment; suppress a reminder if the prospect has already confirmed for that touch; suppress all further reminders on cancel or reschedule and restart the sequence for the new time; never send two systems' reminders for the same touch; reconcile against the system of record; honor opt-out and quiet-hours before any touch

Reminder QAChecklist

• Immediate confirmation fires within seconds of booking with correct date/time/timezone.
• Calendar invite lands with the correct owner and location/method.
• Each enabled reminder fires at its configured time and only once.
• Timezone is correct for the prospect, not the business.
• Reschedule and cancel links work and update the appointment record.
• A confirm reply (e.g. 'C'/'YES') is recorded and suppresses redundant reminders.
• Cancel or reschedule suppresses remaining reminders and restarts the sequence for the new time.
• No duplicate reminders arrive from a second system.
• Opt-out and quiet-hours are honored on every touch.
• Preparation instructions and contact information are present where the appointment type requires them.

Handoff From Link4

Note

Consumes Link 4 output (owner, prior context) and does not re-run follow-up logic.

Consumes

owner; prior_follow_up_context

Handoff To Link6

Note

Confirmation/attendance signals feed Link 6 without authoring Link 6 content.

Exposes

booked_status; booked_date; assigned_owner; reschedule_status

Compliance Guardrail

Every touch respects opt-outs, do-not-contact requests, channel permissions, quiet-hours rules, and the business's approved communication policy and consent controls. The sequence never invents legal requirements or bypasses provider restrictions; jurisdiction- and industry-specific rules are applied by the operator.

What To Measure

Whether confirmed, well-reminded appointments actually raise attendance — tracked via confirmation coverage, reminder coverage, show rate, no-show rate, and reschedule rate (RLR-27 metrics).

Data Required

Per appointment: which touches were enabled and fired, confirm responses, reschedule/cancel events, and the final showed/no-show outcome.

How To Interpret

Rising confirmation and reminder coverage with a rising show rate indicates the sequence is working. A high reschedule rate is not failure — reschedules retain opportunities that would otherwise be no-shows. Duplicate-message complaints indicate a deduplication/system-of-record problem.

Action That Follows

Tune which touches are enabled per appointment type and channel, fix any touch that under-fires, and route actual no-shows into the No-Show Rescue Playbook (RLR-30).

Owner

Automation owns the scheduled touches; the assigned appointment owner (per RLR-32) owns optional human confirmation and any exception handling.

How To Implement

Configure the enabled touches and timings in the booking/reminder system, set one system of record, map the confirmation content fields, and wire cancel/reschedule to suppress-and-restart.

How To Test

Book a test appointment and walk the full sequence end to end: confirm immediate confirmation, calendar invite, each reminder, a confirm reply, a reschedule (sequence restarts), and a cancel (sequence stops) — verifying no duplicates and correct timezone.

When To Remeasure

Re-measure confirmation coverage, reminder coverage, and show rate 14 and 30 days after rollout via RLR-27.

How To Know It Improved

The sequence helped only when re-measured show rate rises and no-show rate falls on real appointments — not because reminders were switched on.