# Appointment Confirmation Playbook | 121 CRM > Confirm a genuine booking, set expectations and give the customer a clear change route. A fictional survey practice confirms Mia’s visit with time, location, preparation and rescheduling details. This playbook turns that kind of situation into an owned sequence with explicit stop points, exceptions and measures. Use only channels, data and capabilities approved for your setup. ## Appointment confirmation: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Appointments Stores scheduled customer interactions with time, attendee, owner, status and related contact context. **How it works:** Applies configured availability, booking rules and connected-calendar settings to eligible appointments. **Why a business would use it:** Makes booked work visible alongside the customer conversation and follow-up. **Limitations:** Sync, meeting-link and resource behaviour varies by calendar type and external provider. **Human responsibility:** Staff must handle exceptions, incorrect availability and bookings that need judgement. ### Appointment reminders Uses configured notifications or workflows around booking, rescheduling, cancellation and attendance events. **How it works:** Applies configured availability, booking rules and connected-calendar settings to eligible appointments. **Why a business would use it:** Keeps customers and staff informed without relying on a person to send each reminder manually. **Limitations:** Sync, meeting-link and resource behaviour varies by calendar type and external provider. **Human responsibility:** Staff must handle exceptions, incorrect availability and bookings that need judgement. ### Email conversations Sends and receives supported email messages against the customer conversation and contact record. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Keeps email context visible to authorised colleagues rather than one private mailbox. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### SMS and MMS Uses a configured phone provider and compliant number to send and receive supported text and media messages. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Supports quick customer updates while preserving the thread in the CRM. **Limitations:** Delivery, message types, geographic coverage, approval and charges vary by channel and provider. **Human responsibility:** A person must own sensitive conversations, failed delivery and any situation outside the approved script. ### Goals and exits Moves or removes records when the configured outcome or stop condition has been met. **How it works:** Runs an ordered sequence only after its configured trigger and conditions are met. **Why a business would use it:** Helps avoid continuing follow-up after the customer has already acted. **Limitations:** Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service. **Human responsibility:** A process owner must approve, test, monitor and pause or correct faulty automation. ## Begin with a valid trigger, enough context and one owner A booking reaches the agreed confirmed status. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A booking reaches the agreed confirmed status. ### Practical scenario A fictional survey practice confirms Mia’s visit with time, location, preparation and rescheduling details. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the appointment confirmation playbook step by step Each step should leave evidence a colleague can understand. Timing and channels should follow the customer context rather than a generic high-pressure cadence. ### 1. Verify the booking Check customer, service, owner, time zone, location and status before communicating. ### 2. Send the confirmation Use the chosen channel to state what is booked and what happens next. ### 3. Provide change options Explain how to reschedule, cancel or ask a question. ### 4. Schedule proportionate reminders Use timing appropriate to the appointment and customer preference. ### 5. Stop old messages Cancel pending communications when the booking changes. ## Stop the normal route when the facts change Exceptions are part of the process, not failures to be hidden. Route them to a person with the authority and context to decide what happens next. ### Missing contact route Create a staff task rather than silently assuming confirmation. ### Resource or host conflict Hold communication until a person resolves availability. ### Sensitive appointment Use approved wording and restrict unnecessary detail. ## Measure whether the work became safer and clearer Use measures that reveal ownership, service quality and control. Counts of messages, tasks or workflow runs are supporting signals, not proof of customer value. ### Confirmed bookings with successful communication Review failures as work, not just a percentage. ### Changes handled before the slot Track whether the route helps customers act in time. ### Wrong-time or duplicate messages Treat any occurrence as a workflow defect. ## Frequently asked questions ### When should the appointment confirmation playbook start? A booking reaches the agreed confirmed status. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the appointment confirmation playbook use? Use only configured channels that suit the purpose, customer preference and consent position. Give each channel a distinct role and check provider availability and usage charges before launch. ### When should appointment confirmation automation stop? Stop when the purpose is complete, the customer responds or opts out, the data conflicts, or an exception needs judgement. In this playbook, pay particular attention to missing contact route, resource or host conflict, sensitive appointment. ### How should we judge whether appointment confirmation works? Review confirmed bookings with successful communication, changes handled before the slot, wrong-time or duplicate messages. Combine the numbers with sampled records and customer context; do not treat activity volume as a business outcome. ## Related CRM pages - [/crm/guides](https://121.direct/crm/guides) - [/crm/guides/customer-follow-up-automation](https://121.direct/crm/guides/customer-follow-up-automation) - [/crm/features/appointments](https://121.direct/crm/features/appointments) - [/crm/features/calendar-management](https://121.direct/crm/features/calendar-management) - [/crm/guides/appointment-reminders](https://121.direct/crm/guides/appointment-reminders) - [/crm/playbooks/appointment-no-show](https://121.direct/crm/playbooks/appointment-no-show) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.