Updating the Autotask Ticket Due Date when creating Service Calls
Updating the Autotask Ticket Due Date when creating Service Calls
Rocketship supports updating the ticket due date when creating service calls (via Fixed Appointments and Next Activities, known as Firm and Tentative Appointments for Sealevel Operations/Pax8 Academy customers) via Workflows. Additionally, you can trigger ticket due date updates via any Workflow, not only the ones used by Fixed Appointments and Next Activities.
You may want to update the Ticket Due Date based on some action you perform in Giant Rocketship, e.g., when you schedule a new Next Activities, you may want to update the Ticket Due Date. This can be done using Workflows. A Workflow can perform these ...
Rocketship is designed to “own” Service Calls for support agents. That said, there are times when Rocketship will import Service Calls from Autotask rather than being the source of those Service Calls in Autotask. When you manually create a Service ...
The Service Call Monitor allows you to trigger Rocketship Workflows based on conditions related to a service call. This is especially helpful for scenarios like flagging overdue appointments or taking action on service calls that are running long. ...
Rocketship supports creates/updates/deletes of Service Calls by 3rd party software. This KB describe that interaction. How We Find 3rd Party Service Calls Service Calls creates/updates/deletes can come from one of three places: Rocketship Autotask ...
When creating Escalation Rules, you will define Ticket Criteria to match a ticket against an Escalation Rule. How to test Ticket Criteria The best way to test Ticket Criteria, i.e., to check which Escalation Rule will match a given Autotask Ticket, ...