121 CRM feature · Call recording

Treat recordings as sensitive evidence, not a default source of surveillance.

Use call recording only for a defined, lawful purpose with clear notice, restricted access, retention and human review. 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 recording in a working customer journey

Illustrative example

Call begins
The fictional service gives the approved recording notice.
Scope applied
Only the configured line and eligible call are recorded.
Access restricted
A supervisor reviews the recording for the stated purpose.
Human decision
Retention enforced
The file follows the approved deletion schedule.

Illustrative workflow — names, organisations and activity are fictional.

Fictional product demonstration

Call recording, 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 · Data responsibility chain

Customer

Lawful inputs, users, instructions and acceptance

121

Agreed configuration, access handling and documented boundaries

Connected supplier

Service operation, account terms and supplier controls

Access follows named roles

Changes retain evidence

Assurances need approval

Illustrative exampleConceptual responsibility view, not a published certification or exhaustive data-flow diagram.

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

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 02

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 03

Messaging and calling compliance

Requires number verification, applicable registrations, consent, sender identity and opt-out handling for each channel and region.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Makes channel setup a governed operational task rather than just a technical connection.
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 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 recording looks like

A fictional support team records selected service calls after notice, restricts playback to supervisors and deletes recordings under an approved schedule. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Start with purpose and lawfulness

Document why recording is needed and which calls or participants are in scope.

Give appropriate notice

Explain recording and any available alternatives through an approved process.

Control the recording

Restrict access, retention, download and sharing according to the sensitivity of the content.

Configuration decisions

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

Obtain legal and privacy review

Confirm consent or other lawful basis, notices, processor terms and jurisdictional requirements.

Set technical scope

Check which numbers, directions and users record, and test pause or exclusion where required.

Human review point

Define review practice

Limit playback to authorised purposes and record how issues are escalated.

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 support team records selected service calls after notice, restricts playback to supervisors and deletes recordings under an approved schedule. The example shows the role of the CRM while keeping the consequential decision with a person.

Call begins

The fictional service gives the approved recording notice.

Scope applied

Only the configured line and eligible call are recorded.

Human judgement

Access restricted

A supervisor reviews the recording for the stated purpose.

Retention enforced

The file follows the approved deletion schedule.

Boundaries and checks

Plan for the limits of call recording

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

Data and context

Call-recording law and notice requirements depend on context and jurisdiction.

Account and provider setup

Recordings may contain special-category, financial or confidential information.

Keep a person accountable

Human responsibility

Telephony capability, storage and charges require account verification.

Questions about this page

Useful answers, without the sales fog.

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

Start with three decisions: obtain legal and privacy review, set technical scope, define review practice. Then test ordinary, missing-data and exception cases with fictional records.

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

Measure whether the intended customer work becomes visible and owned. For this page, review start with purpose and lawfulness, give appropriate notice, control the recording rather than treating clicks, sends or record counts as proof of business value.

4. Can call recording be fully automated?

No. Telephony capability, storage and charges require account verification. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Call tracking Security and data Permissions and roles Workflow triggers

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