121 CRM playbook · Workflow exception handling

Make failed, paused and unexpected automation visible, owned and safe to resolve.

A fictional invoice reminder fails because the contact has no eligible channel and creates an accounts task. 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

Workflow exception handling: the working sequence

Illustrative example

Contain the effect
Assign an owner
Correct and retest
Human review

Contain the effect
Stop repeat or conflicting actions where the exception could harm the customer.
Assign an owner
Route technical, data or customer exceptions to the right accountable person.
Correct and retest
Fix the rule or data, test representative paths and document restart decisions.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow workflow exception handling 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

Testing and execution logs

Supports test runs and operational evidence used to diagnose why a record did or did not follow a path.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Gives a human a way to verify automation and investigate exceptions.
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 02

Conditions and branches

Routes a record through different configured steps when relevant data or events differ.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Lets one process handle common variations without pretending every customer is the same.
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 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

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 workflow log, customer response or monitoring rule identifies an exception. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A workflow log, customer response or monitoring rule identifies an exception.

Practical scenario

A fictional invoice reminder fails because the contact has no eligible channel and creates an accounts task.

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 workflow exception handling 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. Contain the effect

Stop repeat or conflicting actions where the exception could harm the customer.

2. Capture the evidence

Record workflow, record, step, time and safe diagnostic context without exposing credentials.

3. Assign an owner

Route technical, data or customer exceptions to the right accountable person.

4. Resolve the customer need

Complete the required action manually where appropriate.

Close the loop

5. Correct and retest

Fix the rule or data, test representative paths and document restart decisions.

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

Large or repeated failure

Pause the affected workflow and escalate before processing more records.

Human review

Customer already affected

Communicate honestly and correct the relationship impact.

Human review

Cause unknown

Keep the record stopped; do not repeatedly rerun an unexplained action.

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.

Exceptions with named owners

Measure queue coverage.

Time to contain customer impact

Separate containment from final technical fix.

Repeated root causes

Prioritise removal and regression tests.

Questions about this page

Useful answers, without the sales fog.

1. When should the workflow exception handling playbook start?

A workflow log, customer response or monitoring rule identifies an exception. 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 workflow exception handling 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 workflow exception handling 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 large or repeated failure, customer already affected, cause unknown.

4. How should we judge whether workflow exception handling works?

Review exceptions with named owners, time to contain customer impact, repeated root causes. 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

Workflow triggers Workflow goals Automation New-lead response

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