Ticket Details
Manage ticket data, conversations, related tickets, SLA timers and work time. The instructions also cover merging tickets, subscriptions, files, document templates and internal notes.
Click a ticket in the Dashboard to open ‘Ticket Details’. This view also opens after you create a ticket.
The right-hand ‘Details’ section contains “Ticket number”, “Company user”, “Company”, “Phone number”, “Status”, “Ticket relation type”, “Assignee”, “Queue”, “Assets”, “Ticket type”, “Service”, “Priority”, “Reminder”, “Age”, “Estimation” and “Spent time”. Use beside “Company user” to add or change the Company or Customer.
The button at the top deletes the ticket. The two buttons beside it switch between tickets.
Merge tickets
An administrator can enable or disable this function in Settings => General => Tickets.
Merging combines two tickets. All articles and files move to the selected destination ticket; only the history remains in the source ticket. Only an agent can merge tickets, while a customer can view the details. A ticket that has already been merged cannot be merged again.
The following example shows how to merge tickets.
A customer submits a ticket about a keyboard problem.
The customer then submits a similar ticket about a mouse problem.
Now, there are two tickets in the system regarding a similar issue.
You can merge the tickets into one case.
Open the source ticket first. Its articles and attachments will move to the destination ticket. The merge button is in the top right corner of ‘Details’.
Click Merge to open the ticket selection window.
Filter by queue or ticket type, adjust the columns or use the search field to find the destination ticket. Select its checkbox in the table; only one destination can be selected. Click Save at the bottom of the window to display the confirmation:
Click “Yes” to start merging. “No” cancels the operation and returns to the selection window. After merging, the destination ticket opens. Articles from the source ticket should appear in creation-date order. Attachments should appear both in the articles and in the Attachments view, opened with the paperclip icon.
The ticket history records the merge and the number of the merged ticket.
In the source ticket, fields such as Status, Queue and Ticket type are locked. Its history remains available and identifies the destination ticket.
Upper sidebar
Click to open the ticket history. It records changes to the ticket type, service, queue and other fields.
Agents can change most ticket details, unlike customers. You can add assets or relate the ticket to another ticket about a similar problem, request or question.
Click either option to search for an asset to add or a ticket to relate. The following window shows the asset search.
The related-ticket search works similarly. Tickets can be filtered by Queue or Ticket Type, while assets use Categories.
Use Ticket relation type to choose how two tickets are related. Three options are available:
- Related
- Parents
- Subtasks
After selecting which option you want to link, you need to select the ticket you want to relate.
The effect of linking several tickets:
Set a “Reminder” to receive a notification in MINT and by email on a chosen day and time.
You can add a note to the reminder, such as the next action to take.
The note will be displayed in ticket details
You can also estimate the time needed to close the ticket.
To estimate the time, enter appropriate values in the “Time estimation ..” field and press the button
An agent can record time spent resolving a ticket.
In the Spent time… field, the agent enters how much time he spent on resolving the request. In the next column, a day is selected from the calendar. If you want to add a description, you can do it in the Description… field. The last thing you can add is Spent time type which is set in the admin panel. To add the time spent, click on the button.
After the number in Estimation time… or Spent time…, enter one of these unit letters:
- w: weeks
- d: days
- h: hours
- m: minutes
An agent with the “Work time coordinator” role permission can record another agent’s work time in a ticket.
Below the ‘Details’ section, you will find the ‘SLA timeline’ section showing interactive counters (with progression bars) with time left for e.g. responding to the client or for resolution of a problem. Those timers are refreshed each second and progression bars are filling up. Once any of them is full (or close), the right person (depending on Admin choices made in the Services section) will receive a notification. It can be you or any other agent.
A ticket created by a customer in Mint or from an email waits for an agent to be assigned.
When you open such a ticket, you will see three timers, or another number configured by the administrator.
When you assign yourself to a Ticket those timers will not change or stop. However, when you write any message to the Customer, even a simple ‘Hi’, two of those timers will disappear (‘Response time’ and ‘Update time’).
The only timer that stays until the problem is fixed and the ticket is closed is ‘Resolution time’ which shows the time limit before SLA conditions will be broken.
If the Ticket state will be changed to the one which has also a ‘Stop SLA’ option activated (see ‘Admin>Tickets>Statuses) the SLA timer will be stopped.
Once the ticket Status is set back to one that has no ‘Stops SLA’ option enabled, the timer will be running again and counting ‘Remaining’ time down.
If the timer expires, you receive a notification if the administrator has configured one. The timer also changes to the appearance shown below.
Additional attributes below ‘SLA timeline’ depend on the selected Ticket Type. Administrators create and manage them in Admin > Tickets > Custom fields > Tickets structure, described later in this guide.
Below Details, agents can see Knowledge Base topics that may help resolve the customer’s problem. Customers do not see these suggestions in this view. An empty section means that no topics matched the ticket description.
Click a Knowledge Base topic to open its details.
The main area of Ticket Details contains the messages and communication history.
Messages can be displayed in a framed or chat view by selecting one of them . The button responsible for that is located at the top part of the view.
Chat is the default view. Switch to framed view with to see a list of messages, then click a message to expand its details.
The next two buttons next to chat/framed view: are used for ‘Notifications timeline’ and ‘Subscribing/Unsubscribing’ the ticket.
Click to open the notification history for this ticket. Click to load earlier activities.
The second one, once activated () will send notifications each time something new happens within the ticket.
The behaviour of the button when clicked depends on the option selected under ‘Subscription management strategy’ in ‘Admin’ > ‘Settings’ > ‘General’ > ‘Tickets’
With the ‘Allow assigning only yourself’ option selected, You subscribe only yourself to the ticket by selecting the button.
With ‘Allow agents to assign other agents’ selected, an agent can also subscribe other agents to the ticket.
Click ‘Subscribe someone else’ to open the selection window.
Choose users from the list.
Add them with the arrow button. The selected agent appears below.
If you subscribe yourself, your account also appears in the list.
Use the button shown below to unsubscribe another user.
With ‘Everyone can assign everyone’ selected, you can subscribe yourself and other users, including agents and customers. This setting lets customers see the list of all agents in the system.
Subscribing users is similar to subscribing in the “Allow agents to assign other agents” option (above).
Three more buttons provide file and document functions.
The button opens the File Repository.
The File Repository stores MINT application documents. Available actions depend on the user’s access level. Agents can pin files from “Buckets” to tickets and download them.
Click to open the tab with Pinned files on the left and All files on the right.
All files contains the buckets and files uploaded by an administrator. Pinned files contains the files an agent has attached to this ticket from All files.
To pin a file, click its bucket to expand it.
Select the checkbox beside the file. The button appears.
Click to add the selected files to Pinned files. They become visible to the customer assigned to the ticket.
Click to unpin a file. The following confirmation window opens:
Downloading files
Click a pinned file to download it. For files smaller than 20 MB, a “Downloading started” notification appears.
For files larger than 20 MB and smaller than 1 GB, “Preparing the file” appears before “Downloading started”:
For files larger than 1 GB, clicking the file opens an information window:
Click “Download” to open the next window:
The Close button appears when the download finishes:
The button opens Attachment View.
This view lists all files connected to the ticket: standard attachments on the left and inline attachments on the right. Click a file to download it.
The printer button exports the ticket content to a .pdf file.
Click on this button and you will see a small list with two options: Extended and Standard.
Choose a format to open the system file dialog. Select a destination and click Save to save the .pdf file, then open it from that location.
The .pdf file contains the agent-customer conversation and ticket information, including the owner, current status and assigned agent.
The ‘Extended’ .pdf also includes system messages, such as priority changes or agent assignments. The ‘Standard’ version omits these messages.
Another button () can be used by the Agent for creating a new Ticket during a conversation with the Customer.
If another problem arises while you are helping a customer, you can create a new ticket automatically related to the current one.
To do so click on the () button and select ‘Empty’ or ‘Inherit values’ from the menu.
‘Empty’ under Related opens the standard ‘Create new ticket’ view. Complete the required information and create the ticket; it then appears in ‘Related to:’ in Ticket Details. ‘Inherit values’ opens the same form with “Company”, “Company user”, “Subject”, “Ticket type”, “Service” and “Assign to queue” already filled in.
Use the same steps to create a Parent or Subtask ticket for the current ticket.
The last button () is used for generating a document.
The function uses ‘Document templates’ added by an administrator and replaces their placeholders with ticket data. For example, you can generate an offer requested by a customer.
To generate a document you need to click the button and from the dropdown menu select the document template you want to use. If you don’t see any positions here it means that the Admin user has not created any document templates.
Select a template, choose a location on disk and save the file. Its placeholders are replaced with data from MINT Service Desk.
Values inserted in place of placeholders are shown in bold.
The following example shows the offer template before its placeholders are replaced.
The whole process of creating Document templates and using Placeholders is described in the Admin > Tickets > Document templates part of this guide.
The generated document contains data in place of the placeholders. Ask your Mint SD administrator to add any other document templates you need.
You can print the completed document or send it to the customer as an attachment.
The chat area contains the ticket conversation.
Long chat messages are shortened. Click to show the full text.
Type your message in the text box and click to send it.
As an Agent, you can send messages in three ways.
Use “Email channel” to communicate with a customer through their email account rather than MINT Service Desk. You can add CC recipients to receive a copy.
Use “Customer portal” to communicate with a registered customer using MINT Service Desk.
Use “Internal note” for notes about the ticket. Customers cannot see these notes.
In all cases, you can format your message by using the text editor, which will be displayed once you click on the ‘Enter the message…’ field.
Click to send the message. It then appears in the chat.
Select “Private note” at the bottom to send an internal message visible only to agents. Customers cannot see it.
Clear this option before sending a message to the customer. Otherwise, the customer cannot see it.
You can attach files, such as pictures, and use a custom response template instead of repeatedly typing the same message.
Click ‘Custom template’ and in the ‘Choose template response’ select one from the list. Remember that in order to see any of them on the list they need to be first created by the Admin and marked as Custom templates (not system ones) and with the right queue attached. See the ‘Admin>Tickets>Templates part of this guide for more details.
Once you selected the template its content will be loaded right below your selection.
Click Save to load the text into the Rich Text editor. You can edit it before sending.
Use ‘Add signature’ to attach a signature before sending the message.
After pressing this button, the agent will be taken to the signature selection.
Selecting a signature displays its preview.
Select ‘Set as default automatic mail signature for this queue’ below the preview to include this signature in emails automatically.
To add the selected signature to the application, press the button.
To cancel adding a signature press button.
To remove the signature preference, press button.
Use ‘Attach document’ to add a document based on a template from Admin > Tickets > Document Templates before sending the message.
Click on the ‘Attach document’ located at the bottom of the communication section inside the ‘Ticket details’ view.
Inside the ‘select document template’ window select the document template you want to use and click Save.
The document’s placeholders are filled with data, and the file is attached to the message without being sent. Add your message and send it with the document to the customer.
To check the document before sending it, click the attachment thumbnail, save the file to disk and open it.
Use ‘Select survey’ to attach a survey before sending the message.
Click on the ‘Select survey’ located at the bottom of the communication section inside the ‘Ticket details’ view.
Choose which survey you want to select and click the button. For more information about the survey check Admin Portal - > Surveys in this documentation.
To keep a document for internal reference, switch to “Internal note” and attach or send it there. You can see it, but the customer cannot.
Click ‘Reply’ and you will see a new internal message.
You can download the document here later to check the offer sent to the customer.
To discuss an internal message with other agents, click ‘internal discussion’ beside it and enter a comment in ‘Talk to another agent’.
The discussion keeps replies together instead of adding separate private messages to the main chat.
When you reload the view or come back to the ticket after some time, you will notice that internal discussions are hidden. In order to see them, you need to click on the link.
Each article or message has icons beside it.
Click the top icon to see details such as the communication channel and author. The second icon indicates that the message was sent by a system user.
Pressing the third button will display a preview of the article.
The last button exports the selected article to PDF. The similar button at the top of the ticket exports the whole ticket.
When a new message or system notification is waiting, the sidebar shows a notification. On opening Ticket Details, you also see the following message at the bottom of the chat.
Click ‘See’ to read the new messages, or mark them as read.
For long articles, the Show more, Show less, and Expand all buttons are displayed.
Clicking Expand all expands the entire article, allowing you to view all of its content without the need to scroll. There is also Fold button appeared after clicking Expand all:
Clicking Show less collapses the article to a few lines:
Clicking Show more expands the article to several dozen lines and enables scrolling through its content:
A new ticket waits for someone to be assigned to it. Sending a message in its chat as an agent automatically assigns it to you. You can also select yourself in “Assignee” under “Details”.
In both cases, an internal message appears in the Ticket Details conversation.