Setting High Priority level for Customer responded tickets
When a customer replies to a ticket, you want to respond quickly. Rocketship supports that by allowing you to automatically create a Next Step when a ticket changes to Customer Responded. Further, you can configure Rocketship to set the Next Step as a High Priority Appointment so that your technician works it first.
- Login to GRS admin
- Navigate to Schedule
- Find Next Steps
- Find Customer Responded
- Edit customer responded
- Set Priority level to High and save
This part tells the system to schedule the next step shortly after the customer replies automatically.
- Go to Ticket Lifecycle > Settings.
- Find Customer Responded and edit
- Under action, choose schedule next step (No Duplicates)
- On Next Step Rule > Set it to Customer Responded - 0.25 hours. Then hit save.
Related Articles
How to Define Escalation Rules Specific to a Customer Group
The Escalation Engine in Rocketship is versatile in that you can build out very specific workflows for helpdesk, NOC, co-managed, VIP customer accounts, etc. First, let’s remember that the Default Rule is your “catch-all” rule and should handle the ...Using SmartTag to Set Ticket Title
SmartTag can do more than classify tickets. It can also update ticket fields to make them more appropriate for helpdesk use. This behavior is managed in the Ticket LifeCycle screen. Configuration Options When configuring SmartTag, you can set the ...Creating Recurring Tickets
Every Recurring Ticket Rule has a name and is associated with a Category and Ticket Template. Note, because a Ticket Template may have multiple Recurring Rules, each rule has its own name. By creating a many-to-one relationship between Rules and ...How to close tickets while Bulk Closing Related Service Calls
In general, you can rely on Autotask to automatically close Service Calls if you set a Ticket to Complete. (You can read how to enable that setting in Autotask here.) However, you can also use Rocketship to bulk close Service Calls while completing a ...Why does the same Autotask Resource keep getting escalated tickets?
If you have a ticket routing rule that manages an escalation and you find that the same team member keeps getting assigned escalated tickets, there are a two common reasons why: Other team members are blocked due to external appointments. No ...