Solution · UK small businesses

Give a growing team one clear view of the customer work.

When enquiries, messages and follow-up sit with different people or tools, the customer story becomes difficult to see. 121 CRM can organise the shared journey without pretending software runs the relationship.

Subscribe to 121 CRM Seller, billing and cancellationRead what a CRM does

Customer Thread

A day in a small service business

Illustrative example

Morning
New website enquiry
Midday
Owner replies with context
Afternoon
Appointment booked
Review
Fit confirmed by person
Human decision
Friday
Pipeline reviewed

Fictional workflow. Exact channels, booking and reporting depend on the agreed configuration.

Shared working day

One enquiry stays visible as different people contribute.

The customer thread connects contact, conversation, owner, review and next action without an outcome promise.

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.

The working building blocks

Use the CRM where it improves the working day.

The same core capabilities can support different sectors, but the data, permissions, professional boundaries and handovers need to reflect the business using them.

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

Smart lists

Builds reusable contact views from saved filters and relevant record conditions.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Lets teams focus on a working group without maintaining separate copies of the same contacts.
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 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.

Capability 06

Appointments

Stores scheduled customer interactions with time, attendee, owner, status and related contact context.

How it works: Applies configured availability, booking rules and connected-calendar settings to eligible appointments.
Why use it: Makes booked work visible alongside the customer conversation and follow-up.
Plan for: Sync, meeting-link and resource behaviour varies by calendar type and external provider.
Your team owns: Staff must handle exceptions, incorrect availability and bookings that need judgement.

The working day

Keep the hand-offs visible as the team gets busier.

A recognisable working day makes the hand-offs concrete. This 121 journey focuses on ownership rather than instant-response or growth claims.

An enquiry arrives

A supported source can create or update the customer record, retain useful context and assign the first next action.

A colleague continues

The current conversation, owner and opportunity are visible so the customer does not have to restart the story.

The owner reviews the week

A pipeline and due-work view helps the team find stalled enquiries and missing actions without manufacturing a forecast.

Start small

Configure the few things the team must use consistently.

Adoption is more likely when the first view and daily expectations are understandable.

Customer and enquiry

Agree the minimum useful fields, source, owner and reason for contact.

Pipeline and next action

Use stages that reflect real decisions and require a current owner and next step.

Conversation and appointment

Connect only approved channels and calendars, with clear failure and exception handling.

Add when ready

Connect booking, reminders and review once the basics work.

Additional operational views become useful after the team understands the core record and ownership model.

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.

Grow deliberately

Add workflows and reports when the underlying work is stable.

More automation cannot repair unclear ownership, poor data or an undefined customer journey.

Automation

Begin with a bounded acknowledgement, assignment or reminder and test ordinary and awkward cases.

Reporting

Review source, due work and stage ageing using definitions the team understands.

Scope required

Commercial fit

Confirm setup, usage, integrations and support beyond the verified subscription before relying on them.

Questions about this page

Useful answers, without the sales fog.

1. Is 121 CRM suitable for a very small team?

Potentially. Fit depends on the number and type of enquiries, shared ownership needs, current tools and willingness to maintain a simple agreed process.

2. Do we need to configure every feature at the start?

No. Begin with the customer record, ownership, pipeline and next actions that solve a real problem, then add tested capability deliberately.

3. Can the whole team use the subscription?

The supplied checkout describes unlimited users. Roles and permissions still need to be designed so each person has appropriate access.

Read all CRM questions

Continue the journey

What is a CRM?Compare pricing See the product journey

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