How FCA and Ofcom rules change churn tactics for UK firms

What to take away

How FCA consumer duty and Ofcom switching rules reset churn tactics

The Financial Conduct Authority (FCA) sets the conduct rules for banks, lenders, insurers, advisers and brokers in the UK. Its consumer duty requires firms to act to deliver good outcomes for retail customers across products, price and service. For retention teams, that turns a save into an outcome question, not just a revenue question.

Ofcom regulates telecoms, broadband, mobile and pay TV. Its switching rules let customers move providers without contacting the losing provider, and they constrain how exit is handled. Together, the two regimes make friction-based retention a regulatory risk and push churn tactics towards clear, evidenced offers. A playbook built on timing, relevance and documented consent still works.

Teams buying tools should treat the compliance model as a buying criterion, not an afterthought. The UK regulations that apply to customer success platforms differ by sector, and financial services and telecoms carry the heaviest load.

Consumer duty also changes how retention performance is measured. A save that keeps a customer in a product they cannot afford, or that hides a price rise, is not a good outcome even if the churn number improves.

The FCA expects firms to monitor outcomes and act on evidence of harm. Retention dashboards that only track saves and revenue will not answer that question on their own.

Ofcom's regime adds a structural point: when switching is provider-led, the losing provider may not know a customer is leaving until the transfer completes. Retention outreach then depends on earlier signals, not on the cancellation call.

That shifts value towards behavioural signals, usage data and service events. It also raises the bar on consent, because contacting a customer who has already decided to leave can look like pressure if the basis for contact is weak.

Consumer duty constraints on outreach and retention incentives

Consumer duty asks firms to avoid causing foreseeable harm and to support customer understanding. In retention terms, that rules out offers that depend on the customer not understanding the deal.

A discounted renewal that resets a contract term without explaining the new commitment is a poor outcome. So is a save offer that moves a vulnerable customer onto a product that costs more over the full term.

Incentives need evidence behind them. If a retention team is rewarded purely on saved revenue, the incentive can push staff towards pressure or selective disclosure. Firms should test whether their incentive design supports the duty.

Outreach timing matters too. Contacting a customer during a complaint, a bereavement or a payment difficulty is rarely a good outcome, even if the offer is generous. Suppression rules belong in the retention platform, not in a spreadsheet.

The FCA also expects firms to consider the needs of customers in vulnerable circumstances. Retention contacts should allow a pause, a referral or a simpler option rather than a single scripted save.

For software buyers, this means the platform should hold outcome data alongside campaign data. A vendor that cannot show how it records customer understanding, complaints and vulnerability flags is a weak fit for a regulated firm.

This is where rules and ethics shape buying decisions, because the tool either supports the duty or quietly works against it.

Ofcom switching and cancellation requirements

Ofcom's switching rules are designed so that changing provider is straightforward. For most broadband and mobile customers, the process is led by the gaining provider, and the customer does not need to speak to the provider they are leaving.

For broadband and landline, One Touch Switch works like this. The customer contacts the new provider. The new provider checks the account details, manages the transfer and coordinates the switch with the losing provider.

The losing provider must respond to the request, but the customer does not need to call it to cancel. If the details do not match, the switch can be delayed.

That removes a classic retention lever. Teams cannot rely on a retention call at the point of cancellation, because the cancellation may never reach them in the old form.

The cancellation process itself must be clear. If a firm does require contact, the route should be easy to find, available through the channels the customer already uses, and free of unnecessary steps.

Notice periods and early termination charges still exist in many contracts, but they must be explained before the customer commits, not discovered at exit. Retention scripts that obscure them create regulatory risk.

For telecoms retention teams, the practical response is earlier engagement. Service quality, contract end dates, price changes and usage shifts are the moments to act, because the formal switch may happen without warning.

Ofcom also expects firms to handle complaints and disputes fairly. A save attempt that blocks a complaint or delays a transfer to protect a retention number is the wrong design.

Retention software should therefore expose contract end dates, notice terms and exit reasons in one place. If the platform cannot show why a customer left, the next save attempt repeats the same mistake.

Consent, consent fatigue and PECR in financial services and telecoms

PECR governs electronic marketing in the UK, including email, SMS and most automated calls. The Guide to Privacy and Electronic Communications Regulations | ICO sets out the rules that apply to retention campaigns.

