Skip to CRM content
121 CRM

121 CRM feature · Recurring subscriptions

Make recurring commercial relationships visible without hiding the rules behind automation.

Organise recurring payment arrangements and customer follow-up with clear consent, provider and cancellation boundaries. 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 recurring subscriptions 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

Keep payments and customer records connected

AR
OverviewPaymentsInvoicesOrdersProducts

Keep payments and customer records connected

See invoices, orders and products alongside the customer journey while keeping reconciliation visible.

Recorded this month

£2,240

Illustrative total

Open invoices

2

One draft, one sent

Orders

3

Across three customers

ReferenceCustomerIssuedTotalStatus
INV-1048Marlow Works8 Oct£1,240.00Sent
INV-1047Oakfield Homes6 Oct£680.00Paid
INV-1046Bramble Studio2 Oct£320.00Draft
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

Recurring subscriptions

Creates recurring payment arrangements from eligible products and connected provider settings.

How it works
Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it
Supports repeat billing while preserving a visible subscription state.
Plan for
Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns
A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.
Capability 02

Products and prices

Defines physical or digital products with one-time or recurring prices, variants and sales settings.

How it works
Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it
Creates a consistent product record that can be reused across eligible checkout experiences.
Plan for
Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns
A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.
Capability 03

Payment providers

Connects a supported merchant provider before the sub-account can accept eligible payments.

How it works
Uses configured products, merchant connections and checkout rules for an eligible payment or order journey.
Why use it
Keeps payment processing under an explicit merchant account and provider relationship.
Plan for
Provider fees, tax treatment, disputes, settlement and feature eligibility remain separate responsibilities.
Your team owns
A responsible person must approve prices and terms and resolve refunds, disputes and fulfilment exceptions.
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 recurring subscriptions looks like

A fictional membership organisation records the subscribed offer, next billing context and human-owned cancellation requests. The useful outcome is a record that another person can understand and continue, not simply another automated event.

Use approved offers

Create recurring arrangements only from agreed products, prices, terms and customer authorisation.

Keep the customer context

Connect the subscription status to the person and relevant service journey.

Handle lifecycle events

Own failed payments, changes, cancellations and refunds through an agreed process.

Configuration decisions

Decide the operating rules before switching recurring subscriptions 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.

Confirm provider setup

Check supported payment provider, currency, billing behaviour and account charges.

Agree authority

Define who may create, change, pause or cancel a recurring arrangement.

Human review point

Write customer communications

Explain timing, changes and cancellation routes clearly before taking payment.

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 membership organisation records the subscribed offer, next billing context and human-owned cancellation requests. The example shows the role of the CRM while keeping the consequential decision with a person.

Offer selected

Alex chooses the approved monthly membership.

Terms confirmed

The price and cancellation route are shown before authorisation.

Human judgement

Subscription recorded

The configured provider manages the recurring instruction.

Change requested

A person reviews and completes Alex’s cancellation.

Boundaries and checks

Plan for the limits of recurring subscriptions

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

Data and context

Availability and billing behaviour depend on configured commerce and payment services.

Account and provider setup

The CRM does not remove consumer-law, tax or merchant responsibilities.

Keep a person accountable

Human responsibility

Failed or disputed payments require a considered human process.

Questions about this page

Useful answers, without the sales fog.

1. Is recurring subscriptions 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 recurring subscriptions?

Start with three decisions: confirm provider setup, agree authority, write customer communications. Then test ordinary, missing-data and exception cases with fictional records.

3. What is a practical way to measure whether recurring subscriptions is helping?

Measure whether the intended customer work becomes visible and owned. For this page, review use approved offers, keep the customer context, handle lifecycle events rather than treating clicks, sends or record counts as proof of business value.

4. Can recurring subscriptions be fully automated?

No. Failed or disputed payments require a considered human process. Automation can coordinate repeatable steps, while people remain responsible for judgement, exceptions, consent and correcting the record.

Read all CRM questions

Continue the journey

PaymentsInvoicingOnboarding and supportPayment links

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.