121 CRM playbook · Email-enquiry handling

Turn an incoming email into a visible, owned question with a useful response and next action.

A fictional accountancy practice receives Noor’s email about bookkeeping support and assigns it to the new-business queue. 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

Email-enquiry handling: the working sequence

Illustrative example

Triage the message
Respond in context
Resolve properly
Human review

Triage the message
Identify customer, purpose, urgency and whether the email contains sensitive attachments.
Respond in context
Answer the question or explain the next step without asking for information already supplied.
Resolve properly
Close only after the answer or follow-up action is owned.
Human review
A person checks the outcome and any exception.
Human decision

Illustrative playbook — names, organisations and activity are fictional.

Fictional workflow demonstration

Follow email-enquiry 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

Email conversations

Sends and receives supported email messages against the customer conversation and contact record.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Keeps email context visible to authorised colleagues rather than one private mailbox.
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 configured business inbox receives a genuine customer enquiry. Before any automated action, confirm that the event, customer record and communication basis are suitable for this playbook.

Trigger

A configured business inbox receives a genuine customer enquiry.

Practical scenario

A fictional accountancy practice receives Noor’s email about bookkeeping support and assigns it to the new-business queue.

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 email-enquiry 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. Triage the message

Identify customer, purpose, urgency and whether the email contains sensitive attachments.

2. Assign ownership

Route by service and authority, with cover for absence.

3. Respond in context

Answer the question or explain the next step without asking for information already supplied.

4. Link related work

Connect the thread to the contact and opportunity where appropriate.

Close the loop

5. Resolve properly

Close only after the answer or follow-up action is owned.

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

Sensitive attachment

Move it to the approved secure process and restrict access.

Human review

Several recipients reply

Set one owner and prevent conflicting responses.

Human review

Unclear or suspicious message

Use the security and spam process before opening links or files.

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.

Enquiries with one accountable owner

Audit unassigned and multiply assigned threads.

Time to substantive response

Do not count automatic acknowledgements as resolution.

Reopened conversations

Use them to identify incomplete answers.

Questions about this page

Useful answers, without the sales fog.

1. When should the email-enquiry handling playbook start?

A configured business inbox receives a genuine customer enquiry. 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 email-enquiry 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 email-enquiry 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 sensitive attachment, several recipients reply, unclear or suspicious message.

4. How should we judge whether email-enquiry handling works?

Review enquiries with one accountable owner, time to substantive response, reopened conversations. 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

Email marketing Team inbox Customer management Multi-channel 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