121 CRM feature · Customer funnels

Connect acquisition pages to the customer record without pretending every journey is linear.

Design a small sequence of pages and actions around a genuine customer decision, then review where people stop or need help. 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

Customer funnels in a working customer journey

Illustrative example

Details viewed
Noor reads the fictional event information.
Registration started
The form asks for required attendee details.
Completion confirmed
A clear confirmation explains what happens next.
Human decision
Exception visible
An incomplete payment is reviewed before any reminder.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

Customer funnels, shown as working software

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

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.

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

Funnels

Builds an ordered set of pages around a focused lead, booking or sales journey.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Gives a campaign a clear path and supports testing that general website navigation may not.
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 02

Funnel split testing

Compares configured funnel-page variants; the current website builder does not provide the same split-test feature.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Supports evidence-led improvement of a specific conversion step.
Plan for: Generated or templated content is not automatically accurate, accessible, compliant or ready to publish. Split testing is documented for funnels, not general Website pages.
Your team owns: A person must review content, test the journey and explicitly publish or change live assets.

Capability 03

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 04

Site and funnel analytics

Measures supported page views, opt-ins, sales and funnel behaviour.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Shows where visitors progress or leave so a person can decide what to improve.
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 05

Domains and publishing

Connects eligible domains or subdomains and controls preview, save and publish steps.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Lets a business use a branded public address with a deliberate release step.
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.

Use it with purpose

What good customer funnels looks like

A fictional event organiser moves visitors from event details to registration and confirmation, with a clear return path for questions. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Give each step a job

Use one page for explanation, one for an appropriate action and one for confirmation.

Carry context forward

Preserve source and submitted details without making the visitor repeat them.

Review real behaviour

Look at exits and questions to improve clarity rather than simply adding more automation.

Configuration decisions

Decide the operating rules before switching customer funnels 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.

Map the journey

Define entry points, decisions, completion and acceptable exits before building pages.

Set measurement rules

Name each conversion event and document what it does and does not mean.

Human review point

Prepare recovery

Decide how failed forms, payments or abandoned steps are handled.

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 event organiser moves visitors from event details to registration and confirmation, with a clear return path for questions. The example shows the role of the CRM while keeping the consequential decision with a person.

Details viewed

Noor reads the fictional event information.

Registration started

The form asks for required attendee details.

Human judgement

Completion confirmed

A clear confirmation explains what happens next.

Exception visible

An incomplete payment is reviewed before any reminder.

Boundaries and checks

Plan for the limits of customer funnels

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

Data and context

Funnel analytics may not identify every cross-device or consent-limited journey.

Account and provider setup

Split tests need enough suitable traffic and a clear hypothesis.

Keep a person accountable

Human responsibility

A funnel cannot replace human help for exceptions or considered purchases.

Questions about this page

Useful answers, without the sales fog.

1. Is customer funnels 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 customer funnels?

Start with three decisions: map the journey, set measurement rules, prepare recovery. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether customer funnels is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review give each step a job, carry context forward, review real behaviour rather than treating clicks, sends or record counts as proof of business value.

4. Can customer funnels be fully automated?

No. A funnel cannot replace human help for exceptions or considered purchases. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Landing pages Forms and lead capture Abandoned-form follow-up Calendar management

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