# Appointment No-Show Follow-Up Playbook | 121 CRM > Check what happened, offer an appropriate next step and learn from missed appointments without shaming the customer. A fictional training provider checks attendance before contacting Amir about a missed session. 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 no-show: 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. ### Tasks Creates assigned, dated and optionally recurring actions against contacts or opportunities. **How it works:** Tracks a potential deal, stage, owner or task using configured pipeline and record rules. **Why a business would use it:** Turns the next step into owned work instead of leaving it inside notes or inboxes. **Limitations:** Pipeline position is only reliable when users and workflows update it consistently. **Human responsibility:** A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status. ### 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 booked appointment is marked as not attended after staff verification. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A booked appointment is marked as not attended after staff verification. ### Practical scenario A fictional training provider checks attendance before contacting Amir about a missed session. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the appointment no-show 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 status Make sure the person did not attend under another name, cancel through another channel or encounter a service error. ### 2. Pause scheduled messages Stop reminders or post-appointment communications that no longer fit. ### 3. Make a respectful contact Ask whether the customer wants to rearrange and provide the relevant policy. ### 4. Record the reason carefully Use neutral categories and avoid assumptions about motivation. ### 5. Review patterns Look for timing, access, communication or service-design problems. ## 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. ### Business error Apologise and correct the record before any customer action. ### Repeated non-attendance Apply the approved policy through a person, considering vulnerability and context. ### No contact permission Create a manual review or close according to policy. ## 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. ### Verified no-show rate Use a consistent denominator and separate business cancellations. ### Rebooking after appropriate contact Review without treating rebooking as the only good outcome. ### Reasons within business control Prioritise fixes to access, reminders and scheduling. ## Frequently asked questions ### When should the appointment no-show playbook start? A booked appointment is marked as not attended after staff verification. 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 no-show 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 no-show 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 business error, repeated non-attendance, no contact permission. ### How should we judge whether appointment no-show works? Review verified no-show rate, rebooking after appropriate contact, reasons within business control. 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/round-robin-booking](https://121.direct/crm/features/round-robin-booking) - [/crm/guides/appointment-reminders](https://121.direct/crm/guides/appointment-reminders) - [/crm/playbooks/review-request](https://121.direct/crm/playbooks/review-request) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.