Skip to content
Mint Service Desk Documentation centre

Sla Parameters

Mint Service Desk 3.4.2 user manual.

Activation Scheme

The SLA activation process in a ticket follows the scheme below.

1. New Ticket

The process begins with a new ticket.

2. Checking if the Ticket Has an Assigned Contract

  • Yes: The system verifies whether the contract is appropriate based on the ticket type and SLA priority:

    • If the contract is appropriate: The system assigns the contract to the ticket. The algorithm terminates.

3. Checking if the Ticket Has Both a Company and a Service

  • Yes: The system retrieves contracts that are suitable for both the company and the service associated with the ticket. Then system verifies whether the contract is appropriate based on the ticket type and SLA priority:

    • If the contract is appropriate: The system assigns the contract to the ticket. The algorithm terminates.

    • If the contract is not appropriate: The system checks if the ticket has a company:

      • Yes: The system retrieves contracts for all companies.

      • No: The system retrieves contracts for tickets without assigned companies. The system then verifies whether the retrieved contracts are appropriate based on the ticket type and SLA priority:

        • If the contract is appropriate: The system assigns the contract to the ticket. The algorithm terminates.

4. Checking if the Ticket Has an Assigned Company OR Service

  • If it has a company or a service: The system retrieves contracts assigned to the company or service associated with the ticket. Then system verifies whether the contract is appropriate based on the ticket type and SLA priority:

    • If the contract is appropriate: The system assigns the contract to the ticket. The algorithm terminates.
  • If it has neither a company nor a service: The system retrieves contracts for tickets without assigned companies. It then verifies whether the contract is appropriate based on the ticket type and SLA priority:

    • If the contract is appropriate: The system assigns the contract to the ticket. The algorithm terminates.

5. If No Suitable Contracts Are Found

If previously found contracts are not appropriate, the system attempts to determine SLA parameters based on the ticket queue. If the system does not find suitable parameters, the process ends without assigning an SLA.

Configuration

Parameter set and calendar

In order to add a new set of parameters, you need to click on the button, located on the right side, next to the search field. You will see that a new section has been opened.

In this place, you need to type the name for your set of parameters (‘Parameters name’) and select a ‘Calendar’ from the list. If you don’t see any Calendars available, you need to create at least one in the Calendars section.

Escalation times

Configure ‘Escalation times’ for one or more ticket types and priorities.

For each Escalation time you need to specify 4 levels of reminders:

  • Response time: the time during which the Agent must respond to the new ticket. Time stop when Agent respond to ticket or when Agent has been automatically assigned after status change
  • Update time: the time within which the Agent must answer to any new message after the communication has been started. Time is counted separately for each message and is reset by Agent or Customer article, depending on checkbox setting: “Reset update time after agent response””
  • Workaround time: the time used to determine the workaround time (the time within which the Agent must find workaround solution for issue that Customer reported in ticket). Workaround time stop when ticket status change to “Workaround”
  • Resolution time: the time (counting from the moment that ticket has been created) within which Agent must resolve the Ticket.

You can also add more Escalation times by clicking the button.

Warnings and recipients

For each escalation timer, specify when the agent or other selected recipients receive a warning that time is running out.

For example, 10 % 240 min means that 24 minutes from time start (10% of 240 minutes) an Agent will receive a notification.

The first field (10 %) means a percentage of the whole time available for the agent. The second field (240 min) specifies the whole time an agent must make a specific action before the timer ends and SLA conditions will not be fulfilled.

Add recipients in ‘Select notification targets…’. You can notify individual users, a role or everyone assigned to a queue.

Please note that if you want the above notifications to work, when configuring notifications in the Notifications tab in the Admin, you need to select the following as Receivers respectively: ticket.mentioned_user, ticket.mentioned_role, ticket.mentioned_queue

Forced escalation

At the very bottom, the Force Escalation option is available.

In the first field, select the type of escalation. There are four options to choose from:

  • Response time
  • Update time
  • Resolution time
  • Workaround time

In the next field, enter a number from 0 to 100, which indicates after what percentage of time you want force escalation to activate.

In the third field, specify how many times the customer will be able to escalate the ticket.

Example configuration

This example shows that the user will be able to escalate the request five times after 50% of the response time has elapsed. (50% of 120 is 60, so after one hour the customer will have this option available.)

When you finish, just click on the button to complete the process of creating SLA parameters.