SUPPORT WRITING GUIDE
How to explain a support policy decision clearly
State the decision, explain how the rule applies and offer an approved next step. Use Vellix to review the wording while keeping policy decisions with your team.
Two fictional policy replies made specific
Before
No, that’s against our policy.
After
We don’t add gift notes once packing starts, and your order is already being packed. I can send you a printable note to share separately.
Fictional facts: gift-note changes close when packing starts, this order has reached that stage, and sending a printable note is approved. The revision states the rule, connects it to this order and offers an available option. These facts do not describe a real store’s policy.
Before
Maybe we can make Saturday work. I’ll ask around.
After
Our callbacks run Monday to Friday, 9 a.m. to 5 p.m. Mountain Time, so a Saturday callback is not available. I can send you the weekday times we have open.
Fictional facts: the team has already confirmed these callback hours and declined a Saturday exception. The agent can offer available weekday times. The revision communicates that decision without implying that an exception is still being considered or that a slot has been booked. Both comparisons are editorial exercises, not customer messages or measured Vellix outputs.
Start with the decision your team has confirmed
A useful policy reply tells the customer the decision, how the relevant rule applies to their request and what you can offer next. Check all three before drafting. A polite sentence cannot make an unverified decision correct.
Zendesk’s guidance on saying no recommends researching the request, explaining the reason and considering available alternatives. Use that sequence to prepare the answer. Your team still establishes the policy, its application and any exceptions.
The comparisons above start after those decisions are made. If you are still checking eligibility or waiting for an exception review, say what remains open instead of presenting a final refusal.
Connect the rule to this request
In the gift-note example, “against our policy” leaves out the detail the customer needs. The revised reply names the cutoff and explains that this order has reached it. The customer can see how the rule applies to the request.
Use the relevant part of the policy in plain language. Add a verified explanation of its purpose when that helps, but do not invent a reason such as safety or fairness to make the decision sound stronger. Avoid describing a business rule as a technical limitation unless that is also true.
Explain the decision without judging the customer for asking. A link to the current policy can provide more detail when useful, but keep the explanation of this case in the reply.
Keep the next step within the approved options
The printable note is an available option in the fictional case. It does not change the decision about the packed order. In your reply, explain what the alternative provides without implying that it fulfills the original request.
Help Scout’s guidance recommends being firm and kind when a request cannot be met, rather than stringing a customer along. In the callback example, “maybe” suggests an open decision even though the Saturday exception has already been declined.
Offer only an action you can take. Sending available times is different from booking a callback. If no suitable alternative is approved, keep the decision clear rather than adding an exception, escalation or future follow-up that you cannot provide.
Sources and editorial note
Examples are fictional. Sources for the platform guidance are linked below.