Escalating Tickets

his video, created by Michael Simmons, serves as a guide for IT staff on the best practices for escalating support tickets to the SysAdmin team. The goal is to provide enough detail on the front end to avoid unnecessary back-and-forth communication (0:01 - 0:30). Key Requirements for Escalation: Before escalating a ticket, technicians are expected to gather as much of the following information as possible: User identification: Who is the impacted user? (3:05) Device details: Include the host name, machine name, or specific asset serial number (3:20-3:58). Technical data: If applicable, provide a MAC address or IP address. The video notes that if an asset is properly attached, this information can often be pulled from Microsoft Intune (4:05-4:20, 6:34-7:01). Evidence: Include a screenshot or screen recording if an error message is involved (0:44-0:47, 4:23-4:34). Process Overview: Gathering Info: The video demonstrates using an example request for Adobe Creative Cloud access. It emphasizes checking existing policies or knowledge bases before escalating (1:51-2:46). Documentation: All collected information should be added to the ticket timeline (5:07-5:14). Consequences of Poor Escalation: Failing to include these details forces the SysAdmin team to request more information, which leads to a "waiting on tech response" status and slows down resolution (7:37-8:09).