# CRM Complaint Escalation Playbook | 121 CRM > Recognise dissatisfaction, stop unsuitable automation and put the issue with a person authorised to resolve it. A fictional home-services customer disputes an invoice and the workflow pauses reminders while accounts investigates. 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. ## Complaint escalation: 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. ### 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. ### Contacts Stores a person or lead with contact details, activity, ownership and related records. **How it works:** Stores or organises supported business data under configured fields, permissions and record rules. **Why a business would use it:** Gives a team one place to understand who a customer is and what has happened. **Limitations:** The platform does not make imported, duplicated or incomplete data accurate without review. **Human responsibility:** A data owner must define the record model and resolve quality, ownership and access exceptions. ## Begin with a valid trigger, enough context and one owner A customer message, survey response or staff record is identified as a potential complaint. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook. ### Trigger A customer message, survey response or staff record is identified as a potential complaint. ### Practical scenario A fictional home-services customer disputes an invoice and the workflow pauses reminders while accounts investigates. ### Accountable owner Name the person or queue that accepts the work, monitors exceptions and can stop the sequence. ## Run the complaint escalation 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. Acknowledge and preserve context Record the customer’s words, channel, related work and immediate need without defensive rewriting. ### 2. Stop conflicting automation Pause marketing, review requests and collection messages that could worsen the situation. ### 3. Assign the right owner Route by risk, service and authority with a clear response expectation. ### 4. Investigate fairly Gather relevant records and give the customer a human route for questions. ### 5. Resolve and learn Record outcome, redress where authorised and any process improvement. ## 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. ### Safety, legal or regulatory risk Escalate immediately under the approved specialist process. ### Vulnerable customer Adapt communication and pace through trained human judgement. ### Multiple linked issues Keep one accountable complaint owner while assigning supporting actions. ## 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. ### Time to human ownership Measure acceptance by an authorised person. ### Conflicting messages after complaint Target zero and investigate every occurrence. ### Root causes and corrective actions Review themes without minimising individual experiences. ## Frequently asked questions ### When should the complaint escalation playbook start? A customer message, survey response or staff record is identified as a potential complaint. Confirm the record is eligible and that a named owner or monitored queue is available before allowing customer-facing action. ### Which channels should the complaint escalation 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 complaint escalation 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 safety, legal or regulatory risk, vulnerable customer, multiple linked issues. ### How should we judge whether complaint escalation works? Review time to human ownership, conflicting messages after complaint, root causes and corrective actions. 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/team-inbox](https://121.direct/crm/features/team-inbox) - [/crm/security-data](https://121.direct/crm/security-data) - [/crm/features/invoicing](https://121.direct/crm/features/invoicing) - [/crm/playbooks/abandoned-form](https://121.direct/crm/playbooks/abandoned-form) This Markdown alternative contains public product information only. It provides no access to CRM accounts, records, credentials or payment execution.