When dispatching a ticket via Rocketship, you may need to do more than a single operation. That is, instead of just “dispatching to a tech,” you may need to dispatch the ticket, email the customer, set the ticket to Waiting Customer, etc. To assist with that, Rocketship allows you to customize how it processes a dispatch.
Normally, this is how Rocketship will operate:
However, during dispatch, you can skip/bypass steps #4 and #5 entirely. This allows your dispatcher to “dispatch” the ticket but also perform other actions without actively scheduling the resource.
For example, if your dispatcher wanted to dispatch a ticket, send the customer a ticket note, and set the ticket to Waiting Customer without creating an unnecessary Next Activity, they would: