# Missed-Call Follow-Up Playbook | 121 CRM > 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. ## Missed-call follow-up: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### 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 a business would use it:** Acknowledges an enquiry quickly while leaving the team responsible for proper follow-up. **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. ### 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 a business would use it:** Makes call activity part of the customer history rather than a separate phone log. **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. ### 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. ## 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. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop 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. ### 5. Close the loop Record contact, booking or a clear reason the enquiry was not progressed. ## 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. ### Emergency wording Direct potential emergencies to the appropriate public or specialist route; do not diagnose by text. ### Repeated call events Prevent duplicate messages from forwarding, voicemail or several attempts. ### No SMS route Use the agreed voicemail or manual call-back process. ## 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. ## Frequently asked questions ### 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. ### 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. ### 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. ### 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. ## 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/missed-call-text-back](https://121.direct/crm/features/missed-call-text-back) - [/crm/features/call-tracking](https://121.direct/crm/features/call-tracking) - [/crm/features/sms-messaging](https://121.direct/crm/features/sms-messaging) - [/crm/playbooks/quote-follow-up](https://121.direct/crm/playbooks/quote-follow-up) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.