Lead with the answer
Say no in the first lines, not after three paragraphs of cushioning. People read a long wind-up as a sign something bad is coming, and the delay makes the answer feel colder.
Give the reason in plain words
One honest sentence on why is enough. It might be policy, cost or product direction. Avoid blaming the system or hiding behind the rules; say what the decision is and who it protects.
Offer what you can do
A no with nothing next feels final. Offer the nearest thing you can do: a workaround, a partial refund, a different plan or a note on the roadmap if one is true. If you have nothing, say so rather than invent something.
- Do not promise a feature you are not building.
- Do not offer a refund you will not give.
- Do say what the customer can try today.
Keep the tone steady
Thank them for asking and acknowledge what they were trying to do. Avoid apology on top of apology. A calm, respectful tone matters more than soft words.
Record the request
A no today can be useful input tomorrow. Tag the request so you can count how often it comes up. If many customers ask for the same thing, the answer may need to change.