121 CRM playbook · Appointment no-show

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.

Subscribe to 121 CRM Seller, billing and cancellationRead the automation guide

Customer Thread

Appointment no-show: the working sequence

Illustrative example

Verify the status
Make a respectful contact
Review patterns
Human review

Verify the status
Make sure the person did not attend under another name, cancel through another channel or encounter a service error.
Make a respectful contact
Ask whether the customer wants to rearrange and provide the relevant policy.
Review patterns
Look for timing, access, communication or service-design problems.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow appointment no-show from start to next action.

The coded interface shows an example sequence using fictional data and does not expose a live CRM account.

121

Northstar Joinery

Fictional

Make appointments easier to organise

OverviewContactsCalendarAppointmentsAutomation

Make appointments easier to organise

Coordinate availability, appointment status and the follow-up owner.

Mon

10:00

Discovery call

Rowan & Co

Tue

09:30

Site survey

Oakfield Homes

15:00

Drawing review

Marlow Works

Wed

Thu

11:30

Discovery call

Bramble Studio

Fri

13:00

Installation check

Field & Form

Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

What supports the playbook

See what the CRM can coordinate — and where your team steps in.

The CRM can organise the sequence, but the business still sets the rules, checks consent and handles the moments that need human judgement.

Capability 01

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 use it: Makes booked work visible alongside the customer conversation and follow-up.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 02

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 use it: Keeps customers and staff informed without relying on a person to send each reminder manually.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

Capability 03

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 use it: Turns the next step into owned work instead of leaving it inside notes or inboxes.
Plan for: Pipeline position is only reliable when users and workflows update it consistently.
Your team owns: A responsible owner must qualify the deal, choose next actions and resolve stale or disputed status.

Capability 04

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 use it: Helps avoid continuing follow-up after the customer has already acted.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Entry criteria

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.

Human decision retained

Accountable owner

Name the person or queue that accepts the work, monitors exceptions and can stop the sequence.

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.

Close the loop

5. Review patterns

Look for timing, access, communication or service-design problems.

Owner, timing and exception

Make the operational state easy to review

The supporting view keeps the next action and human checkpoint visible around the automated steps.

121 CRM · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314

11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Exception paths

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.

Human review

Business error

Apologise and correct the record before any customer action.

Human review

Repeated non-attendance

Apply the approved policy through a person, considering vulnerability and context.

Human review

No contact permission

Create a manual review or close according to policy.

Operational review

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.

Questions about this page

Useful answers, without the sales fog.

1. 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.

2. 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.

3. 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.

4. 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.

Read all CRM questions

Continue the journey

Appointments Round-robin booking Appointment reminders Review request

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing