Solutions · Start with the operating journey

A CRM should fit how the work arrives, moves and becomes a relationship.

A dental practice, law firm, accountancy practice and trade business may all use contacts and pipelines. The useful differences are in the enquiry, booking, acceptance, sensitivity and follow-up decisions around them.

Subscribe to 121 CRM Seller, billing and cancellationExplore the small-business journey

Customer Thread

One platform, different responsibility points

Illustrative example

Enquiry
Sector context captured
Owner
Right team receives it
Boundary
Sensitive decision identified
Judgement
Qualified person decides
Human decision
Next action
Visible and dated

Sector examples describe operating patterns, not preconfigured packages or guaranteed outcomes.

Sector journey map

Start with the common thread, then place the real boundary.

Every sector needs context, ownership and a next action; the professional, clinical or operating decisions differ.

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

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 04

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.

Choose the journey

Look for the work pattern that resembles your business.

The pages below focus on recognisable operating moments rather than dressing the same feature list in different sector language.

Growing small businesses

Create shared ownership across enquiries, customer conversations, appointments and follow-up.

Professional practices

Organise intake and relationship work while keeping acceptance, conflicts, advice and professional judgement outside routine automation.

Appointment and field services

Connect booking or site work to clear customer communication and the next operational action.

Shared foundation

Every useful setup still needs the same basic disciplines.

Sector language does not remove the need for clear data, ownership, permissions and acceptance.

Relevant records

Collect only useful customer and enquiry context, with additional care for sensitive or regulated information.

Named owners

Give each active enquiry, conversation or appointment an appropriate person and next action.

Bounded workflows

Automate routine movement only after exceptions and professional or clinical decisions are clearly excluded.

Capability selection

Add only the views the sector journey needs.

Booking, workflows, reviews and reporting remain configurable parts of a controlled operating design.

121 CRM · Capability workbench

Trigger

Enquiry captured

Route

Assign by agreed rule

Decision

Person reviews exceptions

Workflow sequence

Route routine work and expose the human decision.

Booking and reminders

Connect availability, confirmation and exception handling.

Review request flow

Agree eligibility, timing, destination and response ownership.

Reporting summary

See source, ownership and due work without promising an outcome.

Illustrative exampleConceptual product views. A capability is available only where it is enabled, configured, tested and commercially agreed.

Fit before configuration

A sector page is a starting point, not an implementation specification.

The final design depends on the business model, existing systems, team roles, service risk and commercial scope.

Map the real journey

Use representative enquiries and customer cases to define stages, hand-offs and useful evidence.

Check connections

Review calendars, practice systems, accounting tools, forms and communication routes separately.

Human approval

Agree acceptance

The customer approves the configured workflow, limitations and responsibilities before operational use.

Questions about this page

Useful answers, without the sales fog.

1. Is there a different CRM product for each sector?

These pages describe sector-specific operating journeys within 121 CRM. They do not claim a separate preconfigured product or included package for every sector.

2. Can 121 copy our current process exactly?

Not automatically. Existing steps should be reviewed for purpose, data, ownership and risk before deciding what to retain, simplify or configure.

3. What if our sector is not listed?

Start with the CRM overview and map the enquiry-to-next-action journey. A new sector page is not required to assess whether the core operating model fits.

Read all CRM questions

Continue the journey

Small-business CRM Health and wellness Professional practices CRM for accountants

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