Cancellation response pack for retention review

Build one pack of draft replies for the cancellation reasons your team sees repeatedly. This gives retention and support leads a consistent starting point to review, rather than asking each agent to write from scratch.

Use the pack for common cases only. Keep exceptions, disputed charges, safeguarding concerns and complaints in their existing escalation process.

1. Define the cases in the pack

Start with recent cancellation contacts. Take a sample large enough to show repeated reasons, then group them by what the customer is actually asking for. Do not begin with broad labels such as retention or billing.

Create a working list such as:

• Price is no longer affordable
• The customer does not use the product
• A needed feature is unavailable
• The product does not work as expected
• The customer is moving to another provider
• The trial or renewal surprised the customer
• The customer wants to pause rather than cancel

For each reason, write one case card in a shared document or spreadsheet. Include these fields:

Field	What to record
Customer situation	The facts the reply may safely assume
Allowed action	What an agent may offer, change or explain
Not allowed	Promises, exceptions or concessions requiring approval
Required wording	Terms that must match policy or product behaviour
Escalation trigger	The condition that stops the standard reply
Source material	Policy section, product note and approved examples used

Keep reasons separate when the permitted action differs. For example, I cannot afford this and I was charged unexpectedly may both mention price, but they need different checks and outcomes.

2. Prepare controlled source material

Give the model a small, current source set for each case card. Use the current cancellation policy, product limits relevant to the request, and a few replies that a lead has previously approved for that same case.

Remove customer names, account numbers, email addresses, order references and internal notes that are not needed to write the template. Replace them with neutral placeholders such as [renewal date] and [plan name].

Label every source clearly:

• Policy: rules, eligibility and required disclosures
• Product facts: what the product can and cannot do
• Approved replies: examples of phrasing and structure, not new rules
• Case card: the audience, allowed action and escalation trigger

Do not treat an old approved reply as policy. It may contain a one-off goodwill decision, an expired offer or wording that no longer applies. If the sources conflict, policy and confirmed product facts win. Ask the owner to resolve the conflict before drafting.

3. Draft one template at a time

Work from one case card at a time. Ask for a response template, not a final message to a named customer. This keeps the output reusable and makes review quicker.

Use a prompt structure like this, replacing the bracketed content:

Draft a customer support response template for this cancellation reason:
[customer situation]

Use only the source material below. Do not add offers, policy terms,
product capabilities or timelines that are not stated.

Allowed action: [allowed action]
Not allowed: [not allowed]
Escalate when: [escalation trigger]

Write in this order:
1. Acknowledge the customer’s reason without overstating it.
2. State the relevant option or next step.
3. Explain any condition in plain language.
4. Give a clear cancellation route if the customer still wants to leave.
5. Add an internal note headed "Escalate if".

Use placeholders only where account-specific facts are needed.
Keep the tone calm, direct and respectful.

Source material:
[policy]
[product facts]
[approved replies]

Ask for two variants only if you have a real channel difference to review, such as email and live chat. Otherwise, one strong template is easier to govern than several near-duplicates.

The draft should not corner the customer into staying. A retention response can explain a suitable option, but it must preserve a clear route to cancel. Do not use pressure, artificial urgency or claims about savings that are not in the source material.

4. Review against the case card

Put the draft beside its case card. A retention lead should check the commercial and customer-experience judgement. A support lead should check operational accuracy, routing and agent usability.

Review in this order:

1. Check every factual statement against the policy or product facts.
2. Check that the draft offers only the action marked as allowed.
3. Check that the cancellation path is visible and accurate.
4. Check that the escalation condition is explicit, not implied.
5. Check placeholders. An agent must know what belongs in each one.
6. Compare the wording with approved replies for tone, without copying outdated commitments.

Record the reviewer decision in the pack: approve, revise, or retire. Add the policy version or internal reference used, plus the review date. Product behaviour and service rules can change, so verify current platform documentation when your workflow depends on model behaviour or limits. See the xAI documentation overview for version-dependent details.

5. Test the pack with awkward examples

Before agents use a template, test it against short fictional scenarios that expose its boundaries. For the same cancellation reason, vary the account status, timing and customer wording.

For example, test whether the price template still behaves safely when:

• The customer asks for a refund as well as cancellation
• The customer says they were charged after cancelling
• The plan named in the message does not match the current plan
• The requested exception is not listed in the allowed action
• The customer is angry but has not stated a clear reason

You are looking for wrong output, not polished prose. Stop the draft from entering the pack if it invents eligibility, implies a guarantee, omits the cancellation route, or turns an escalation trigger into an agent decision.

If you see this	Do this
An unsupported promise	Remove it and tighten the source material or Not allowed field
A vague condition such as “if eligible”	State the actual check, or route to the right team
Tone that sounds defensive or overly sales-led	Replace it with one acknowledgement and one relevant option
A missing cancellation instruction	Add the approved route before resubmitting for review

6. Maintain the habit

Assign one owner for the pack and a review cadence tied to policy, pricing, product and process changes. When a change occurs, identify affected case cards first. Then redraw only those templates, rather than asking the team to rewrite the whole pack.

Track agent feedback in one field: template failed because. Use specific entries such as plan limit changed, escalation route unclear or customer question not covered. Review repeated failures at the next pack update.

When the process does not work, do not keep adding longer instructions to the prompt. Go back to the case card. Usually the problem is an unclear allowed action, conflicting source material, or a cancellation reason that is too broad. Split the case, resolve the policy question with its owner, then draft and review again.