When is it appropriate to escalate a customer issue to a supervisor?

• A. Never escalate, handle yourself.
• B. When the issue involves policy exceptions, potential liability, or requires authority beyond your scope.
• C. Only escalate for billing questions.
• D. Escalate only if the customer asks for it.

Answer: (B)

Escalation is needed when the situation goes beyond what you can safely and fairly decide on your own. If a customer request involves an exception to policy, could create liability for the company, or requires authority that you don’t have, a supervisor should weigh in. This protects both the customer and the company by ensuring decisions follow the right rules and risk controls, and that the action taken is authorized.

In practice, you would escalate when you encounter a policy exception request, a potential liability issue (such as refunds, credits, or terms that could expose the company to risk), or a matter that requires higher-level approval. If you can resolve it within your scope and within policy, you handle it yourself and keep the customer informed. Gather the essential details—what happened, who’s involved, policies or terms at play, what the customer is asking for, and what steps you’ve taken—so the supervisor has what they need to decide.

Why the other ideas don’t fit: there are many cases where escalation isn’t needed, but this option reflects the moments that truly require supervisory input. Limiting escalation to billing questions ignores situations that involve policy exceptions or risk. Waiting for the customer to ask for escalation places the burden on the customer and can delay resolution when the right action is to involve a supervisor. And handling everything yourself, even when a policy constraint or liability is present, can lead to improper outcomes.