121 CRM playbook · Missed-call follow-up

Acknowledge an unanswered call, gather safe context and create a human-owned call-back.

A fictional plumbing firm misses Lee’s call during a job and sends a neutral acknowledgement. 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

Missed-call follow-up: the working sequence

Illustrative example

Check eligibility
Create the call-back
Close the loop
Human review

Check eligibility
Confirm the outcome was genuinely missed and no colleague has already handled the caller.
Create the call-back
Assign an owner and due time based on staffed hours rather than promising instant service.
Close the loop
Record contact, booking or a clear reason the enquiry was not progressed.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow missed-call follow-up 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

Follow up consistently, with people in control

OverviewContactsInboxPipelineAutomation

Follow up consistently, with people in control

Build the sequence, review each decision and test an exception before activation.

Draft v0.4

This example stays on this page and does not send messages or change CRM data.

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

Missed-call text back

Can send a configured text response after a qualifying missed call when the number and workflow are eligible.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Acknowledges an enquiry quickly while leaving the team responsible for proper follow-up.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 02

Call handling

Supports configured inbound and outbound calling, routing, voicemail and related call records.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Makes call activity part of the customer history rather than a separate phone log.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 03

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 use it: Supports quick customer updates while preserving the thread in the CRM.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 04

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.

Entry criteria

Begin with a valid trigger, enough context and one owner

A configured business number records an eligible missed inbound call. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A configured business number records an eligible missed inbound call.

Practical scenario

A fictional plumbing firm misses Lee’s call during a job and sends a neutral acknowledgement.

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 missed-call follow-up 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. Check eligibility

Confirm the outcome was genuinely missed and no colleague has already handled the caller.

2. Send a neutral text

Identify the business, acknowledge the missed call and invite limited, non-sensitive context.

3. Create the call-back

Assign an owner and due time based on staffed hours rather than promising instant service.

4. Review the reply

A person assesses urgency, service fit and the safest next step.

Close the loop

5. Close the loop

Record contact, booking or a clear reason the enquiry was not progressed.

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

Emergency wording

Direct potential emergencies to the appropriate public or specialist route; do not diagnose by text.

Human review

Repeated call events

Prevent duplicate messages from forwarding, voicemail or several attempts.

Human review

No SMS route

Use the agreed voicemail or manual call-back process.

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.

Eligible missed calls acknowledged

Check genuine eligible calls rather than raw telephone events.

Call-backs completed within the stated window

Compare actual human response with the expectation given.

Duplicate or inappropriate texts

Treat these as quality failures and fix the trigger.

Questions about this page

Useful answers, without the sales fog.

1. When should the missed-call follow-up playbook start?

A configured business number records an eligible missed inbound call. 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 missed-call follow-up 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 missed-call follow-up 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 emergency wording, repeated call events, no sms route.

4. How should we judge whether missed-call follow-up works?

Review eligible missed calls acknowledged, call-backs completed within the stated window, duplicate or inappropriate texts. 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

Missed-call text back Call tracking SMS messaging Quote follow-up

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