121 CRM playbook · Quote follow-up

Follow up an issued estimate with useful context, clear ownership and respectful stop conditions.

A fictional landscaping firm follows up Jo’s garden estimate before its stated validity date. 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

Quote follow-up: the working sequence

Illustrative example

Confirm the document
Offer useful help
Stop or continue deliberately
Human review

Confirm the document
Check that the right customer received the approved version with terms and exclusions.
Offer useful help
Ask whether the customer has questions rather than assuming silence means objection.
Stop or continue deliberately
End the sequence on response, expiry, opt-out or a human decision to pause.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow quote follow-up 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

Keep payments and customer records connected

OverviewPaymentsInvoicesOrdersProducts

Keep payments and customer records connected

See invoices, orders and products alongside the customer journey while keeping reconciliation visible.

Recorded this month

£2,240

Illustrative total

Open invoices

One draft, one sent

Orders

Across three customers

Reference	Customer	Issued	Total	Status
INV-1048	Marlow Works	8 Oct	£1,240.00	Sent
INV-1047	Oakfield Homes	6 Oct	£680.00	Paid
INV-1046	Bramble Studio	2 Oct	£320.00	Draft

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

Estimates

Prepares an amount for customer review before it becomes an approved billing or document process.

How it works: Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it: Provides a controlled step between a sales conversation and a formal charge.
Plan for: Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns: A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.

Capability 02

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

Waits and timing

Pauses a sequence until a duration, time, event or supported condition is reached.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Keeps communication paced around the customer rather than firing every step at once.
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 05

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.

Entry criteria

Begin with a valid trigger, enough context and one owner

An approved estimate is sent and the response remains open. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

An approved estimate is sent and the response remains open.

Practical scenario

A fictional landscaping firm follows up Jo’s garden estimate before its stated validity date.

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 quote 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. Confirm the document

Check that the right customer received the approved version with terms and exclusions.

2. Wait an appropriate interval

Choose timing that reflects the value, urgency and decision complexity.

3. Offer useful help

Ask whether the customer has questions rather than assuming silence means objection.

4. Record the outcome

Capture accepted, declined, revised, delayed or no-decision status accurately.

Close the loop

5. Stop or continue deliberately

End the sequence on response, expiry, opt-out or a human decision to pause.

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

Pricing or scope query

Route to someone authorised to explain or revise the estimate.

Human review

Vulnerability or complaint

Pause automated follow-up and move to the appropriate human process.

Human review

Estimate superseded

Stop messages tied to the obsolete version.

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 estimates with an owner

Every live commercial document should have accountable follow-up.

Age by decision status

Separate genuinely pending work from stale records.

Reasons for revision or loss

Use structured reasons cautiously to improve the process.

Questions about this page

Useful answers, without the sales fog.

1. When should the quote follow-up playbook start?

An approved estimate is sent and the response remains open. 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 quote 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.

3. When should quote 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 pricing or scope query, vulnerability or complaint, estimate superseded.

4. How should we judge whether quote follow-up works?

Review open estimates with an owner, age by decision status, reasons for revision or loss. 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

Quotes and estimates Opportunity management Workflow goals Appointment confirmation

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