Question handling

What happens when somebody asks how to cancel

Cancellation is the one question where the honest answer and the commercially convenient answer point in different directions, which is why so many businesses bury it. Deciding to answer it clearly is a business decision, not a configuration setting. Once you have made it, the handling is straightforward and unusually valuable.

What they are really asking

How do I stop paying you, by when do I have to act, and what do I lose when I do.

  • how do i cancel my subscription
  • how do i cancel my booking
  • what is the notice period
  • can i cancel and get a refund
  • do i lose my data if i cancel
  • can i pause instead of cancelling
  • how much notice do i have to give
  • i cancelled but was still charged
  • can i cancel before it renews
  • what happens to my account after i cancel

The material that answers it

An assistant is only as good as the document behind it, and for this question the document usually exists but is written in the wrong shape. What each one has to contain to be answerable:

Material that answers this question
The cancellation route, written as stepsWhere the button is, or the address to write to, or the number to ring. Say which one is the real route rather than listing three and leaving somebody to guess. If a written notice is required, say exactly what has to be in it.
Notice periods and renewal datesHow much notice, measured from what event, and what happens to a cancellation that arrives inside the notice window. Index the rule in the form a customer can apply to their own dates without arithmetic they will get wrong.
What happens to service between now and the endWhether access continues to the end of the paid term or stops on request, whether a partial period is refunded, and whether a booking already made survives. This is the question underneath most cancellation messages and it is rarely written down.
Your data retention and deletion policyHow long anything is kept after an account closes, how to request export before that, and how to request deletion. In many markets a customer has a right to ask for their data, so this material has to be accurate rather than reassuring.
Any early termination or contract termMinimum terms, fees, and what happens on a fixed contract cancelled early. If it exists it will be argued about, so index the exact clause rather than a paraphrase of it.

How to handle it

Settle the business question before you configure anything

There is a real decision here and it belongs to whoever owns retention, not to whoever installs the assistant. A tool that answers cancellation questions plainly will help some people leave who might otherwise have given up trying.

The case for answering plainly is that the alternative produces a worse outcome: a person who could not find the route ends up cancelling through their bank, disputing a charge, or writing about it publicly. Make the choice deliberately, then write the material to match it.

Give the rule, not a date

The assistant does not know when a particular customer's term ends and should not appear to. What it can do is state the rule precisely enough that somebody can apply it: notice is measured from this event, it must reach you by this point in the cycle, and a request arriving after that takes effect at the following renewal.

That is more useful than a date it would have had to invent, and it survives being quoted back.

Answer the loss question explicitly

Almost every cancellation message has an unasked second question inside it: what happens to my bookings, my history, my files, my number, my saved work. Somebody hesitating over cancelling is often hesitating over that, not over the money.

Cover it in the same reply: access until when, export before that, retention after, and how deletion is requested. It is the most reused paragraph in this whole family and hardly anybody has written it.

Route the actual cancellation to whatever performs it

The assistant does not write into any system. It cannot cancel anything, and it must not use wording that suggests a cancellation has been recorded because a customer described one in chat.

The safe close is: here is the route, here is the notice rule, and if you want the team to handle it, leave a name, an email and your message. Then be explicit that the cancellation takes effect when the team or the route confirms it, not when the conversation ends.

When it stops being an answer

Retention offers and negotiated terms

A discount to stay, a pause, a downgrade, a waived fee. These are commercial decisions made by a person about one customer, and an assistant that offers one has given away margin nobody authorised. If you run retention offers, keep them out of the indexed material entirely.

Any dispute about notice or a contract term

I cancelled and was charged again, I was never told about a minimum term, the notice period is not what I signed. Each of these is a contested account of what happened and needs somebody who can look at the record.

The assistant should stop quoting the policy at that point, because repeating the clause to somebody who is disputing the clause makes the situation worse.

A cancellation that is really a complaint

Cancel everything, this is unacceptable, I want to speak to someone. Treat the intent behind it rather than the word. These reach a person immediately with the message captured, because the outcome is still recoverable and an efficient process answer is what makes it not.

How this one goes wrong

The cancellation that never happened

A customer types that they want to cancel, has a helpful exchange, and leaves believing it is done. The next charge arrives. Now you have a billing dispute, a customer who can reasonably say they told you, and a transcript that looks like an acknowledgement.

The fix is wording rather than technology. Every cancellation reply ends by naming what actually performs the cancellation and stating that it is not this conversation. It reads as a small friction and it prevents the one outcome in this family that reliably ends in a chargeback.

The same question, trade by trade

The pattern above holds everywhere. The wording, the escalation line and the material behind it do not, so there is a page per trade.

Questions

Can the assistant cancel a subscription for somebody?
No. It does not write into any system. It explains the route and the notice rule, and it can take a name, an email and a message for the team, which arrives at the address you nominate. The cancellation happens where it always happened.
Should we answer cancellation questions at all?
That is yours to decide, and it is worth deciding rather than defaulting. If you choose not to index the material, the assistant will refuse and point at your contact route, which is at least honest. What you should avoid is indexing something vague and letting it improvise.
How do we handle cooling off rights?
Where you trade may give consumers a short cancellation window on distance sales, separate from anything your own terms say. If that applies to you, index your published wording for it and let the assistant quote that rather than the general policy, because the two have different windows and different consequences.

Keep reading

Try it on your own material

Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.