Freshdesk Status

 
This document is prepared to explain various statuses configured in Freshdesk for SOLVAY. Through this document you will be able to understand which status should be used at basic situation.

List of the statuses available in Freshdesk are:

  1. Open
  2. Pending
  3. Need for more information
  4. Waiting on Third party
  5. Transferred
  6. Transferred to CM
  7. Resolved
  8. Activities before closure
  9. Closed

P.S: All are explained according to the best practice in this document.

Open:

  • If ticket is new, automatically assigned status to Open.
  • Any ticket created will be in Open status i.e. ticket is not acknowledged yet by any agent.
  • A ticket is assigned to a group. Dispatcher of that group can assign among the available agent based on the skill/domain. It is an agent's responsibility to change the status of the ticket further as required.

Pending:

  • If ticket is assigned to a Group, Agent. Pending status is updated.
  • Pending status in Freshdesk means "Work in progress".

  • After a ticket is dispatched to L1 queue, an agent should acknowledge the ticket by changing the ticket status to Pending status. This means, a ticket has been acknowledged and an agent is working on the ticket.
  • The change in status can be done either in ticket dashboard or in ticket properties after opening a ticket.

 

  • Ticket properties:

 

  • Freshdesk SLA:

Need for more information:

  • Ticket was answered and agent waits for request from the user.
  • While working on the ticket if an agent feels like they need more information on the issue from user then status should be updated as "Need for more information" and should send a reply to user.
  • As soon as the user replies to email, Freshdesk will pop up a status saying user has replied. This will be applicable if the user is able to communicate in English.
  • If any language translation is required then the ticket status needs to be changed as Need for more information and send that ticket to L0, by changing the group.
  • Click on Reply button, and write the content, and click on send button and set status as "Send and set as need for more information".



  • This activity will be popped up in activity list of ticket.

  • Ticket status has been changed as Need for more information

  • This will stop the clock in Freshdesk.

  • User will receive an email like below

**

 

  • Ticket Dashboard will look like below:


  • As soon as the user responds to the ticket a status will pop up as customer responded in ticket dashboard.


  • And status will change as Pending by freshdesk automatically.

Waiting on Third party:

  • Ticket was transferred to entity external to applications (vendor, supplier, infrastructure)
  • This status will be updated when ticket is transferred to external entity.

Example Vendor, SAP, Supplier etc.

  • To update the ticket into status "waiting on third party", we need to change the status in ticket properties tab and update the ticket.

Transferred:

  • When a ticket is transferred to specific groups and must be signaled like that. Used in specific processes (e.g. HtR) no agent is assigned.
  • When a ticket is transferred to specific groups they must be indicated like this.
  • We use this option, when we are transferring tickets from one group to other.

For example:

  • A ticket is with IS-CGI-L2-Techno, an agent who is working on the ticket feels like they need information from functional team, a ticket can be transferred to IS-CGI-L2-OTC.
  • When the ticket is transferred the status should be changed to "Transferred" and change the group name.

Update the status:


 

  • Change the group name:

Transferred to CM:

  • When a ticket is transferred to Solman/other change management tools in use - e.g. OtC CRM - PMO Toolkit
  • When a ticket is transferred to change management system the "Transferred to CM" status is updated
  • This will stop the SLA clock in freshdesk.

  • This will update the ticket as below

Activities before Closure:

  • When a resolved ticket requires some additional actions before closure. Example: it needs to be translated to requester's language.
  • When a resolved ticket requires some more additional actions before closure then we will keep a ticket in this status.

Example:

A ticket needs to be translated to requester's language.

Resolved:

  • Used when a solution is found and proposed to user. May be closed automatically.
  • If a solution is found by an agent, the detailed solution will be proposed to the user by resolving the ticket.
  • By replying the solution to a user and update a status as "set a status as resolved".

  • User will receive an email on resolving the ticket.

Closed:

  • Closed tickets

A ticket can be closed in 3 ways are:

  • By user
  • By agent
  • Auto closed

    By user:
  • User can mark the ticket as closed from customer portal after a solution is proposed by agent.
  • When an agent finds a solution, they should reply to user and mark the ticket as resolved.


  • After a ticket is resolved, ticket looks like below in dashboard

  • When a ticket as a status "resolved", user will receive an email communication from freshdesk, stating the ticket has been resolved.

  • User can view the list of ticket and their status in customer portal of user. User will have an option on right hand side of the ticket to "Mark the ticket as closed".

  • When the user mark the ticket as closed, user will get a below pop up.

  • This will also trigger an email notification to user, like below.

  • On agent's portal, the ticket looks like below in ticket dashboard.



By agent:

  • An agent can also change the ticket status to closed, if the user confirms that provided solution is useful.


Auto closed:

  • If the ticket is not marked by user as closed and if agent also have not marked ticket as closed, then fresh desk will mark resolved tickets as closed after "defined days" in system.

Example:


If the ticket is not marked as closed within 5 days, all resolved tickets will be marked as closed after 5 days.