Skip to CRM content
121 CRM

121 CRM feature · Missed-call text back

Recover context from a missed call while the need is still current.

Acknowledge an unanswered call promptly and give the caller a simple way to continue, without pretending a text replaces a person. 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 CRMSeller, billing and cancellationExplore all CRM features

Fictional product demonstration

See missed-call text back 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

Follow up consistently, with people in control

AR
OverviewContactsInboxPipelineAutomation

Follow up consistently, with people in control

Build the sequence, review each decision and test an exception before activation.

Draft v0.4

This example stays on this page and does not send messages or change CRM data.

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

Missed-call text back

Can send a configured text response after a qualifying missed call when the number and workflow are eligible.

How it works
Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it
Acknowledges an enquiry quickly while leaving the team responsible for proper follow-up.
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 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

SMS and MMS

Uses a configured phone provider and compliant number to send and receive supported text and media messages.

How it works
Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it
Supports quick customer updates while preserving the thread in the CRM.
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

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 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 missed-call text back looks like

A fictional plumbing firm misses a call during a site visit, sends a neutral acknowledgement and asks the caller to describe the non-emergency job. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Acknowledge, do not diagnose

Confirm that the call was missed without guessing the reason or promising availability.

Invite a safe reply

Ask for limited information and direct emergencies or sensitive matters to the right channel.

Create an owned response

Route the reply or call-back task to someone who can assess it.

Configuration decisions

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

Set the trigger carefully

Decide which numbers, call outcomes and hours should produce a message.

Write boundary copy

Identify the business and explain that the text is not confirmation of service.

Human review point

Prevent loops

Exclude repeat events, known spam and calls already handled by another person.

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 · Connected operations

Book discovery

October · illustrative availability

MTWTFSS1234567891011121314
11:3014:00

Appointment sequence

Booked

Calendar entry created

1 day before

Reminder scheduled

Exception

Owner reviews a reply

Journey summary

New

24

Illustrative

Owned

21

Illustrative

Due

4

Illustrative

Website
Referral
Direct
Illustrative exampleAll dates, counts and workflow states are fictional. Availability and behaviour depend on the agreed setup.

Practical example

Follow one example from signal to next action

A fictional plumbing firm misses a call during a site visit, sends a neutral acknowledgement and asks the caller to describe the non-emergency job. The example shows the role of the CRM while keeping the consequential decision with a person.

Call missed

A call reaches the business while the engineer is unavailable.

Text acknowledged

The caller receives a short, branded message.

Human judgement

Need described

Sam replies that a tap is leaking but isolated.

Call-back owned

A person reviews urgency and calls Sam.

Boundaries and checks

Plan for the limits of missed-call text back

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

Data and context

The caller may not be able or willing to receive SMS.

Account and provider setup

Telephone and SMS usage may incur provider charges.

Keep a person accountable

Human responsibility

Emergency, safeguarding or sensitive enquiries need a separate response policy.

Questions about this page

Useful answers, without the sales fog.

1. Is missed-call text back 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 missed-call text back?

Start with three decisions: set the trigger carefully, write boundary copy, prevent loops. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether missed-call text back is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review acknowledge, do not diagnose, invite a safe reply, create an owned response rather than treating clicks, sends or record counts as proof of business value.

4. Can missed-call text back be fully automated?

No. Emergency, safeguarding or sensitive enquiries need a separate response policy. 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 trackingSMS messagingMissed-call follow-upContact segmentation

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 CRMSeller, billing and cancellationCompare pricing

121 CRM

Your customers. Your conversations. Your business. Organised around clear ownership and human decisions.