Away Schedules provide a way to manage the availability of your resources by marking them as unavailable during specific periods. This feature is essential for accurately maintaining your team’s capacity and ensuring tickets and tasks are assigned to available resources only.
Away Schedules indicate to the Escalation Service that a resource is Unavailable, and thus not eligible for ticket assignment. If you want a resource to show as Available for ticket assignment, but busy for a certain day/time each week, instead use Rocketship’s Recurring Schedules. Additionally, if you want a resource to “toggle” as available/unavailable for a certain Tier within an Escalation Rule, e.g., only being Available after-hours, then use Scheduling Constraints.
The Escalation Engine automatically excludes resources marked as away from ticket assignments. This ensures no new tickets are assigned to an unavailable resource.
The Scheduling Engine treats resources marked as away as busy for the duration of the Away Schedule. This means that even if an Away Schedule is not open ended, the resource may not be assigned new tickets because they appear too busy for the given timespan. That said, the Scheduling Engine may still find time slots before/after the Away Schedule to schedule work.
This creates an “open-ended” Away Schedule for the resource and is the best way to flag a resource as “Out Sick”.
This is used to define both the start and end dates.