Situation: Allow agents to choose a ticket template and apply it’s properties to existing tickets
- Requester enters in a ticket either via the web portal or email.
- Agent reviews the ticket and determines this is a common incident, and knows that a ticket template exists
- Agent selects the existing ticket template and associated fields are selected, as well as an appended description
Example:
- Requester submits a ticket via email stating the company benefits portal isn’t loading.
- This is a known issue, and the Agent has a pre-defined script to send to the requester
- The Agent selects the “benefits portal not loading” ticket template, and it automatically populates the associated form fields, as well as the description to send back to the requester.
The current process does not allow for a ticket template to be applied after a ticket is created.


