121 CRM guide · Follow-up exceptions

Follow-up exceptions: give every credible enquiry a clear next step.

This is an operating question, not a request for more CRM fields. This guide helps a small team turn follow-up exceptions into a specific, testable way of working rather than a vague intention. It uses a bounded customer journey, clear ownership and evidence people can review, keeping follow-up exceptions grounded in real work rather than treating it as another abstract CRM ambition.

Subscribe to 121 CRM Seller, billing and cancellationExplore all practical guides

Customer Thread

Follow-up exceptions in a working decision

Illustrative example

Define the question
Observe the work
Agree the boundary
Test and review

Define the question
Write down what the team needs to improve or decide about follow-up exceptions.
Observe the work
Use channel rules, consent records, routing tests, response examples and an exception path, not assumptions.
Agree the boundary
Record how follow-up exceptions may be supported by the CRM and where a person must decide.
Human decision
Test and review
Check the share of actionable enquiries with an owner, response and explicit next step, then revise the method.

Fictional example using Marlow Studio; adapt the method to your own customers, responsibilities and configuration.

Fictional working example

See follow-up exceptions in context

This code-built follow-up exceptions illustration shows how the decision could appear inside a working CRM, demonstrating information and responsibility rather than a fixed account configuration.

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.

CRM building blocks

Connect the advice to day-to-day CRM work.

These are the practical tools behind the guide, with enough context to decide where they can help and where people still need to take responsibility.

Capability 01

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

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

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.

Capability 05

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.

Start with the decision

Start with the decision behind follow-up exceptions

The useful aim is to move each credible enquiry from arrival to an owned and appropriate next action. For follow-up exceptions, define what needs to change, who owns the choice and how the team will recognise a better customer or staff outcome.

The question to answer

Write this enquiry process as a question an owner can answer. Here, the practical task is to turn follow-up exceptions into a specific, testable way of working rather than a vague intention. Name the customer stage and the later action this enquiry process should inform.

Evidence to bring into the room

Collect channel rules, consent records, routing tests, response examples and an exception path. Use a small current sample to test this enquiry process, including one example that did not follow the expected path.

Human review point

A boundary people can recognise

The main risk is that fast automation can send the wrong response, ignore an opt-out or leave an apparently routed enquiry without an accepting person. State the stop, escalation or approval point for this enquiry process in ordinary language and give it to a named person.

A practical method

A four-part method the team can test

Try this method on a representative slice of this enquiry process before changing every team or record. Each part of the follow-up exceptions trial should leave evidence that another person can inspect, challenge and repeat.

1. Set the channel rule

Define what the channel captures, what permission is needed, when it is monitored and what the customer should expect next; keep the practical aim in view: turn follow-up exceptions into a specific, testable way of working rather than a vague intention.

2. Route to an accepting owner

Use service, location, availability or another observable rule, then expose enquiries that remain unaccepted or are reassigned; keep the practical aim in view: turn follow-up exceptions into a specific, testable way of working rather than a vague intention.

3. Respond with context

Give the owner the original message, source, prior relationship and agreed response expectation without forcing the customer to repeat information; keep the practical aim in view: turn follow-up exceptions into a specific, testable way of working rather than a vague intention.

4. Stop and escalate

Define opt-out, duplicate, safeguarding, complaint, unsuitable and incomplete-information paths before automating routine follow-up; keep the practical aim in view: turn follow-up exceptions into a specific, testable way of working rather than a vague intention.

Review the method

Make the next decision visible

Use the second view to inspect ownership, exceptions and the evidence the team should review before extending this enquiry process.

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.

Worked example

How Marlow Studio could apply the guide

Marlow Studio is a small design consultancy. The team tests follow-up exceptions on one bounded customer journey, using fictional data and the existing working practice as its comparison point.

The starting question

Marlow Studio needs to turn follow-up exceptions into a specific, testable way of working rather than a vague intention. The customer context needed for this enquiry process exists today, but it is spread across records and individual knowledge, so another colleague cannot consistently explain the next decision.

The bounded trial

The team selects ten recent examples, applies the four-part method to this enquiry process and records every exception. It changes only the minimum fields, ownership rules and prompts needed for this enquiry process; one person can halt the trial if customer context is lost.

The review conversation

The owner checks the share of actionable enquiries with an owner, response and explicit next step. Staff compare the new route for this enquiry process with the earlier practice, identify avoidable administration and show which awkward case still needs a person rather than another rule.

The honest conclusion

Official product material can evidence a general capability, but it does not establish that the capability is enabled or included in a particular 121 customer account for this follow-up exceptions trial. The trial can show whether the method is clearer for Marlow Studio; it cannot promise revenue, growth or a universal result.

Limits and review

Limits, warning signs and review points

The follow-up exceptions design needs another look when unassigned messages grow, response context is missing, opt-outs are mishandled or customers receive overlapping follow-up. Give this enquiry process both a calendar review and an event-driven trigger so a once-useful configuration does not quietly become misleading.

Treat workarounds as evidence

If staff keep a private list, retype the same value or move this enquiry process into chat, ask what the agreed method failed to represent. Fix that problem before layering another automated action over this enquiry process.

Challenge the apparent signal

The CRM shows captured events under chosen definitions. Before drawing a conclusion from this enquiry process, check missing activity, timing, duplicated records and whether the population still matches the decision.

Reconfirm availability and dependencies

Official product material can evidence a general capability, but it does not establish that the capability is enabled or included in a particular 121 customer account for follow-up exceptions. Recheck the providers, permissions, retention and communication rules supporting this enquiry process when the scope changes.

Human review point

Give somebody the stop decision

The accountable owner must be able to pause this enquiry process, correct the record and explain why an exception was handled differently. Responsibility for this enquiry process cannot be delegated to a status or score.

Questions about this page

Useful answers, without the sales fog.

1. What decision should come first in follow-up exceptions?

Start with the question that changes a customer action or handover: how will the team turn follow-up exceptions into a specific, testable way of working rather than a vague intention? Give this enquiry process an owner and test it against a few current examples before choosing more configuration.

2. What evidence is useful for reviewing follow-up exceptions?

Bring channel rules, consent records, routing tests, response examples and an exception path. Include a normal case, a missing-information case and an exception so the review of this enquiry process does not describe only the ideal journey.

3. Where should automation stop when handling follow-up exceptions?

Stop where context, consent, fairness, professional responsibility or an unusual customer need changes the appropriate action for this enquiry process. A person should own that point in this enquiry process and be able to explain the decision.

4. What should trigger another review of follow-up exceptions?

Review this enquiry process when unassigned messages grow, response context is missing, opt-outs are mishandled or customers receive overlapping follow-up. Also set a proportionate review date for this enquiry process so quiet drift is found even when nobody raises an incident.

Read all CRM questions

Continue the journey

Guides Dormant-lead reactivation Customer management

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