Melampaui dasar-dasar Easy Redmine: Membuka potensi HelpDesk

Automatic ticket follow up

Are you having trouble with stale and passive tickets? Or would you like to get feedback after the ticket is solved? Say no more! These and other use cases can be easily covered via Automatic updater. 

You can set it in your Project >> Settings >> HelpDesk

This section allows you to set a current status and time without any update to avoid updating live tickets.

Then you select the action of what should happen such as change status, assignee, and/or send an email from a template to the Client.

Since the automatic updater is configured per project, you can design various processes based on product, client level, and region – however, your tickets are sorted into various projects.

Naturally, in these emails, you can share relevant info about the ticket such as ID, link, ticket owner, priority, subject, or date of last update. This way the message can provide your Client with information they may have not been aware of or something they may need.

Use cases for smooth ticketing 

Here we prepared a couple of use cases of how to use this neat feature to make your work easier.

Rate your experience

• Current status: The ticket resolved
• Wait 2 days
• Send an email containing a link to NPS, or another customer survey about their experience with your services
• Change status to Ticket closed

Ticket closing chain

• Current status: Waiting for reply
• Wait 7 days
• Send email follow-up about a question you need to get answered to be able to solve this issue
• Change status to Follow up sent
• Wait 5 days
• Change status to Ticket closed

The ticket was stalled by a support agent

• Current status: In progress
• Wait 4 hours
• Change assignee to Stan the Man(ager) to escalate and highlight that a ticket is in progress for too long without a notification to the Client.

Tireless follow-up

• Current status: Feedback required
• Wait 1 day
• Send emails such as: Please send us feedback, it is crucial to solve your problem.

As you can see, there is no status change. What this will do? The system will send a follow-up email every day as long as the ticket remains in this status. Unless the Client replies or someone manually changes the status, it will be sending emails till infinity. Sounds extreme? Maybe. But it may happen that you encounter a situation when this is needed.

What to keep in mind 

By now, you have probably already thought of many cases of usage. Before you implement them, make sure to check these notes to prevent any undesirable effects.

1/ Wait time is counted from the last update of the task

The last update means any change in the ticket = attribute change or comment. If you think the ticket should have been automatically updated, but wasn't, please check the History for all changes. Maybe there was an attribute change that reset the wait time.

2/ Don't forget to “change status”

We strongly recommend changing the status during an automatic update. There may be situations when a perpetual following up is desired (Use case D), but in regular cases, the status should be changed to move the process toward a resolution (use cases A, B, C).

3/ Verify statuses after the Client reply

Especially in cases when you are asking for a reply, you should be aware of what ticket status will be set after the Client sends the reply. Be careful and avoid any follow-ups for this status – the Client did what you asked him for.

The status after the Clients response is in HelpDesk >> HelpDesk settings >> Change status after the client's response to

Conclusion 

Now that you've learned the secrets of automatization, you can use your HelpDesk to its full potential. With setting up automatic actions you can be more efficient and you'll save some precious time that can be used elsewhere – maybe as your coffee break!