Self-serve product journey

Follow one enquiry from first message to next action.

This guided example shows the operating idea without pretending to be a live account or a finished video demo. Every person, message and value below is fictional.

Subscribe to 121 CRM Seller, billing and cancellationExplore every P0 feature

Customer Thread

Northstar Joinery · illustrative enquiry

Illustrative example

09:12
Website enquiry captured
09:13
Acknowledgement logged
09:18
Owner assigned
10:05
Suitability reviewed
Human decision
Thursday
Discovery call due

Illustrative interface — availability depends on the agreed configuration.

Interactive product journey

Open each working view in the example.

Follow the fictional Northstar Joinery enquiry through capture, conversation, pipeline, booking, follow-up and reporting.

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

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.

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

Dashboards

Combines supported widgets and filters into an operational view for ongoing monitoring.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Helps a team review the few measures needed for the next decision.
Plan for: A report reflects available source data and configuration; it does not prove causation or data completeness.
Your team owns: A person must interpret results, investigate gaps and decide what action is justified.

Chapter 01 · Enquiry

Start with the customer, source and reason for contact.

The record gives the team enough context to respond without turning every field into compulsory administration.

Source

Website enquiry — recorded as part of the illustrative journey.

Need

A short, plain-language summary of what the customer asked for.

Human responsibility

Consent and identity

Channel permissions and customer identity need appropriate configuration and team practice.

Chapter 02 · Conversation

Keep the response and ownership visible.

Supported channels can feed a shared workflow once they are connected and configured. Start with the channels your team can operate well rather than enabling everything at once.

Acknowledgement

A routine response may be configured to set expectations.

Assignment

The enquiry has a named owner rather than a shared-inbox assumption.

Human decision retained

Escalation

Sensitive or unusual messages stay with a person.

What joins the views

Routine movement, with a visible human decision.

A workflow can acknowledge, assign and remind. It should also show where a person reviews suitability, consent or an exception.

121 CRM · Workflow sequence

Enquiry received

Capture source and customer

Acknowledgement

Set a clear response expectation

Human review

Check fit, consent and exceptions

Owner assigned

Name the person responsible

Follow-up due

Remind the owner, not the customer blindly

Illustrative exampleA conceptual workflow. Triggers, messages, delays and exceptions need configuration and testing.

Chapter 03 · Opportunity

Make the stage and next action useful to the team.

A pipeline should reflect real decisions, not manufacture certainty. The owner records why the enquiry moves and what happens next.

Stage

Discovery planned.

Next action

Call due Thursday, owned by Amina.

Outcome

Won, lost or paused is recorded by the team with an appropriate reason.

Questions about this page

Useful answers, without the sales fog.

1. Is this a live CRM account?

No. It is an original, illustrative product journey using fictional data to explain the intended workflow.

2. Does every account use these stages?

No. Pipeline stages, owners, fields and workflows should be configured around the business and tested before use.

3. Can I book a live walkthrough?

A booking route and walkthrough commitment have not yet been approved. Contact 121 through the existing published telephone route if you need to discuss fit.

Read all CRM questions

Continue the journey

Explore all features Review pricing Plan onboarding

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