Mark a Resource as Unavailable for New Tickets

Mark a Resource as Unavailable for New Tickets

In Rocketship, the Escalation engine will bypass any Resource that is set inactive. This can be useful in scenarios where a Resource is sick, on extended leave, etc.

This can be done via the DispatchBoard by a service coordinator.

  1. Log in to Autotask
  2. Go to your Rocketship Dashboard widget
  3. Go to the DispatchBoard
  4. Click on Manage->Resource
  5. Click on “Set Inactive” on the relevant Resource

Once set to Inactive, Rocketship will stop dispatching/escalating tickets to this resource.

Accessing the Manage Resources screen via the Rocketship DispatchBoard.

    • Related Articles

    • Stop a Resource from getting some tickets but not others

      There are times you want a resource to stop getting tickets in some situations while getting tickets in others, at the same time. For example, let’s say you have a tech who is going on a two-day vacation. You do not want them getting any helpdesk ...

    • 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 ...

    • Mark a Resource as Unavailable for New Tickets

      In Rocketship, the Escalation engine will bypass any Resource that is set inactive. This can be useful in scenarios where a Resource is sick, on extended leave, etc. This can be done via the DispatchBoard by a service coordinator. Log into Autotask ...

    • How do I handle technician’s going to lunch?

      If you have a helpdesk where you want a tech to stop getting new tickets while they are out to lunch, we recommend you use the In/Out feature. Note, we would argue that for a tier 2+, you would not normally log them in/out for a short time away from ...

    • Stop a Resource from getting some tickets but not others

      There are times you want a resource to stop getting tickets in some situations while getting tickets in others, at the same time. For example, let’s say you have a tech that is going on a two-day vacation. You do not want them getting any helpdesk ...