How to handle cancellation requests in Help Scout
A fair process for cancellation emails in Help Scout: saved replies, tags, workflows and satisfaction ratings, plus when a pause or discount is worth offering.
By Florian
Many subscription businesses still receive a good share of cancellations by email: “please cancel my account”, “stop charging me”, “how do I unsubscribe?”. If your support runs on Help Scout, those emails land in the same inbox as bug reports and how-to questions, and they are handled however the agent on shift sees fit.
This guide sets out a consistent, fair way to handle them: cancel promptly, ask one optional question, offer something only when it fits the reason, and confirm in writing. It shows how to support that process with Help Scout’s own tools, based on its documentation: saved replies, variables, tags, workflows, automatic workflows, email satisfaction ratings and the Happiness report (all accessed November 2026). Help Scout does not manage your billing, so the cancellation itself happens in your billing system or app.
The ground rule: never harder than signing up
Whatever you do in the inbox, cancelling by email should not be harder than signing up was. In practice:
- A cancellation request is executed. If the customer clearly asks to cancel, you cancel. You do not wait for them to answer a survey, call you, or reply to an offer.
- Offers are optional and come once. You can mention an alternative in the same reply that confirms the cancellation, or in a reply that asks a genuinely necessary question. You do not reply with an offer and leave the cancellation pending.
- The customer gets a written confirmation with the date the cancellation takes effect.
Rules differ by country and change over time; our guide on click-to-cancel rules summarises where things stand. The process below is designed to stay on the right side of them, but it is not legal advice.
Step 1: recognise cancellation emails with a workflow
Help Scout workflows come in two kinds: automatic workflows, which run in the background on conversations that match their conditions, and manual workflows, which an agent runs on demand and which skip the conditions step. Per Help Scout’s automatic workflows article:
- Conditions support AND and OR logic, up to 30 conditions per workflow, and condition values are not case-sensitive.
- An automatic workflow runs on a given conversation only once.
- “Apply to Previous” can apply the actions retroactively to existing conversations that match.
A simple setup:
- Create an automatic workflow with OR conditions on the subject or body containing phrases such as “cancel my”, “cancel subscription”, “close my account”, “unsubscribe” and “stop charging”.
- Add the action Add Tag(s) with
cancellation-request. Tags can be added from both automatic and manual workflows (tags article). - Assign the conversation to the person or team who can cancel accounts.
- Create a manual workflow “Cancellation handled” that agents run after cancelling: it adds a tag with the outcome (see step 4) and closes the conversation.
Keyword rules will catch some emails that are not cancellations (“can I cancel the invite I sent?”). Agents should remove the tag when it is wrong; that keeps your counts honest.
Step 2: write saved replies for each case
Help Scout’s saved replies are managed per inbox under Settings > Inboxes > your inbox > Saved Replies, and can include variables for the customer’s name, the agent’s name and other fields. Three replies cover most requests.
Cancelled, no offer. For customers who are clearly done: the product does not fit, the company closed, they found another tool.
Hi [first name], your subscription is cancelled. You will not be charged again. You keep access until [date], the end of the period you already paid for. If you have a moment, what was the main reason you cancelled? Replying is completely optional.
Cancelled, with a relevant alternative. For reasons where an alternative might genuinely help, such as a temporary break or budget. The cancellation is still done; the alternative is an easy way back.
Hi [first name], your subscription is cancelled and you will not be charged again. Since you mentioned [reason], one option if it helps: we can [pause your account for up to N months / move you to the smaller plan] instead, so your data stays as it is. Just reply “pause” and we will switch it. Otherwise, nothing else to do.
Need one detail. Only when you truly cannot identify the account (several accounts on one email, a different email from the one on file). Ask for the minimum, and cancel as soon as you have it.
Keep the brackets as placeholders your agents fill in; do not promise anything your billing system cannot do.
Step 3: when a pause or discount is worth offering
Offers work when they answer the reason the customer gave, and backfire when they look like a toll gate. A rough guide:
| Reason given | Reasonable alternative | Usually better to just cancel |
|---|---|---|
| “Taking a break”, seasonal use | Pause | |
| “Too expensive right now” | Smaller plan or a time-limited discount | If they already said they are switching |
| “Missing feature X” | Tell them honestly if X is planned, without dates you cannot keep | Yes, in most cases |
| “We are closing the company” | Yes | |
| “Bad experience with support” | An apology and a fix, not a discount | Often |
Do not offer the same discount to everyone who writes “cancel”: customers learn that asking to cancel is how you get a discount. Our guide to pause vs discount vs downgrade goes into more detail.
Step 4: tag the outcome, not just the request
Add a second tag when the conversation is closed, so you can measure what happened:
cancel-donecancel-paused(customer chose a pause)cancel-downgradedcancel-withdrawn(customer changed their mind on their own)
Help Scout’s views and workflow filters support conditions such as “is tagged with any”, “is tagged with all” and “is not tagged with” (tags article). A view of conversations tagged cancellation-request but with no outcome tag shows requests that were left hanging, which is the one number you want at zero.
Step 5: read satisfaction ratings with care
Help Scout’s email satisfaction ratings are enabled per inbox and add rating links to outgoing replies. Customers pick Great, Okay or Not Good, can add an optional comment, and have 10 days from a reply to rate it or change their rating. The Happiness report shows the share of each rating and a Happiness Score (percentage of Great minus percentage of Not Good). Ratings are indexed by the date of the reply, not the date of the rating.
On cancellation conversations, a rating measures how the cancellation was handled, not whether the customer likes your product. A “Great” on a fast, clean cancellation is a good result. A “Not Good” with “I had to email three times” points to a broken process. Help Scout suggests using workflows to flag poor ratings with comments for follow-up; on cancellations, that follow-up is to fix whatever went wrong, not to win the customer back.
Doing this with NoChurn
NoChurn’s Help Scout connector is read-only: it reads conversations and never replies, tags or closes anything in Help Scout. Conversations are matched to your customers by email; doubtful matches are suggested for you to confirm and never merged automatically. They feed the churn score and churn drivers, and serve as dated, verbatim evidence if a cancelled customer later files a chargeback on Stripe or Braintree. If you want fewer cancellations arriving by email at all, NoChurn’s cancel flow gives customers a self-serve path with a reason, an optional offer (discount, pause or plan change) and a one-click cancel button that is always visible, hosted or through the API. See NoChurn + Help Scout.