Grab-and-Go Self Assignment

Grab-and-Go Self Assignment

There is a use case that happens in some MSPs where the person triaging a ticket is also the person who will work the ticket. For example, a resource may answer a customer call, create the ticket, and begin working immediately with the customer.

In this situation, it can be tedious to use a Rocketship Dispatch or Rocketship Forward operation as they are designed for future work. The Grab-and-Go dispatch operation is an alternative that allows the resource that triaged the ticket to immediately begin work.

With Grab-and-Go, the resource only answers two questions:

  • Team. What team are they operating under while working the ticket?
  • Schedule Type. Do they want to override the system default work block that will be created and started?

When a Grab-and-Go operation is performed, the following will happen:

  1. Rocketship will forward the ticket to the resource by clicking ‘Grab-and-Go’.
  2. A Next Activity will be created per the Admin’s default setting.
  3. The Next Activity will be started for the resource.
  4. Any Rocketship workflows for these operations will execute.

This all happens behind the scenes; the resource working the ticket can instantly move forward with work. The benefit of this approach is that the Next Activity work block will track effort by the resource, helping Rocketship to properly allocate timeslots and ensuring service managers are always aware of current work by the team.

    • Related Articles

    • How Rocketship decides tickets assignment

      In Rocketship, the Escalation Engine handles both dispatching (new tickets) and escalations (existing tickets). It’s important to understand how the Escalation Engine decides who should be assigned a ticket. Rocketship is an activity-based solution, ...

    • First Available vs Sticky Escalations

      The Escalation Engine supports several assignment methods, such as First Available, Round Robin, and Least Sticks. However, there are situations where you want recent tickets from the same customer to be handled by the same technician—helping them ...

    • Using Ticket Routing to Automate Dispatch & Escalations

      With Rocketship for Autotask, it is easy to use ticket routing to automate dispatch & escalations. Ticket routing is how you shuffle tickets around – whether it’s a dispatch, which is assigning a ticket to a resource when there’s been no assignment ...

    • Understanding Escalation Methods in Rocketship

      In Rocketship, the Escalation Engine plays a pivotal role in orchestrating the assignment and routing of tickets among different Teams and Resources. To grasp the concept of Escalation Methods, it’s essential to distinguish them from Escalation ...

    • Understanding Recurring Tickets

      The Recurring Tickets engine is robust and scalable. To understand how it works, consider that: A Category is a way to group similar tickets, e.g., Account Management, NOC, Service Manager. A Ticket Template is a written process to be followed, ...