How to handle cancellation requests with an AI agent

If the customer wants to cancel, make it easy. Once the holder is verified, it states the consequences from the system, including any fee or refund, mentions one approved offer at most, and cancels routine subscriptions at depth 3 on the customer's confirmation. Cancellations that involve a fee waiver, a refund or a regulated product go to a person.

What is the cancellation process, and who owns it?

Cancellation ends an ongoing service: a subscription, a membership, a contract, an insurance policy, a recurring delivery. Customers expect it to be quick and to take effect when they asked. Firms want to keep customers and recover what they are owed. Regulators and consumer bodies in many markets expect cancelling to be no harder than signing up, and treat obstruction as poor conduct.

Customer operations owns the cancellation process. Product or commercial teams own retention offers. Finance owns fees and refunds. Compliance owns the rules on cooling-off periods and how retention may be attempted. The agent is the customer's first point of contact and must sit on the customer's side of the line, in keeping with our guide to the AI support agent that knows when to say no.

What are the steps, and at what depth?

1. Agent, depth 1: verifies the account holder. Only the holder, or someone with recorded authority, can cancel.
2. Agent, depth 1: identifies what is being cancelled. One subscription among several, the whole account, a single add-on. Customers often say "cancel my account" when they mean one service.
3. Agent, depth 1: reads the consequences from the system: the end date, any early termination charge, any refund for unused time, what happens to content or data, whether a cooling-off right applies.
4. Agent, depth 3: states the consequences plainly, with figures from the system.
5. Agent, depth 3: mentions one approved retention offer, if one exists for this customer, once. If the customer declines, the agent proceeds without a second attempt.
6. Agent, depth 3: cancels on the customer's clear confirmation, for routine cancellations with no fee change and no refund beyond what the system calculates automatically.
7. Agent, depth 2: drafts cancellations needing a decision: a fee waiver request, a disputed refund, a cancellation outside the normal window, or a regulated product such as an insurance policy where your process requires a person.
8. Person, operations: approves drafted cancellations.
9. Agent, depth 3: confirms in writing: what was cancelled, when it ends, final charges or refunds, and how to come back.

Which controls matter, and what evidence does each leave?

One offer, then proceed. Evidence: the transcript showing the offer, the customer's reply and the cancellation that followed.

The customer's confirmation is recorded. Evidence: the confirmation turn and the cancellation timestamp.

Figures come from the system. No estimates of fees or refunds. Evidence: the system reference for each figure.

Effective date as requested. If the customer asked to cancel on a given date, the cancellation takes effect then, not when it was processed. Evidence: request date and effective date side by side.

Exceptions are held. Evidence: held verdicts and approvers.

What should you measure?

• Time from request to confirmed cancellation.
• Cancellations needing more than one contact. Each one is a sign of friction.
• Retention offers made, accepted and declined. A high decline rate is fine; complaints about pressure are not.
• Charges taken after a cancellation request, which should be none beyond those stated.
• Complaints about cancellation, read in full.

Where does it usually go wrong?

Retention becomes obstruction. The agent loops through offers, asks "are you sure?" three times, or claims cancellation must be done by phone. Stop after one offer.

Cancel, close and delete are confused. Ending a subscription is not closing an account, and neither deletes data. Clarify, and route closures and deletion requests to their own processes.

Future payments keep running. The subscription ends but a separate payment instruction, such as a recurring card payment or direct debit set up outside the subscription system, keeps collecting. Confirm that every payment linked to the cancelled service has stopped.

Partial cancellations end everything. A customer cancels one add-on and loses the main service. Confirm the exact item before acting.

Essential cover is cancelled without the consequences being clear. A vulnerable customer cancelling insurance to save money may not realise what they lose. The agent states the consequences and offers support options, without pressing.

Accessibility is overlooked. If cancelling requires a form or a call the customer cannot manage, offer another route; see can an AI agent handle accessibility requests?

Returns and refunds are mixed in. Cancelling an order already shipped is a return, handled as in handling returns requests with an AI agent. A request for compensation alongside a cancellation is a goodwill decision, covered in handling goodwill gesture requests with an AI agent.

Where Pryme fits

In Pryme, routine cancellation is a separately certified capability at depth 3, and anything that moves money beyond the system's own refund calculation is held. Attest replays the agent on your past cancellation conversations to check it stops after one offer and executes when asked.