Skip to content
Mint Service Desk Documentation centre

Notifications

Mint Service Desk 3.4.2 user manual.

Tickets

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

FilterNotified ticketsRelated events
ticket.queueon 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.prioritywith 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.servicewith 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.assigneewith 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_authorwith specific article author- New ticket - New article - New comment
ticket.mentioned_queuewith 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_rolewith 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_userwith 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.userwith events from the Events column triggered by the users selected in the filter- New ticket - New article - New comment - Queue change - Assignee change
ticket.customerwith selected customer assigned to ticket- New ticket - New article - New comment - Queue change - Ticket closed - Status change
ticket.ticket_typeon 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.companywith selected companies assigned to ticket- New ticket - New article - New comment - Queue change - Assignee change - SLA Force escalation
ticket.channelwith article in Email channel or Customer Portal channel- New ticket
ticket.first_attribute_dictionary_valuewith the indicated selected value in custom field of dictionary type- New ticket - Status change
ticket.strikeRulesee Tickets → Strike rules in Admin profile- Ticket strike
ticket.strikesee 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

Assets

Configure system, email and push notifications for assets. The initial list contains 3 predefined notifications.

Predefined asset notifications:

  • Asset Alert - This is a notification that involves setting custom fields of the asset type ‘Alert’ and when the time comes the appropriate notification will be sent.
  • Asset Reminder - This is a notification that involves setting a custom field of type “Alert” in the custom asset fields and you can add a time option of how much before the original time you want the reminder to come. When the reminder time arrives, the appropriate notification will be sent.
  • Asset Alert & Reminder - This is a combination of the two notifications written above.

Example: The user sets the date alert to 31/05/2022 at 12:00 p.m. In addition, the user sets the reminder to 1h. This setting will cause the user to get an alert notification at 12:00 and a reminder notification an hour later.

Remember that the user needs to have the correct rights (given by the admin) for Assets 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.

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 type of user will be able to see the notification.

Events

Here you can select one, or more, events for which the user will receive a notification.

For example, if you want to set Alert or Remind the user about assets use one of the options from the list (Alert or Reminder).

Filters

Here you can select some notification filters for assets.

For example, if you want to send notification (‘Events=’ Alert or Reminder) about an assets to a person assigned to an asset (‘Receivers’ = ‘asset.assigne’) you can leave it that way or put some filters.

However, if you want this notification to be sent only to one particular Agent you have to choose him from the ‘asset.assignee’ filter list.

Now, if additionally, you want this notification to be sent only within the Assets from one particular category you can choose this category from the ‘assets.category’ 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 user Assigned to asset or Category where the asset is located.

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.

Channels

The last section of the process of creating a notification requires selecting a channel for which this particular notification will be used.

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.

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 Assets reminder and inside the ‘Channels’ section you will add the title “Assets Reminder” and as a template, you put “Asset Reminder” 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.

Contracts

This section contains all the notifications for Contracts in MINT Service Desk - system, email, and push.

If you like to add some new notifications, click on the button located on the right side of the main view. Now you can start the configuration of a new notification

General settings

The first section is similar to that in the Ticket and Asset notifications and is described there.

Events

Here you can select one, or more, events for which the user will receive a notification.

For example, event “End of support” means a notification will be sent to recipients when the contract ends.

Filters

Here you can select some notification filters

Available contract filters:

  • contract.time_to_end_of_support: set how long before the contract ends to send the notification. Choose “Day”, “Week” or “Month”.

– Remaining hours to use - specifies the percentage of remaining contract hours; once this threshold is reached, a notification will be triggered the next time work time is recorded. The notification will be triggered when the number of remaining hours is equal to or less than the set threshold. Work time is recorded in the ticket details under the “Spent time” section.

  • contract.contract_type: restrict the notification to a specific Contract Type.
  • contract.company: select the companies assigned to the contracts.
  • contract.service: filter by services linked to the contracts.

Receivers

This section is similar to that in the Ticket and Asset notifications and is described there.

Channels

This section is similar to that in the Ticket and Asset notifications and is described there.

Consents

This section contains all the notifications for Consents in MINT Service Desk - system, email, and push.

If you like to add some new notifications, click on the button located on the right side of the main view. Now you can start the configuration of a new notification

General settings

The first section is similar to that in the Ticket and Asset notifications and is described there.

Events

Here you can select one, or more, events for which the user will receive a notification.

We can select here:

  • New answer - notification will be sent for every new user answers
  • Removed answer - notification will be sent whenever a user removes an answer

Filters

Here you can select some notification filters

Let’s describe them here

– consent.consentId - here you can selected specific consent or consents created in Consents tab – consent.user - here you can select user or users which made consent action (new answer or removed answer)

Receivers

This section is similar to that in the Ticket and Asset notifications and is described there.

Channels

This section is similar to that in the Ticket and Asset notifications and is described there.

Filters

At the top of the page, you can find a set of filters that can be used to narrow down the list of notifications.

The available filters are:

  • Notification type: All types, Tickets, Assets, Contracts, Consents
  • Channel: All channels, System, Email, Push
  • Status: All statuses, Sent, Awaiting, Error, Unknown
  • Date range: Created from, Created to

Notification list

The main part of the page contains the notification list. As in many other areas of the system, a search field is available in the upper-right corner.

Notifications can be searched by columns such as Error Message, Notification Entry, and Type. Some columns can also be sorted. As with other tables in the system, you can adjust the number of records displayed per page using the pagination settings.

Columns

Of all the columns available in the table, the following are described in more detail because they provide additional options or functionality.

Sent date

The Sent date column allows you to quickly determine whether a notification has already been sent and, if so, when it was sent. If the notification has not been sent, its current status is displayed instead. This status can help determine the appropriate next steps when investigating why the notification has not been sent.

For example, the Awaiting status indicates that the notification may still be sent, while Error indicates that the notification will not be sent.

Notification entry

The Notification entry column provides the most interaction options.

First, it displays the name assigned to the notification in its configuration, making it easy to identify the relevant notification entry.

Next to the notification name, a gear icon is displayed.

Clicking this icon takes you directly to the configuration of the selected notification, where it can be edited.

The column also provides access to the actual content of the notification.

You can preview the message by clicking either the speech bubble icon or the notification name.

Receivers

The Receivers column displays the number of recipients of a notification.

Clicking Receivers opens a modal window containing a list of users who received or are intended to receive the notification. The list also includes each user’s unique ID as assigned in Mint Service Desk.

Related identifiers

The Related identifiers column shows the system objects that triggered the notification.

Depending on the notification type, this may be a ticket, article, asset, contract, or consent. The column displays the specific identifier of the related object, such as the ticket ID, article ID, asset ID, contract ID, or consent ID.