Escalation
Routing a Caller Who Asks to Speak With a Manager
Respond to manager requests without unnecessary resistance while preserving context, privacy, and the receiving manager's availability rules.
Acknowledge the request without debating it
When a caller asks for a manager, acknowledge the request and explain the next step. The assistant may ask for enough context to route correctly, but should not force the caller to prove that the concern is serious. A calm question such as "May I tell the manager what this is about?" leaves room for the caller to decline.
Do not promise an immediate conversation unless the manager's availability rule supports it. If the request involves a safety concern, threat, regulated complaint, or another defined urgent condition, follow that specific escalation path first.
Capture a concise escalation brief
Record the caller's preferred name, contact method, account or case reference when appropriate, reason for escalation in the caller's words, desired outcome, and any prior contact. Separate what the caller reported from actions visible in the business record.
Avoid adding judgments such as difficult, unreasonable, or aggressive unless a behavior must be documented for safety and the wording is factual. The manager needs decision context, not a label that could bias the response.
Route to an owner and state the window
Use the manager queue or duty roster rather than a personal number unless direct transfer is approved. Tell the caller whether the next step is a transfer, scheduled callback, or written review and provide the approved response window. Read back the contact details.
If the manager does not respond within that window, move the item to the backup owner and update the caller when policy requires it. Review manager-request outcomes for repeat root causes, missing authority at the first line, and delays. The goal is not to suppress escalations; it is to make them accountable and useful.