Zendesk macros for cancellation and pause requests

If customers can email support to cancel, your Zendesk agents are running a cancel flow whether you designed one or not. Without macros, each agent improvises: one cancels immediately, another sends three retention offers, a third forgets to confirm the end date. The result is inconsistent for customers and impossible to measure.

This guide gives you a small set of macros for cancellation and pause requests, explains how to build them in Zendesk, and sets out the rules that keep them honest. It relies on Zendesk’s help center articles on creating macros, creating macros from existing tickets, Liquid markup and placeholders, suggested macros and the Comment text condition (all accessed November 2026).

How Zendesk macros work

A macro is a saved set of actions an agent applies to a ticket in one click. Actions can add comment text, update ticket fields, add or remove tags, add followers and change the assignee. Points from Zendesk’s documentation that matter for this use case:

Where to create them: in Admin Center, under Workspaces, Agent tools, Macros, then “Create macro”.
Who can use them: the “Available for” setting limits a macro to all agents, specific groups, or only you.
Shared vs personal: by default, agents can only create personal macros; shared macros are created by admins (or by agents whose custom role allows it, on plans with custom roles).
From a real ticket: you can turn a good reply into a macro with “Create as macro” in the ticket options menu. Zendesk suggests rewriting the comment so it is less specific to the original request.
Placeholders: macros can insert ticket and user data, such as the requester’s first name, with placeholders like {{ticket.requester.first_name}}. Custom user fields can be used as placeholders too, which is how you can show a plan name or renewal date if you sync them into Zendesk.

Rules before the templates

Cancellation macros are retention tools, and retention tools are easy to abuse. Four rules:

Cancelling is always an option in the first reply. The customer must be able to answer “just cancel” and have it done.
One offer, at most. If the customer declines, cancel. Do not send a second macro with a bigger discount.
Confirm in writing, every time. State what was cancelled, the effective date, and whether any charge or refund follows.
The macro does not do the cancellation. Zendesk macros change the ticket, not the subscription. The agent still cancels in your billing system or admin. Build a checklist into the internal note so nobody forgets.

Click-to-cancel rules in several jurisdictions require cancellation to be as easy as signing up; see click-to-cancel rules for SaaS.

The macro set

Name macros so they sort together in the picker, for example with a Cancel :: prefix.

Cancel :: First reply

Actions: add tag cancel-request, set a custom “Request type” field to Cancellation if you have one, add comment:

Hi {{ticket.requester.first_name}}, thanks for getting in touch. I can cancel your subscription for you right away.

If you have a moment, could you tell me what made you decide to cancel? It helps us improve. If you’d rather not say, just reply “cancel” and I’ll take care of it.

Cancel :: Offer pause

Use only when the reason is temporary: a seasonal business, a project ending, a team on leave.

Actions: add tags cancel-offer and offer-pause, add comment:

Thanks for explaining. Since it sounds like a quiet period rather than a problem with the product, I can pause your subscription instead: no charges while it’s paused, and your data stays as it is. It would restart on [date].

If you’d still prefer to cancel, reply “cancel” and I’ll do it straight away.

Cancel :: Offer plan change

Use when the reason is price, and you have a cheaper plan that really covers their usage.

Actions: add tags cancel-offer and offer-downgrade, add comment:

I understand. Based on how you’re using the product, the [plan] plan at [price] would cover what you need. I can switch you now, effective from your next billing date.

If you’d rather cancel, just reply “cancel” and I’ll take care of it.

How to choose between pause, discount and downgrade is covered in pause vs discount vs downgrade.

Cancel :: Confirm cancellation

Actions: add tag cancel-done, set status to Solved, add comment:

Your subscription is cancelled. You’ll keep access until [end date], and you won’t be charged again. If you ever want to come back, you can restart from your account at any time.

Thanks for having been a customer.

Cancel :: Confirm pause

Actions: add tag cancel-paused, set status to Solved, add comment:

Done: your subscription is paused until [date]. You won’t be charged during the pause. We’ll send you a reminder a few days before it restarts, and you can cancel at any point.

Only promise the reminder if you actually send one.

Cancel :: Internal checklist

A separate macro that adds an internal note, not a public reply:

Checklist: (1) cancelled or paused in billing, (2) end date confirmed to customer, (3) reason tag added, (4) refund decision noted.

Tagging reasons

The macros tag the outcome. Add a second tag for the reason so you can learn from the requests: reason-price, reason-not-using, reason-missing-feature, reason-switching, reason-support, reason-other. Keep the list short and stable; if you need help choosing categories, see churn survey questions.

With outcome and reason tags on every ticket, a monthly report answers: how many cancellation requests came in, which reasons dominate, and which offers were accepted for which reason.

Getting the right macro in front of agents

Route cancellation tickets. A trigger with Comment text conditions (“cancel”, “close my account”, “unsubscribe”, “pause”) can add the cancel-request tag and assign the ticket to the group that handles billing. Expect false matches and review them.
Suggested macros. Zendesk can suggest macros to agents based on the ticket; the availability of this feature depends on your plan, so check it in your account.
Restrict who can use offer macros. Use “Available for” to limit discount or plan-change macros to the group that is allowed to grant them.

Measuring

Once tags are in place, build a view or an Explore report of tickets tagged cancel-request by month, split by outcome tag. Compare offer acceptance by reason. If a paused customer cancels at the end of the pause, count that too: a pause that only delays churn by two months is still useful, but it is not a save.

Doing this with NoChurn

NoChurn’s Zendesk connector is read-only, so your macros, tags and triggers stay in Zendesk and keep working as they are. What NoChurn adds is a self-serve cancel flow you can link to from the first-reply macro: reasons, one matching offer (discount, pause or plan change) and a one-click cancel that is always visible, hosted or built headless with the API. Customers who cancel can get win-back emails at day 30, 60 and 90 based on their reason. NoChurn also reads Zendesk tickets, matched to customers by email (doubtful matches are suggested, never merged automatically), for the churn score and as evidence if a cancelled customer later disputes a charge. See NoChurn + Zendesk.