Tier 1 vs Tier 2 Support: When to Escalate

Escalation should not feel like passing a problem into a fog machine. It should feel like handing off a clear case file.

Tier 1 usually handles common, repeatable issues. Tier 2 handles problems that need deeper access, deeper troubleshooting, or more technical judgment.

Keep it with Tier 1 when

• The issue matches a known fix or knowledge base article.
• The request is routine, like a password reset or basic account unlock.
• The user needs guidance, not a system change.
• The ticket can be resolved with approved Tier 1 permissions.

Escalate when

• The fix requires admin access Tier 1 does not have.
• The issue affects multiple users or a business-critical workflow.
• The ticket keeps returning after the standard fix.
• Logs, integrations, security review, or infrastructure checks are needed.

The complaint many IT teams have is not that escalations exist. It is that escalations arrive empty. Before sending a ticket up, include the symptoms, affected users, screenshots, errors, attempted fixes, and why the ticket is being escalated.

A good escalation saves Tier 2 from starting over.