121 CRM playbook · New-lead response

Respond to a useful new enquiry quickly, establish ownership and agree the next step without rushing qualification.

A fictional roofing company receives a website enquiry from Kim about a repair and assigns it to the duty estimator. 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

New-lead response: the working sequence

Illustrative example

Validate the record
Assign an owner
Agree the next action
Human review

Validate the record
Check contact details, source, consent and whether the request is genuine enough to work.
Assign an owner
Route the enquiry using service, location and team-cover rules.
Agree the next action
Record a call, appointment, information request or clear close reason.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow new-lead response 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

Know what needs to happen next

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

Harbour Clinic

Review non-clinical brief

Jamie1 day

Field & Form

Assign an owner

Unassigned3 hours

Discovery

Bramble Studio

Call · Thu 11:30

Amina2 days

Oakfield Homes

Site visit · Fri

Tom4 days

Proposal

Marlow Works

Decision due Friday

Tom6 days

Outcome

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

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.

Capability 02

Forms

Collects structured visitor details and maps supported responses into CRM records and workflows.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Turns an enquiry into usable data instead of an unstructured email.
Plan for: Generated or templated content is not automatically accurate, accessible, compliant or ready to publish.
Your team owns: A person must review content, test the journey and explicitly publish or change live assets.

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

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 05

Triggers

Starts a workflow after configured contact, event, appointment, opportunity, course or other supported activity.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Lets follow-up begin from a business event instead of waiting for someone to remember.
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

A valid enquiry enters the CRM from an approved channel. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A valid enquiry enters the CRM from an approved channel.

Practical scenario

A fictional roofing company receives a website enquiry from Kim about a repair and assigns it to the duty estimator.

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 new-lead response 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. Validate the record

Check contact details, source, consent and whether the request is genuine enough to work.

2. Acknowledge appropriately

Confirm receipt and set an honest expectation for the next human response.

3. Assign an owner

Route the enquiry using service, location and team-cover rules.

4. Review fit

A person checks urgency, suitability and missing context.

Close the loop

5. Agree the next action

Record a call, appointment, information request or clear close reason.

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

Duplicate or spam

Suppress automation and merge or close only after an appropriate check.

Human review

Sensitive or urgent request

Move to the approved specialist or emergency route; do not leave it in routine nurture.

Human review

No response

Use a short, proportionate cadence and stop after the agreed limit.

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.

Median time to owned first response

Measure when a useful owner accepts the lead, not merely when an automatic message sends.

Leads with a dated next action

Review whether live enquiries have an accountable next step.

Exception volume and reasons

Use exceptions to improve forms, routing and cover.

Questions about this page

Useful answers, without the sales fog.

1. When should the new-lead response playbook start?

A valid enquiry enters the CRM from an approved channel. 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 new-lead response 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 new-lead response 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 duplicate or spam, sensitive or urgent request, no response.

4. How should we judge whether new-lead response works?

Review median time to owned first response, leads with a dated next action, exception volume and reasons. 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

Lead management Team inbox Follow-up automation Missed-call 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 CRM Seller, billing and cancellationCompare pricing