Specify Who Can Override Ticket SLA Violation Scheduling
If you enable the rejection of Next Activity scheduling requests if it will result in a ticket SLA violation, you will likely want certain resources in your company to be able to override that, e.g., your service coordinator.
You can do that by giving those users one or both of the following privileges:
- Allow Next Activity After SLA Rights
- Allow Next Activity Ticket Due Rights
This is done via the Users screen in Rocketship Admin.
Related Articles
How to Customize SLA Violation Workflows
This feature is currently disabled in Rocketship for all customers as it was causing some confusion. The SLA violation prediction remains enabled in Rocketship Calendars for users and dispatchers however. If you have enabled the rejection trigger in ...
Specifying Scheduling Alignment for Next Activities
When the Rocketship Next Activity Scheduler finds the best location for an activity, it can be instructed to align the service call on a time boundary (e.g., always on a 5-minute boundary). This is done via the Scheduling Alignment in Minutes ...
Viewing Ticket SLA Violations Predictions
You can view potential SLA violations predicted by Rocketship via any Rocketship calendar. How It Works Rocketship evaluates the workload of your technical resources, capacity, existing ticket assignments and workload estimates (via Next Activities) ...
Rejecting Scheduling that will violate an SLA
The Next Activity scheduling engine can be configured to reject scheduling requests that will likely result in a ticket SLA violation. The ticket being scheduled will automatically be routed to your service coordinator for review and handling. In ...
Escalations vs Scheduling
When using Rocketship, it’s important to be clear that Rocketship can take two actions on a ticket: escalations (ticket routing) and/or work scheduling. It may take one, the other, both, or neither. Let’s work through the scenarios. Note that we have ...