Knowledge Base / Accounts / Ticket Triage and Escalation
Problem
Practical checks for ticket triage and escalation. Follow the safe steps below and contact your support team if the issue continues.
These are general troubleshooting checks, not a confirmed diagnosis. Follow your organization's procedures and stop if a step could risk data, safety, or managed equipment.
Symptoms to check
- A request is not clearly categorized, not enough detail is provided, or the issue impacts a critical service.
- The problem may affect one user, a department, or a wider business service.
Possible causes
- Missing information, unclear symptoms, or delayed routing may slow down resolution.
- Escalation may be necessary when the issue affects multiple users, business-critical systems, or security risks.
Resolution
- Collect key details: user or device name, location, error message, time started, impact level, and any troubleshooting already completed.
- Classify the ticket by urgency and scope. A single user issue may require basic support, while a multi-user outage or valid security incident needs prompt escalation.
- Assign the ticket to the correct team and include the evidence collected. Good triage reduces duplicate work and speeds up resolution.
- If the issue is repeated, impacts critical work, or suggests security compromise, notify the right administrator immediately and document the escalation path.
- Keep the ticket updated as progress is made so the requester knows the status and the next action.
Prevention and preparation
- Use a standard ticket template for all support requests.
- Train users to include exact error messages, impact details, and screenshots when submitting a request.
Related guides
Still not fixed? Log a support request and include the exact error, who or what is affected, and the steps you already tried. Never include passwords or verification codes.
Submit a ticketLast reviewed: October 2026