Hi @MSimmons 9701ea2 forsyth
Thank you for reaching out! We definitely understand how crucial it is for your teams to have all the technical information in place before tickets are escalated.
Building on what @bverma_iiQ mentioned regarding using Ticket Templates to standardize the initial intake, I wanted to suggest another alternative to level up that workflow using Subtasks and Subtask Groups from the Advanced Ticketing App.
While Ticket Templates are great for the initial submission, you can use the Rules Engine to ensure the SysAdmin requirements stay front-and-center during the escalation process itself:
-
Automated Checklists: You can create a "SysAdmin Escalation Requirements" Subtask Group. Instead of agents remembering to look at a template, you can set a rule: If Ticket Owner is changed to SysAdmin, then Apply Subtask Group.
-
Visible Audit Trail: While subtasks don't currently "hard-block" the escalation action, they provide an immediate, visible checklist in the subtask widget. If a SysAdmin receives a ticket and those subtasks aren't checked off, they have a clear justification to kick it back to the initial agent for more info.
-
Consistency: This ensures that every time a specific escalation occurs, the exact same set of technical requirements is presented to the agent.
You can find more information on how to setup subtasks in the article below. Please don’t hesitate to let us know if you need any additional information about the advanced ticketing app!