121 CRM playbook · Inbound-call handling

Answer, identify, route and record inbound calls without losing the customer’s purpose or next action.

A fictional property firm receives Alex’s call about a viewing and routes it to the available enquiries team. 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

Inbound-call handling: the working sequence

Illustrative example

Set the opening context
Resolve or route
Create the next action
Human review

Set the opening context
Identify the business and, where relevant, explain recording or privacy information.
Resolve or route
Answer within authority or assign the call and context to the right person.
Create the next action
Confirm booking, call-back, information request or closure.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow inbound-call 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

Keep customer messages together

OverviewContactsInboxPipelineAutomation

Keep customer messages together

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

Search inbox

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

Call handling

Supports configured inbound and outbound calling, routing, voicemail and related call records.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Makes call activity part of the customer history rather than a separate phone log.
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

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 03

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 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 call reaches an approved business number during or outside configured hours. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A call reaches an approved business number during or outside configured hours.

Practical scenario

A fictional property firm receives Alex’s call about a viewing and routes it to the available enquiries team.

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 inbound-call 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. Set the opening context

Identify the business and, where relevant, explain recording or privacy information.

2. Understand the purpose

Capture a concise reason and verify identity only to the level needed.

3. Resolve or route

Answer within authority or assign the call and context to the right person.

4. Record the outcome

Use meaningful outcomes rather than “spoke to customer”.

Close the loop

5. Create the next action

Confirm booking, call-back, information request or closure.

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

Caller at risk or in distress

Use the approved emergency or safeguarding route, not a routine script.

Human review

Identity cannot be verified

Limit disclosure and arrange a secure next step.

Human review

No suitable person available

Give an honest call-back window and named queue.

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.

Calls with a meaningful outcome

Audit vague and missing records.

Transfers with context retained

Reduce customer repetition.

Promised call-backs completed

Compare actual service with stated expectations.

Questions about this page

Useful answers, without the sales fog.

1. When should the inbound-call handling playbook start?

A call reaches an approved business number during or outside configured hours. 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 inbound-call 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 inbound-call 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 caller at risk or in distress, identity cannot be verified, no suitable person available.

4. How should we judge whether inbound-call handling works?

Review calls with a meaningful outcome, transfers with context retained, promised call-backs completed. 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

Call tracking Team inbox Tasks and activities Web-chat handling

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