Status of tickets is an important property by which we could filter and sort the tickets. By default, there are four different ticket statuses in Freshdesk:
- Open: Every new ticket that is created in your helpdesk is marked as Open. It means that an agent from your team is yet to resolve the complaint and move it on to other statuses.
- Pending: If the progress of the ticket is awaiting the reply from a customer or any 3rd party, the ticket could be put On Hold using Pending status.
- Resolved: When agents are reasonably sure that they have provided the customer with a solution to their problem, they can change the status of the ticket to Resolved.
Closed: Resolved tickets can be moved to Closed status if the customer acknowledges that the problem has indeed been resolved. If the customer has not replied, the standard practice is to automatically close the ticket (You can use the Supervisor to do this) after 48 or 72 hours.
Apart from these, kindly note that you could add custom statuses to this list of default options which could be useful for your workflow and mapping of tickets.
In addition to the four primary ticket statuses, you can create custom statuses from the Ticket Fields section under the Admin tab. These can be used to customize the workflow in your helpdesk.
For example, you can create a ticket status like 'Waiting on Customer' to indicate that the agent is waiting for information from the customer. At Freshdesk, we use two additional ticket statuses: ‘Awaiting Customer Response’ and ‘Awaiting Developer Fix’, for which the SLA timers are turned off. Likewise, you can also tailor your ticket statuses to bring in your business rules
For every custom status that you create, you get to choose whether to turn SLA timers on or off based on your preferences. An SLA timer is a background clock that starts ticking once a new ticket is created. The SLA timer calculates the time spent in replying, resolving or closing a ticket and equates that with the SLA policies that have been configured based on ticket priorities for your helpdesk. The SLA timer does the work of monitoring each ticket and, if turned on, ensures that the SLA policy is not violated. When you turn them off, all tickets that fall under those statutes will be shown as 'On Hold' in your ticket dashboard.
You have a quick and efficient support team being ninjas and solving customers' issues and they send out a response promptly. When they eagerly await a feedback from the clients on the thread, you would want to group them in a status relevant to this scenario and so you could add a status called "Awaiting Customer response."
Please navigate to Admin -> ticket fields -> Status -> and add one in the dropdown -> as you do not want to violate SLA on a ticket - you could turn this off for this status as you are anyway waiting for them to get back.
We do have a feature called 'Dynamic forms' that allows you to display different fields based on the value chosen for the default Type field. This feature is available only from the Estate Plan onwards.
Please navigate to Admin -> ticket fields -> click on the plus icon next to the dropdown field to add a section. This article will guide you to set this up and give more information as well.
In your ticket form, you would be able to add a dropdown field and make it available for the customers who are raising queries with you. Please navigate to Admin -> ticket fields -> choose this field which is a list icon with an arrow pointing downwards found in the "Drag and drop down" toolbar.
In order to make it available to the customers to edit, please click the field to navigate to the properties. Once there, check all the relevant boxes under agent and customer which includes "customer can edit" option.
Usually, on the ticket fields, you would have given access to the customers to edit a couple of them while submitting a ticket. In order to prevent them from editing this after the ticket creation is generally not possible until we customize it accordingly.
This is possible using the "Portal Customisation" feature which is available only from the Estate Plan onwards.
After a ticket is created, you could edit the ticket from within your Freshdesk Account, if you wish to change the Requester of the ticket, Subject or Description or Ticket Properties. Please click on the more option within the ticket (details page) where the edit option would be part of its dropdown.
This would open the Edit Ticket Details page from where you could edit the ticket and save the changes for it to reflect in the ticket.
Note: This option would not be visible if the ticket is an Outbound Email.
Please navigate to Admin -> ticket fields to see the lock symbol displayed next to some of the options listed there. This is because they are visible only to agents and are not displayed to customers.
Yes, changing the Ticket Field Name would automatically change the Label for existing tickets and the Field would also be automatically updated. Please navigate to Admin -> ticket fields -> click on the field to be taken to its properties window where this change can be made.
However, in the case of drop-down fields, if one of the choices within the drop-down is deleted or edited, the value would not be updated on existing tickets. The value of the field, in such cases, would revert to Null(...).
When a ticket is closed without filling a mandatory Ticket Field, you would receive an error saying "Unable to close __ Required fields were empty". You could click on the Ticket Count mentioned in this error message to update the mandatory fields and close the ticket.
You could also mark the ticket field as non-mandatory by editing the field under Admin-->Ticket Fields.
To do lists are for all of us to track our work and set deadlines for ourselves. When you add a to-do inside a ticket that you are working on, this to- do list is available on the dashboard as well. When this is complete, you could check this in the dashboard which would be reflected inside the ticket as well.
A few things to understand about to- do list are that when you add to-do for someone else who is assigned to a ticket, this would be available in that ticket's details page, however, it would not be available on their dashboard.