Listening: Support Escalation Call (L1 → L2)

Escalate in support contexts means to pass a ticket or issue to a higher tier (L1 → L2 → L3) or to a specialist who has greater authority or expertise to resolve it.

Support tier vocabulary:

• L1 (Level 1) — first-line support; handles common issues with scripted responses
• L2 (Level 2) — technical support; handles complex issues L1 cannot resolve
• L3 (Level 3) — engineering or specialist escalation; often involves developers

Priority/Severity levels:

• P1 / Sev-1 — Critical; system down or major business impact; requires immediate response
• P2 / Sev-2 — High; significant impact, workaround may exist
• P3 / Sev-3 — Medium; limited impact
• P4 / Sev-4 — Low; minor issue or cosmetic

"Give me a rundown" = give me a quick summary. This is a very common phrase in escalation and handover conversations.

Why L2 asks for a rundown: Before spending time on an issue, L2 engineers need to know what L1 already attempted — to avoid repeating steps and to quickly identify where to focus.

What a good rundown includes:

• What the customer reported (the symptom)
• What steps were tried (the troubleshooting history)
• What was ruled out (negative findings)
• Any error messages or logs already collected

Related phrases:

• "bring me up to speed" = same meaning — give me the context I'm missing
• "what's the history on this?" = what has happened so far
• "where are we at?" = what is the current status

"Loop in" = include someone in a conversation or communication chain. It means adding a person so they are informed and involved.

Examples:

• "I'll loop in the on-call engineer" = I will add the on-call engineer to this conversation/thread
• "Can you loop in the customer?" = Can you make sure the customer is part of this communication?
• "Keep me looped in" = keep me informed as things develop

Related phrases:

• "CC them" = add them to the email CC (similar idea)
• "bring in" = same as loop in
• "rope in" = informal — get someone involved, sometimes reluctantly

ETA in this context means Estimated Time to Answer/Resolution — the estimated time when the customer will receive a response or the issue will be fixed.