Skip to CRM content

121 CRM playbook · Pipeline hygiene

Keep opportunities current, explainable and connected to a real next decision.

A fictional building firm reviews opportunities with no next action or stage change in fourteen days. 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.

Fictional workflow demonstration

Follow pipeline hygiene 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

Know what needs to happen next

AR
OverviewContactsInboxPipelineAutomation

Know what needs to happen next

See each opportunity's stage, owner and next action in one view.

6 open2 need review

New enquiry

2

Harbour Clinic

Review non-clinical brief

Jamie1 day

Field & Form

Assign an owner

Unassigned3 hours

Discovery

2

Bramble Studio

Call · Thu 11:30

Amina2 days

Oakfield Homes

Site visit · Fri

Tom4 days

Proposal

1

Marlow Works

Decision due Friday

Tom6 days

Outcome

1

Hill & Co

Reason recorded

AminaClosed
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

Opportunities

Represents a potential sale or deal linked to a contact, value, owner and pipeline position.

How it works
Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it
Shows which customer conversations are active commercial work rather than general contacts.
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 02

Pipelines

Defines an ordered sales process through which opportunities can be reviewed and moved.

How it works
Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it
Makes the sales process visible so follow-up is based on stage rather than memory.
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

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 04

Stages and statuses

Uses configured stages plus open, won, lost and abandoned statuses to describe the state of a deal.

How it works
Tracks a potential deal, stage, owner or task using configured pipeline and record rules.
Why use it
Separates progress through a process from the final commercial outcome.
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 scheduled review identifies open opportunities that are stale, incomplete or inconsistent. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A scheduled review identifies open opportunities that are stale, incomplete or inconsistent.

Practical scenario

A fictional building firm reviews opportunities with no next action or stage change in fourteen days.

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 pipeline hygiene 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. Prepare the view

Filter live opportunities by owner, stage, age and missing next action.

2. Check reality

Ask whether the work is still live and what evidence supports the current stage.

3. Correct the record

Update stage, value basis, owner and next action from known facts.

4. Close honestly

Record won, lost, duplicate or abandoned outcomes with an appropriate reason.

Close the loop

5. Fix recurring causes

Improve stage definitions, training or automation behind repeated errors.

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

Owner unavailable

Reassign temporarily with context rather than editing blindly.

Human review

Customer decision genuinely delayed

Keep the record open with a dated review and reason.

Human review

Value uncertain

Use the agreed basis or leave it unknown rather than inventing a forecast.

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.

Open opportunities with dated next actions

Review by owner and stage.

Stale items corrected or closed

Track clean-up and underlying causes.

Stage-definition exceptions

Use them to refine the pipeline.

Questions about this page

Useful answers, without the sales fog.

1. When should the pipeline hygiene playbook start?

A scheduled review identifies open opportunities that are stale, incomplete or inconsistent. 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 pipeline hygiene 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 pipeline hygiene 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 owner unavailable, customer decision genuinely delayed, value uncertain.

4. How should we judge whether pipeline hygiene works?

Review open opportunities with dated next actions, stale items corrected or closed, stage-definition exceptions. Combine the numbers with sampled records and customer context; do not treat activity volume as a business outcome.

Read all CRM questions

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.

121 CRM

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