Saying no is the part of support people dread most, and the part I think we get most wrong. We soften it into a maybe, or bury it under policy, and the customer leaves more frustrated than if we had been honest in the first sentence. Over time I learned that a clear, kind no protects the relationship far better than a vague maybe ever could.
Lead with the no, then with the why
Hiding the answer three paragraphs down does not make it land softer; it makes the customer scan for it and feel managed. I say the no early and plainly, then explain the reason. People can accept a no they understand. What they cannot accept is feeling like they have to dig for it.
Never hide behind policy
"That is our policy" is the fastest way to make someone feel like they are talking to a wall. The policy may be the reason, but the customer wants a person who gets why it is frustrating. I name the constraint honestly and stay on their side of it: I understand why that is annoying, and here is what is actually going on.
Always offer the next best thing
A no with nothing after it is a dead end. A no followed by what I can do keeps the conversation moving. Even when the alternative is small, it shifts the tone from refusal to help.
I cannot do that, but here is what I can do instead — and if it does not work for you, tell me more about what you are trying to solve and I will keep looking.
That last line matters. It tells the customer the door is still open, and that I am not just closing the ticket. Most of the time, that is all they wanted to hear.