HOWTO Close Tickets while Bulk Closing Related Service Calls

HOWTO Close Tickets while Bulk Closing Related Service Calls

In general, you can rely on Autotask to automatically close Service Calls if you set a Ticket to Complete. (You can read how to enable that setting in Autotask here.) However, you can also use Rocketship to bulk close Service Calls while completing a ticket (or at any other time).

Let’s walk through the Workflow for this:

  1. Create a new custom Workflow “Close Ticket & Service Calls”
  2. In the editor, click on Service Calls
  3. For Bulk Close, set “Ticket Service Call Close All” to enabled.
  4. Click on the Tickets tab.
  5. Set Resulting Ticket Status, set to Complete
  6. Click on the Publish tab.
  7. Enable Publishing
  8. Enable: Require Note
  9. Click Submit

This Workflow is now published to your team.

In the Ticket Insight, if you trigger this Workflow, it will force the user to enter a note, and then the Workflow will close the ticket and all open service calls associated with the ticket.

Note: Workflows are queued, so it may take a few seconds.



    • Related Articles

    • Configuring How We Route Imported Autotask Service Calls

      Rocketship is designed to “own” Service Calls for support agents. That said, there are times when Rocketship will import Service Calls from Autotask rather than being the source of those Service Calls in Autotask. When you manually create a Service ...

    • Using the Service Call Monitor to Trigger Rocketship Workflows

      The Service Call Monitor allows you to trigger Rocketship Workflows based on conditions related to a service call. This is especially helpful for scenarios like flagging overdue appointments or taking action on service calls that are running long. ...

    • How long does it take for Rocketship to show imported Service Calls?

      Rocketship supports creates/updates/deletes of Service Calls by 3rd party software. This KB describe that interaction. How We Find 3rd Party Service Calls Service Calls creates/updates/deletes can come from one of three places: Rocketship Autotask ...

    • Mass Accepting Service Calls During Onboarding

      During the onboarding process, especially if you are using the SeaLevel/Pax8 Academy “pending acceptance” concept for Service Calls, you may need to mass accept the imported Service Calls we find during the onboarding process. That’s because some ...

    • Using the Service Call Monitor to Trigger Rocketship Workflows

      The Service Call Monitor allows you to trigger Rocketship Workflows based on conditions related to a service call. This is especially helpful for scenarios like flagging overdue appointments or taking action on service calls that are running long. ...