Skip to CRM content
121 CRM

121 CRM playbook · Complaint escalation

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.

Subscribe to 121 CRMSeller, billing and cancellationRead the automation guide

Fictional workflow demonstration

Follow complaint escalation 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

Keep customer messages together

AR
OverviewContactsInboxPipelineAutomation

Keep customer messages together

See the message, customer context and responsible owner in the same working view.

Bramble Studio

Jamie Clarke · Email

Contact confirmed

Could Thursday morning work for a short discovery call?

09:54

Yes — 11:30 is available. I can send the appointment details once the scope is confirmed.

10:02

Thursday morning would work well. Thank you.

10:24

Write a reply…
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

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 use it
Helps a team see the customer history and coordinate replies from one working view.
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

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 03

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.
Capability 04

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 use it
Gives a team one place to understand who a customer is and what has happened.
Plan for
The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns
A data owner must define the record model and resolve quality, ownership and access exceptions.

Entry criteria

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.

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

Close the loop

5. Resolve and learn

Record outcome, redress where authorised and any process improvement.

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

24

Illustrative

Owned

21

Illustrative

Due

4

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

Safety, legal or regulatory risk

Escalate immediately under the approved specialist process.

Human review

Vulnerable customer

Adapt communication and pace through trained human judgement.

Human review

Multiple linked issues

Keep one accountable complaint owner while assigning supporting actions.

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.

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.

Questions about this page

Useful answers, without the sales fog.

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

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

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

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

Read all CRM questions

Continue the journey

Team inboxSecurity and dataInvoicingAbandoned-form 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 CRMSeller, billing and cancellationCompare pricing

121 CRM

Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.