121 CRM feature · Call tracking

Make telephone activity visible enough for responsible follow-up and review.

Connect configured business calls to customer records, outcomes and next actions while treating attribution with care. 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

Call tracking in a working customer journey

Illustrative example

Call received
A caller reaches the fictional service number.
Outcome recorded
The call is answered or marked missed by the configured system.
Record matched
The number is associated with the contact where possible.
Human decision
Next action set
A survey booking or call-back is owned.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

Call tracking, 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 · Reporting summary

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleFictional figures only. Definitions, access, data quality and interpretation determine whether a view is useful.

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

Phone numbers

Supports eligible purchased, ported or hosted numbers subject to country, carrier and compliance rules.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Lets a business use a recognised contact number in connected customer journeys.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider. Number eligibility, registration and portability depend on carrier, country and use case.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 02

Call handling

Supports configured inbound and outbound calling, routing, voicemail and related call records.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Makes call activity part of the customer history rather than a separate phone log.
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

Call reporting

Reports supported call records and outcomes from configured telephony.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Shows call activity and missed demand that may need operational attention.
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.

Capability 04

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.

Use it with purpose

What good call tracking looks like

A fictional home-services firm records whether a tracked inbound call was answered, missed or converted into a survey booking. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Use approved business numbers

Keep customer calls on configured lines with clear ownership and published contact details.

Record the operational outcome

Distinguish answered, missed, voicemail and other useful outcomes.

Link the next action

Create a call-back, appointment or closed reason rather than treating a call count as success.

Configuration decisions

Decide the operating rules before switching call tracking 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.

Plan number use

Define which number appears in each context and how forwarding behaves.

Set handling rules

Agree opening hours, routing, voicemail and missed-call ownership.

Human review point

Interpret reports carefully

Separate call volume from qualified enquiries, completed work and customer value.

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 home-services firm records whether a tracked inbound call was answered, missed or converted into a survey booking. The example shows the role of the CRM while keeping the consequential decision with a person.

Call received

A caller reaches the fictional service number.

Outcome recorded

The call is answered or marked missed by the configured system.

Human judgement

Record matched

The number is associated with the contact where possible.

Next action set

A survey booking or call-back is owned.

Boundaries and checks

Plan for the limits of call tracking

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

Data and context

Number availability, routing and usage costs depend on the telephony provider.

Account and provider setup

Attribution can be incomplete where numbers are shared or journeys cross channels.

Keep a person accountable

Human responsibility

Call status cannot explain conversation quality or customer intent.

Questions about this page

Useful answers, without the sales fog.

1. Is call tracking 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 call tracking?

Start with three decisions: plan number use, set handling rules, interpret reports carefully. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether call tracking is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review use approved business numbers, record the operational outcome, link the next action rather than treating clicks, sends or record counts as proof of business value.

4. Can call tracking be fully automated?

No. Call status cannot explain conversation quality or customer 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

Missed-call text back Call recording Inbound-call handling

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