Define what a save-off offer may include

A save-off offer is the concession a retention specialist may make to keep a customer who asks to cancel. It may include a discount, a pause, a plan change, or a short extension. Write the allowed offers by product and by customer value. An offer that is not on the list needs an owner's approval.

Separate a save-off from a refund or a contract waiver. A discount changes the next bill, while a refund returns money already collected. The two need different approvals and different records. Mixing them lets a specialist promise money the client did not authorize.

State the maximum value and the maximum duration for each offer. A percentage discount and a free month are both concessions with a cost. Record the cost on the offer so the client can see the total. A limit without a cost estimate is hard to enforce.

Name the customers or segments that are out of scope for retention offers. A regulated account or a disputed contract may need legal review before any concession. Put the exclusion beside the offer list. The desk should stop rather than improvise on an excluded account.

Write the limit before the queue opens

The limit should be written before the first cancellation arrives, not negotiated during a call. Set it with the client owner and record the effective date. Publish it where the retention desk can see it during a request. A limit that lives in a meeting note is not a control.

Decide who may approve an offer above the limit and how fast that approval must arrive. A named manager with a backup is better than a shared inbox. Record the approval channel and the expected response time. The desk needs a real path when the answer is negative.

Set a separate limit for a first-time cancellation and for a repeat request. A customer who has already received a concession may not qualify for another at the same level. Record the prior offers on the account. This prevents a loop of repeated save-offs.

Review the limit when pricing, packaging, or the cancellation policy changes. Record the change and retrain the desk before the new limit applies. An outdated limit can create a promise the client will not honor. The review date belongs on the written rule.

Record the cancellation request at first contact

Record the cancellation request when the customer first asks, not when the save-off fails. Capture the reason, the product, the requested end date, and the channel. The record starts the clock on any contractual or regulatory deadline. A request logged after the fact can miss that deadline.

Do not make a save-off a condition of accepting the cancellation. The customer's request stands even if they decline the offer. Record the decline and continue the cancellation path. A retention target should never block the customer's choice.

Note the exact offer made, including the value and the duration. Record whether the customer accepted, declined, or asked for time. A verbal acceptance still needs the customer's written confirmation. The record should show what was promised and when.

Keep the cancellation reason in the customer's own words where possible. A short category is useful for reporting, but the raw reason explains the pattern. Do not rewrite a complaint into a neutral label that hides the cause. The next product review needs the real wording.

Handle a request that arrives through a third party

A cancellation may arrive through a reseller, a bank, or a payment provider. Confirm the customer's identity and the authority of the third party before acting. Record the source and the reference number. A third-party request without authority is not a valid cancellation.

Check whether the third-party channel has its own deadline or evidence format. Some payment providers require a specific dispute reference. Record the format the provider accepts. A correctly handled request can still fail if the reference is wrong.

Tell the customer what was received and what happens next. Use the contact method on the account, not the address in the third-party message. Record the message time and the channel. This prevents a fraudster from using a cancellation to probe the account.

Reconcile third-party cancellations against the billing system before closing. A request can be marked complete while the subscription still renews. Record the billing status and the next charge date. The customer should not need to ask twice.

Review offers against outcomes

Review save-off offers by product, value, and outcome each month. Compare the customers who stayed with those who cancelled later anyway. A high acceptance rate with early churn is not a successful save. The cost per retained customer is the measure that matters.

Look for offers that exceed the written limit. Each exception should have an approval reference and a reason. A cluster of exceptions may mean the limit is unrealistic or the approval path is too slow. Fix the rule or the path, not just the individual case.

Sample the cancellation records for consent and clarity. Check that the customer understood the offer and that the cancellation was honored when declined. Record the findings and the correction. A retention program that confuses customers creates complaints that cost more than the churn.

Share the review with the client owner and the billing team. Name one change to test in the next cycle, such as a clearer offer script or an earlier approval. Record the effective date and compare the next month. A review without a change is only a report.

For the next step, compare this workflow with Set a decision limit for refunds in a delegated queue and Write a customer promise register for outsourced support. For access and oversight, use the authoritative planning reference alongside your own policy.