# Multi-Channel Customer Follow-Up Playbook | 121 CRM > Coordinate email, SMS, telephone and other approved channels so the customer receives a coherent conversation, not repeated chasing. A fictional training provider emails course details, then uses one SMS reminder only where requested. 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. ## Multi-channel follow-up: the working sequence Illustrative playbook — names, organisations and activity are fictional. ## Capabilities explained ### Conversations inbox Brings supported connected message threads into a shared operational inbox. **How it works:** Handles an eligible customer interaction through a configured inbox, number or connected channel. **Why a business would use it:** Helps a team see the customer history and coordinate replies from one working view. **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. ### 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. ### 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. ### 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 live customer task needs follow-up and the appropriate channels and preferences are known. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A live customer task needs follow-up and the appropriate channels and preferences are known. ### Practical scenario A fictional training provider emails course details, then uses one SMS reminder only where requested. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the multi-channel 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. Choose a primary channel Use the customer’s preference and the nature of the information. ### 2. Give each channel a role Let one explain, another remind and a person handle questions. ### 3. Check recent activity Stop or adapt when the customer replies elsewhere. ### 4. Limit cadence Set a clear attempt count, spacing and end date. ### 5. Keep one owner Make a person accountable for the whole conversation across channels. ## 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. ### Conflicting preferences Use the most restrictive current choice and obtain clarification. ### Reply on another channel Pause queued messages and respond in the thread the customer chose. ### Sensitive matter Move to the approved secure or specialist route. ## 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. ### Customers receiving duplicate or contradictory messages Target zero. ### Live follow-ups with a named owner Check the cross-channel view. ### Responses honoured before next send Review workflow timing and sync delays. ## Frequently asked questions ### When should the multi-channel follow-up playbook start? A live customer task needs follow-up and the appropriate channels and preferences are known. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the multi-channel 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 multi-channel 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 conflicting preferences, reply on another channel, sensitive matter. ### How should we judge whether multi-channel follow-up works? Review customers receiving duplicate or contradictory messages, live follow-ups with a named owner, responses honoured before next send. 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/conversations](https://121.direct/crm/features/conversations) - [/crm/features/campaign-management](https://121.direct/crm/features/campaign-management) - [/crm/playbooks/human-handover](https://121.direct/crm/playbooks/human-handover) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.