Consent must be specific, informed and freely given, and it must be recorded. A tick box buried in a sign-up flow, or consent bundled with terms and conditions, is unlikely to meet the standard.

Soft opt-in can cover existing customers in some cases, but it has conditions. The contact details must come from a sale or negotiations, the marketing must relate to similar products, and the customer must have had a clear chance to refuse.

The Direct marketing guidance | ICO explains how these rules apply in practice, including the need for clear information at the point consent is collected.

Consent fatigue is now a real operational problem. Customers receive retention messages from banks, insurers, energy suppliers and mobile networks, and many stop engaging or withdraw consent entirely.

That makes consent state a live data field, not a one-off flag. Retention platforms should hold the source of consent, the date, the channel and the scope, and should respect withdrawal immediately across systems.

Choosing a lawful basis matters as well. The ICO's guidance on Sending direct marketing: Choosing your lawful basis sets out how consent, legitimate interests and other bases apply to direct marketing.

For financial services, legitimate interests can support some service messages, but it is a weaker fit for promotional save offers. Telecoms firms face similar limits, especially where consent was collected for a different purpose.

The wider consumer rules also matter. The Digital Markets, Competition and Consumers Act 2024 strengthens consumer protection duties and enforcement, including for subscription traps and unfair commercial practices.

Consumer protection enforcement guidance for businesses is collected on Consumer protection guidance for businesses - GOV.UK, which is useful when retention messaging sits close to the line on pressure selling.

Designing cancellation and save processes that stay compliant

A compliant cancellation process is short, clear and available. A compliant save process is relevant, evidenced and easy to decline. The two should be designed together, because friction in one often hides in the other.

Use this sequence when you rebuild a regulated process:

A save offer should be easy to understand in one reading. If it needs a call to explain the price, the term or the exit cost, it is probably not a good outcome.

For example, a compliant offer states: 'Your monthly price stays at the amount on your bill for 12 months, no new minimum term, exit cost: none.' A non-compliant version says 'Save now' but leaves the new term and exit cost to a link.

Timing beats pressure. A well-timed message before a price change or contract end performs better than a last-minute call, and it is easier to defend.

Retention teams should also avoid repeated contact after a clear refusal. Treat two or more save attempts after a clear refusal as pressure unless the customer has asked for contact or a service issue requires it.

Checklist for a compliant save process:

Teams that skip this work often find the problem later. Reviewing strategy mistakes before renewal is cheaper than rebuilding a process after a complaint or an FCA information request.

Evidence, records and audit trails for regulated retention teams

Regulators ask for evidence, not intentions. A retention team should be able to show what it did, why, and what happened to the customer.

That means records of consent, contact history, offer terms, customer understanding and outcome. If a customer complains, the firm should be able to reconstruct the case within days, not weeks.

Audit trails should cover who changed a campaign, when, and on what basis. Version history matters when a save script or eligibility rule is challenged.

Retention platforms should log consent withdrawal across channels. A customer who opts out by SMS should not receive an email campaign the next day.

Data retention rules also apply. UK GDPR and the Data Protection Act 2018 set limits on how long personal data is kept, and retention teams should not hold old campaign data indefinitely without a purpose.

Reporting should separate marketing contact from service contact. A service message about a contract change is not the same as a promotional save offer, and the records should show the difference.

Firms should also keep evidence of customer understanding testing. If the save offer was tested with real customers and the results informed the design, that record supports the consumer duty position.

What UK retention software buyers should specify in contracts

Contracts should name the compliance features, not just the campaign features. A vendor that cannot describe its consent model in writing is a risk to the buyer.

Ask for written confirmation of how the platform handles consent capture, withdrawal, suppression and audit logs. Put the detail in the schedule, not in a sales deck.

Set out exit rights. If the firm changes vendor, it needs its consent records, contact history and audit logs in a usable format.

Agree service levels for consent withdrawal. A withdrawal that takes days to propagate across systems is a compliance failure, not a support ticket.

Sample clause: 'The supplier shall propagate a consent withdrawal across all processing systems within one business day and provide evidence of completion on request.'

Finally, check the vendor's own obligations. A processor that mishandles data creates risk for the controller, and the contract should reflect that allocation clearly.

Common questions