121 CRM feature · Lead management

Bring every credible enquiry into a consistent working process.

Turn new enquiries into owned, visible next actions without losing source, context or consent. The capability is described from official product evidence; its availability, configuration and any usage charges for a particular 121 account still need to be confirmed before reliance.

Subscribe to 121 CRM Seller, billing and cancellationExplore all CRM features

Customer Thread

Lead management in a working customer journey

Illustrative example

Enquiry received
Owner assigned
Fit reviewed
Next action set

Enquiry received
Website form includes service area and preferred contact method.
Owner assigned
Amina accepts the lead and checks the postcode.
Fit reviewed
A person confirms that the request matches the service offered.
Human decision
Next action set
A call is due at 10:30 tomorrow.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

See lead management in the context of real customer work.

This coded interface uses realistic fictional data to explain the operating pattern; it is not a screenshot of a live customer account.

121

Northstar Joinery

Fictional

Know what needs to happen next

OverviewContactsInboxPipelineAutomation

Know what needs to happen next

See each opportunity's stage, owner and next action in one view.

6 open2 need review

New enquiry

Harbour Clinic

Review non-clinical brief

Jamie1 day

Field & Form

Assign an owner

Unassigned3 hours

Discovery

Bramble Studio

Call · Thu 11:30

Amina2 days

Oakfield Homes

Site visit · Fri

Tom4 days

Proposal

Marlow Works

Decision due Friday

Tom6 days

Outcome

Hill & Co

Reason recorded

AminaClosed

Illustrative 121 interfaceAll people, organisations, dates and activity are fictional. Any figures are illustrative. Controls demonstrate interaction patterns, not enabled account features.

How it helps

See how the feature supports the work.

Each part has a clear job. It becomes useful when it fits the way customers already move through the business and your team knows when to step in.

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

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

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.

Use it with purpose

What good lead management looks like

A fictional heating firm receives enquiries from its website, telephone and referrals, then gives each one an owner and a dated next action. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Capture the source

Record where the enquiry came from and the contact details the person chose to provide.

Assign responsibility

Give a named person responsibility for the first useful response and the next decision.

Move qualified work forward

Create an opportunity only when the enquiry meets the team’s agreed entry criteria.

Configuration decisions

Decide the operating rules before switching lead management on

A credible setup begins with ownership, eligibility and exception decisions. Those choices should be written in plain English and tested with realistic fictional data.

Define a valid lead

Agree what minimum information makes an enquiry actionable rather than creating unusable records.

Set response ownership

Decide who receives each enquiry, who covers absence and when an unhandled lead is escalated.

Human review point

Choose the next-action rule

Require a dated action or an explicit closed reason so records do not drift.

From configuration to daily use

Keep the rule, the owner and the exception visible

The second view shows how the capability connects to work a person can review and continue.

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.

Practical example

Follow one example from signal to next action

A fictional heating firm receives enquiries from its website, telephone and referrals, then gives each one an owner and a dated next action. The example shows the role of the CRM while keeping the consequential decision with a person.

Enquiry received

Website form includes service area and preferred contact method.

Owner assigned

Amina accepts the lead and checks the postcode.

Human judgement

Fit reviewed

A person confirms that the request matches the service offered.

Next action set

A call is due at 10:30 tomorrow.

Boundaries and checks

Plan for the limits of lead management

Product capability is only one part of a dependable process. Data quality, provider configuration, consent, permissions and staff cover still matter.

Data and context

Duplicates and incomplete details still need human review.

Account and provider setup

Consent and preferred channel must be respected before follow-up.

Keep a person accountable

Human responsibility

A lead stage describes process position; it does not prove buying intent.

Questions about this page

Useful answers, without the sales fog.

1. Is lead management confirmed as included in every 121 CRM account?

No. The underlying capability is evidenced in official product documentation, but 121 plan entitlement, sub-account configuration, connected providers and usage charges have not been assumed. Confirm the intended setup before relying on it.

2. What should we decide before configuring lead management?

Start with three decisions: define a valid lead, set response ownership, choose the next-action rule. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether lead management is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review capture the source, assign responsibility, move qualified work forward rather than treating clicks, sends or record counts as proof of business value.

4. Can lead management be fully automated?

No. A lead stage describes process position; it does not prove buying intent. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Customer management Sales pipelines New-lead response Tasks and activities

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