Tickets
Configure ticket notifications by event, filters, recipients, channel and language. Set up SLA alerts and reminders for Pending Autoclose.
Configure system, email and push notifications for tickets. The initial list contains 8 predefined notifications.
Predefined ticket notifications:
New Article: notification will be sent to the user once there is a new message (Article) in the Ticket, for example, a new reply from the Agent or Customer.
New Comment: notification will be sent to the user when there is a internal message in the Ticket Details communication section. Those are small internal messages regarding a particular Article (‘Internal Discussion’).
New Ticket: notification will be sent to the user, whenever there is a new Ticket in a Queue.
Pending reminder: notification will be sent to the user if he earlier set up a ‘Reminder’ inside the Ticket Details view, in the ‘Details’ section.
Queue Change: a notification will be sent to the user when the queue is changed.
SLA Expiration: notification will be sent to the user when time runs out (timer reached 0) for SLA parameter: Response time / Update time / Resolution time, within the Ticket that has SLA/parameters.
SLA Notification: notification will be sent to the user when the SLA Parameter timer (Response / Update / Resolution) reached the Escalation point. The user will know that he has little time before time runs out (timer reaches 0) and he needs to take immediate action.
Ticket closed: a notification will be sent to the user when the ticket is closed.
Remember that the user needs to have the correct rights (given by the admin) for Queues, Tickets Types to receive some of the notifications.
If you like, you can always add some new notifications. To do so click on the button located on the right side of the main view.
Now, in the new view, you can start the configuration of a new notification.
General settings
Enter a notification name; it is required to save. You can also add a description, colour and icon.
If you decide to give a notification a unique icon you need to type its name in the ‘Notification icon’ field.
Choose an icon from the Font Awesome gallery and enter its name in the Notification icon field.
After you do that you will see an icon in two places, on the ‘Activities’ part of the Agent and/or Customer sidebar and in the “Ticket Details” view when you click the Notification icon.
There are also two important things you can do. First, you can set the notification status: on () or off (). Basically, it means activating/deactivating this notification.
Secondly, you can choose which user will be able to see the list of his notifications and for example turn on/of some them. It was described in Web interface > Basics > Notification section of this guide.
Events
Here you can select one, or more, events for which the user will receive a notification.
For example, if you want to notify the user when any of SLA timers (for Response, Update, Resolution) has run out you should select the following events.
Filters
Filters restrict notifications to tickets that match the selected values.
Below we have a list of filters and a description:
- in column Filters - filter name
- in column Notified tickets - conditions for the ticket that must be fulfilled
- in column Related events - the supported event type for a specific filter
Ticket Notification Filters
| Filter | Notified tickets | Related events |
|---|---|---|
ticket.queue | on selected queues | - New article - New comment - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration - SLA Force escalation - Reminder - Queue change - Assignee change - Ticket closed - Status change - Ticket strike |
ticket.priority | with selected priorities | - New article - New comment - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration - SLA Force escalation - Reminder - Queue change - Assignee change - Ticket closed - Status change - Ticket strike |
ticket.service | with selected services | - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration - SLA Force escalation - Ticket strike |
ticket.assignee | with selected agents assigned to ticket | - New article - New comment - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration - SLA Force escalation - Reminder - Queue change - Assignee change - Ticket closed - Status change - Ticket strike |
ticket.article_author | with specific article author | - New ticket - New article - New comment |
ticket.mentioned_queue | with an assigned SLA in which the selected queues are indicated in the configuration | - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration |
ticket.mentioned_role | with an assigned SLA in which the selected queues are indicated in the configuration | - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration |
ticket.mentioned_user | with selected role mentioned in article or assigned SLA in which the selected users are indicated in the configuration | - New article - SLA Update: notification - SLA Update: expiration - SLA Response: notification - SLA Response: expiration - SLA Resolution: notification - SLA Resolution: expiration - SLA Workaround: notification - SLA Workaround: expiration |
ticket.user | with events from the Events column triggered by the users selected in the filter | - New ticket - New article - New comment - Queue change - Assignee change |
ticket.customer | with selected customer assigned to ticket | - New ticket - New article - New comment - Queue change - Ticket closed - Status change |
ticket.ticket_type | on selected ticket types | - New ticket - New article - New comment - Queue change - Ticket closed - Status change - SLA Force escalation - Assignee change - Reminder - Child tickets have been modified |
ticket.company | with selected companies assigned to ticket | - New ticket - New article - New comment - Queue change - Assignee change - SLA Force escalation |
ticket.channel | with article in Email channel or Customer Portal channel | - New ticket |
ticket.first_attribute_dictionary_value | with the indicated selected value in custom field of dictionary type | - New ticket - Status change |
ticket.strikeRule | see Tickets → Strike rules in Admin profile | - Ticket strike |
ticket.strike | see Tickets → Strike rules in Admin profile | - Ticket strike |
For example, if you want to send notification about a New article (‘Events’ = ‘New article’) to a person assigned to a Ticket (‘Receivers’ = ‘ticket.assignee’) you can leave it that way or put some filters.
If you want this notification to be sent only for ticket with specific Agent assigned, you have to choose him from the ‘ticket assignee’ filter list.
Now, if additionally, you want this notification to be sent only within the Tickets from one particular queue you can choose this queue from the ‘ticket.queue’ filter list.
Remember that you can add multiple values for each filter.
Receivers
Here you can select the main target recipient of notifications. That can be for example Customer who created the Ticket (‘ticket.customer’), Agent assigned to the ticket (‘ticket.assigne’), people who are subscribing to the Ticket (‘ticket.subscribers), and so on.
When you click on ‘Select receivers…’ field you will see the list of available receivers.
From that list, you can select and add one or more positions.
Selecting ‘ticket.customer’ applies the restrictions shown below.
Channels
The last section of the process of creating a notification requires selecting a channel for which this particular notification will be used.
The next step will be to select the language from the dropdown list that you want to create a notification for.
For each language, we can configure separate notification content. Agent receives a notification based on their own language setting in the MINT system. If the language the Agent works in is not defined in the notification, the default notification is sent in English (GB) or the first language on the list if we have not set up a notification in English (GB).
Example: In the Mint Service Desk system, there are two Agents - Agent 1 works in Italian and Agent 2 works in Spanish. Admin has set up a notification for both agents. During configuration, Admin saved a response template for English (GB) and Italian. If the notification is triggered, Agent 1 will receive the notification in Italian, while Agent 2 will receive it in English (GB), as the Admin did not configure a notification for Spanish.
When you have selected the channel and language, press the button.
MINT Service Desk system offers 3 channels:
- System – notifications will be sent and visible within the system (‘Activities’ section on the Client/Agent sidebar),
- Email – notifications will be sent on user email address available in the system,
- Push – notification that is used specifically for the MINT Service Desk mobile application.
Use to delete this notification or to edit it.
When you press the edit button, apart from choosing the channel for notification, you can also create a name (‘Title’) and unique template for it (‘Template for:’).
For example, when you’re creating a notification about the SLA clock expiration and inside the ‘Channels’ section you will add the title “SLA Expiration” and as a template, you put for example “Time’s out!” the final result will look like on the screen below.
However, when you leave the ‘Title’ field empty, system will take the ‘Name’ (required field in ‘General setting’ part) and use it as notification title.
Use Dynamic Fields in the title and template to insert the relevant data when a notification is created.
To add the Dynamic field, you need to click on the scissors icon next to ‘Title’ or below ‘Template for:’ field.
Strike rule Notification
To configure a reminder, you need to have set Strike rule configuration (click here to visit) and assign your configuration to Pending Autoclose status in selected ticket type (click here to visit). Then create a new notification (following the creation guidelines described above). In the Events section, select Ticket strike. In the Filters section, find the ticket.strike option. Clicking on this field will display all the options configured in Tickets → Strike rules. You can select one or multiple values from the list.
Let’s set up an example configuration for the First strike option, which triggers after 25% of the time allocated to close the ticket has elapsed. Create a new notification, fill in the Name field, Events, and the ticket.strike filter.
In the Receivers section, choose ticket.assignee so that the assigned agent receives the notification.
In the Channels section, select System and configure the notification content in the desired language. Fill in the notification title and template, then save it.
If our ticket status changes to Pending Autoclose:
the notification will appear after 25% of the time set for the mentioned status has elapsed