How to escalate technical support and contact engineering teams?

This article outlines the official escalation procedures for customer service agents when technical issues require engineering involvement. It specifies required information, triage levels, SLAs, on-call contact processes, and best practices for efficient handoffs.

Overview

Escalations should be reserved for incidents that surpass the agents troubleshooting capability or when time-sensitive intervention is required. Proper escalation reduces mean time to resolution. Agents must supply complete diagnostics, reproduction steps, and impact assessments to engineering teams.

Severity Levels and SLAs

• Severity 1 (Critical): Complete service outage impacting many users. SLA: immediate escalation to SRE and engineering with 15-minute response expectation.
• Severity 2 (High): Major functionality impaired for a subset of users. SLA: escalate within 1 hour.
• Severity 3 (Medium): Partial impairment or performance degradation with workaround. SLA: escalate during business hours within 24 hours.
• Severity 4 (Low): Minor issues, feature requests, or general questions. SLA: handle via normal backlog processes.

Step-by-Step Escalation Process

1. Attempt resolution: Perform standard troubleshooting steps and document results.
2. Gather required information: Include account ID, timestamps, environment, logs, HAR files, traceroute, error messages, user steps to reproduce, and screenshots.
3. Classify severity: Based on impact and the number of affected customers, select the appropriate severity level.
4. Create escalation ticket: In Ticketing System > New Escalation. Use escalation template and attach diagnostics. Include customer contact and preferred communication channel.
5. Notify on-call: Use escalation matrix and contact on-call via PagerDuty or the internal chat channel for the applicable service. Post a concise summary with ticket link.
6. Acknowledge and track: Confirm receipt from engineering, update the customer with expected timelines, and follow up until resolution.

Important Notes and Warnings

⚠️ Warning: Do not escalate sensitive personal data in public channels. Use secure systems for transferring PII and ensure redaction where appropriate.

💡 Tip: Attach relevant logs and clearly state the business impact in the first two lines to expedite attention from engineering teams.

Frequently Asked Questions

Q: What if engineering requests additional access?
A: Coordinate with the customer to obtain temporary access or obtain an elevated support session. Ensure access follows approval process and is logged.

Q: How do I escalate outside business hours?
A: Use the on-call pager system for Severity 1 or 2 incidents; include emergency contact details and allow on-call to manage notification procedures.

Handoff Checklist for Agents

• Ticket summary and steps to reproduce
• All collected logs and timestamps
• Customer environment and configuration
• Impact assessment and related customer SLAs

Related Documents and Contacts

• Escalation matrix and on-call schedule
• Runbooks for common critical incidents
• Contact list for Engineering, SRE, and Product teams

Follow this structured approach to ensure escalations are effective, well-documented, and aligned with SLAs. Properly triaged and detailed escalations improve response times and resolution quality.