121 CRM · Customers, conversations, next actions

Keep the customer journey in one visible thread.

Bring enquiries, conversations, ownership and follow-up into a practical CRM that your team can understand — with human judgement kept firmly in the loop.

Subscribe to 121 CRM Seller, billing and cancellationSee the product journey

Customer Thread

A new enquiry becomes an owned next action

Illustrative example

Enquiry
Website form received
Conversation
Acknowledgement recorded
Owner
Assigned to Amina
Decision
Fit reviewed by a person
Human decision
Next action
Call due Thursday

Illustrative example — names and activity are fictional.

See the operating thread

One enquiry, carried through the work.

The useful part is not another database. It is a shared view of the customer, the conversation, the owner and the next action.

121 CRM · Customer thread

New enquiry09:12

Northstar Joinery

Website · Commercial enquiry

“We need a clearer way to coordinate enquiries between the office and site team.”

Owner

Amina K.

Next action

Discovery call

Enquiry
Website form
01
Conversation
Reply recorded
02
Owner
Amina assigned
03
Review
Suitability check
04
Next action
Call on Thursday
05

Illustrative exampleFictional customer and activity. Exact fields, channels and stages depend on configuration.

Inside the working system

See what each part contributes.

The CRM is easier to plan when contacts, conversations, work, access and automation are treated as separate capabilities with clear responsibilities.

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

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

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

Capability 05

Workflow builder

Combines a start event with an ordered sequence of configurable actions.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Turns a repeatable customer process into a visible, reviewable flow.
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.

Recognise the problem

Customer work is difficult when the story is scattered.

An inbox can hold the message. A spreadsheet can hold the name. Neither automatically gives the team a shared, current view of what happens next.

Enquiries without owners

Make responsibility visible so the team can see who is following up.

Conversations without context

Keep supported messages alongside the customer record and current opportunity.

Follow-up held in memory

Record the next action and due date instead of relying on someone remembering.

The working journey

Capture. Converse. Organise. Follow up.

121 CRM can be configured around a real customer journey, rather than asking your team to adopt a generic stage list.

Know the customer

Connect useful details, activity, tasks and opportunities in one working record.

Manage the opportunity

See the stage, owner and next action without pretending a pipeline can predict the outcome.

Human decision retained

Keep the human

Use automation for routine movement while people handle judgement, consent and exceptions.

Three working views

Move from signal to action without losing the context.

Booking, reminders and reporting sit around the same customer thread. The examples are illustrative, not a promise of a particular configuration.

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.

Platform or partnership

Use the platform. Add practical help where it is agreed.

The subscription provides access to 121 CRM. Configuration, migration, training, managed operation and other support are not assumed to be included unless they are expressly agreed.

Verified checkout detail

Platform access

The approved checkout identifies 121 CRM at £250/month (no VAT charged) with unlimited users.

Scope before work

Onboarding

Agree the starting data, workflows, access and acceptance checks before configuration work begins.

To be agreed

Ongoing support

Choose only the help your team needs; service commitments remain subject to an agreed scope.

Questions about this page

Useful answers, without the sales fog.

1. Which parts of the customer journey can the CRM organise?

The CRM can organise configured customer records, conversations, opportunities, appointments, follow-up and reporting. Start with the parts that solve a real handover or visibility problem.

2. Do we need to enable every feature?

No. A smaller setup that the team understands is usually a better starting point. Add another capability when its owner, data, workflow and benefit are clear.

3. Does enabling a feature make the process automatic?

No. Features still need configuration, useful data and day-to-day ownership. Automation can coordinate routine steps, but people remain responsible for judgement and exceptions.

Read all CRM questions

Continue the journey

Explore customer management See sales pipelines Review pricing

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