Escalation and saying no without losing the customer
When to hand a case to someone else, how to do it cleanly, and how to refuse a request while keeping the conversation open.
Two situations separate a trained support agent from a new one. The first is knowing when a case must go to someone else and handing it over so the customer does not repeat the story. The second is saying no to a request that policy does not allow, in a way that keeps the person talking to you instead of to a review site. Scenario questions test both, and scoring looks for a specific order of steps.
When to escalate
Escalate when any of these is true: you do not have the system access to fix it; the customer asks for a supervisor twice; the issue involves safety, legal threats or data exposure; or the case has already been reopened once. Do not escalate because the customer is upset; that is normal and you are trained for it.
A clean handover has three parts: tell the customer what will happen and when, write a summary the next person can act on, and stay on the case until the transfer is confirmed.
Example summary: "Order 44812, delivered damaged on 3 Oct, photos attached in ticket. Customer wants replacement, not refund. Replacement is out of stock until 15 Oct; customer not told yet. Please offer the 15 Oct date or an upgrade to model B at no cost. Customer prefers email, not calls, after 6 pm."
Saying no: the four-step order
- Acknowledge what they asked for in their words.
- Say no plainly, once, with the reason in one sentence.
- Offer what you can do.
- Ask which option they want, so the next move is theirs.
A customer wants a refund on a subscription used for five months: "I understand you want the full five months refunded. I cannot refund months that were used, because the plan terms cover only the current billing period. What I can do is refund this month in full and cancel future billing today. Would you like me to do that, or would you prefer to keep access until the period ends?"
Worked example two: the request that is not yours to grant
A customer asks for a discount you have no authority to give. Wrong: "Let me see what I can do" followed by a long hold. Right: "I am not able to apply a discount on this account. I can raise it with the retention team, who respond within one working day, and I will note that you asked. Shall I do that?"
Common mistakes
- Saying "unfortunately" three times. Say no once and move to the offer.
- Blaming policy as if it belongs to someone else. "Our policy" not "their policy".
- Transferring without a summary, so the customer starts from zero.
Practice habit: Write the four-step refusal for one scenario a day: a late return, a lost promo code, a request outside your access. Keep each under 70 words and end with a question.
More in Office and BPO