Escalations

Escalate for a clear reason

An L1 agent may need specialist help with an unfamiliar product issue, a customer complaint or a request approaching its service target. Record the reason and select an eligible destination through the configured escalation path. The new owner needs the customer context and the unresolved question, not just a high-priority label.

The escalation record distinguishes the person sending the work from the person receiving it. Its assignment event shows the resulting responsibility change. A repeated escalation request should resolve to the same accepted hop instead of creating several competing owners or repeated notifications for the specialist.

Make acceptance visible

The named recipient acknowledges that they have accepted the escalation. That action confirms the handoff; it does not resolve the customer’s issue. The receiving agent still needs to investigate, respond and record the actual resolution through the ticket workflow. Closing an escalation task cannot silently close the underlying ticket.

If the recipient has not acknowledged the handoff, the Support Manager can see the outstanding escalation and decide how to intervene. Work should not appear safely transferred while nobody has accepted responsibility. Acknowledgment belongs to the named eligible recipient, so another person cannot dismiss the open handoff merely to clear the manager’s view.

Complete the specialist handoff

Suppose the specialist finds that the customer needs an account configuration change. They record the investigation, prepare the permitted customer response and resolve the request when the required action is complete. The original L1 involvement and escalation remain in the ticket history, allowing the manager to understand how the issue was handled across levels.

Routing still respects team scope, skill requirements and available capacity. If a valid recipient is unavailable, retain an observable unresolved handoff instead of assigning an arbitrary inactive agent. The expected outcome is an accepted escalation with one accountable owner, a traceable reason and a clear distinction between receiving the work, resolving the issue and reviewing any missed service commitment.

Review the working record

Review an unresolved escalation alongside its recorded assignment event and current SLA episode. Those records answer different questions: who accepted the handoff, who currently owns the request and which target applies. Keeping them distinct prevents an acknowledged notification from being mistaken for finished customer work.