Skip to CRM content
121 CRM

121 CRM feature · Customer reactivation

Make reactivation a considered service conversation, not a blast to an old list.

Reconnect with suitable past customers using a relevant reason, current preferences and a respectful stop rule. 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 customer reactivation 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

Smart lists

Builds reusable contact views from saved filters and relevant record conditions.

How it works
Stores or organises supported business data under configured fields, permissions and record rules.
Why use it
Lets teams focus on a working group without maintaining separate copies of the same contacts.
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

Email campaigns

Creates and sends configured email campaigns to eligible audiences using connected sending infrastructure.

How it works
Runs an approved campaign, publishing or reputation process through connected channels and profiles.
Why use it
Lets a business communicate with a defined customer group and measure supported engagement.
Plan for
Platform policies, connection expiry, delivery, public responses, usage and add-on charges can vary.
Your team owns
A person must approve content and handle negative feedback, policy issues and publishing failures.
Capability 03

SMS campaigns

Sends compliant campaign messages through an eligible configured phone setup.

How it works
Runs an approved campaign, publishing or reputation process through connected channels and profiles.
Why use it
Provides a direct channel for appropriate short updates and calls to action.
Plan for
Platform policies, connection expiry, delivery, public responses, usage and add-on charges can vary.
Your team owns
A person must approve content and handle negative feedback, policy issues and publishing failures.
Capability 04

Workflow builder

Combines a start event with an ordered sequence of configurable actions.

How it works
Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it
Turns a repeatable customer process into a visible, reviewable flow.
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.
Capability 05

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.

Use it with purpose

What good customer reactivation looks like

A fictional bicycle workshop contacts opted-in customers whose annual service may be due, excluding recent visits and open complaints. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Define a relevant audience

Use a real service interval or customer need rather than age of record alone.

Check current context

Exclude active work, complaints, opt-outs and records with unreliable contact details.

Offer an easy choice

Give the person a useful next step and a simple way to decline further messages.

Configuration decisions

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

Agree eligibility

Document recency, prior relationship, service relevance and preference rules.

Choose proportionate channels

Use the channel and cadence the customer would reasonably expect.

Human review point

Set stop conditions

End the sequence after response, opt-out, complaint or a short defined attempt limit.

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 bicycle workshop contacts opted-in customers whose annual service may be due, excluding recent visits and open complaints. The example shows the role of the CRM while keeping the consequential decision with a person.

Audience reviewed

Fictional customers with a likely service due are selected.

Exclusions applied

Recent jobs, complaints and opt-outs are removed.

Human judgement

Message sent

The reminder explains why the customer is hearing from the business.

Response handled

Replies and declines stop further messages.

Boundaries and checks

Plan for the limits of customer reactivation

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

Data and context

Historic consent and contact data may no longer be current.

Account and provider setup

A past purchase does not guarantee present interest or suitability.

Keep a person accountable

Human responsibility

Campaign results need context and cannot prove incremental demand.

Questions about this page

Useful answers, without the sales fog.

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

Start with three decisions: agree eligibility, choose proportionate channels, set stop conditions. Then test ordinary, missing-data and exception cases with fictional records.

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

Measure whether the intended customer work becomes visible and owned. For this page, review define a relevant audience, check current context, offer an easy choice rather than treating clicks, sends or record counts as proof of business value.

4. Can customer reactivation be fully automated?

No. Campaign results need context and cannot prove incremental demand. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

Campaign managementContact segmentationCustomer reactivation

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.