---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# On-Call Scheduling subflows

# On-Call Scheduling subflows {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Subflows in On-Call Scheduling enable you to build and configure on-call escalation notification flows.

## Using subflows for on-call escalation {#on-call-scheduling-subflows-overview__section_b1x_xf1_zfc}

A subflow is an automated process consisting of a sequence of reusable actions, data inputs, and outputs. In contrast to flows, subflows do not have a trigger but instead run when called from a flow, from another subflow, or from a script. Compared to workflows, subflows enables you to easily configure channels, and notification and response messages. Maintain, build, and modify your own custom on-call scheduling flows in Workflow Studio with subflows for new instances. The following subflows are available with On-call:

* On-Call: Assign
* On-Call: Assign and Notify
* On-Call: Assign by Acknowledgment
* On-Call: Assign by Acknowledgement per Rota
* On-Call: Assign by Acknowledgement Voice
* On-Call: Check Assignment Response
* On-Call: Conference Call Escalation
* On-Call: Escalations by Email
* On-Call: Escalation By Email per Rota
* On-Call: Time-off approval

{#on-call-scheduling-subflows-overview__ul_bbg_3g1_zfc}Using Workflow Studio, you can build and configure various components such as subflow inputs, outputs, actions, and flow variables such as escalation levels. You can use the contextual comments in the flow designer to help you configure the subflows. For more information on building and configuring subflows in Workflow Studio, see
[Workflow Studio](https://www.servicenow.com/docs/access?context=workflow-studio&version=australia&pubname=australia-build-workflows&ft:locale=en-US)

## Subflows activation and uses {#on-call-scheduling-subflows-overview__section_ydt_dh1_zfc}

Starting from the Zurich release, for the zBoot or new users, On-Call Scheduling uses subflows and workflows are no longer supported.

For existing or upgrade users, in Zurich, your current workflows continue to be supported along with the subflows.

With the migration from legacy workflow to subflows, each workflow has a corresponding subflow with similar name and functional capabilities.

To activate the subflows, you must navigate to AllOn-Call SchedulingAdministrationTrigger Rules and select the subflow for a trigger rule to activate and use the subflow. For more information, see [Create an escalation trigger rule](https://servicenow-prod.fluidtopics.net/vVvAW~y1bVTejok_L7k1ww "Create a trigger rule to specify both the conditions under which an escalation process should begin and the actions (workflow or script) to perform for the escalation.").

For using subflows in Service Operations Workspace (SOW), SOW version must be 8.0 or later.
* **[Subflows installed with On-Call Scheduling](https://servicenow-prod.fluidtopics.net/0b8rqJBmySizV4wv4K5z_w)**   
  Subflows are installed with On-Call Scheduling to support building on-call escalation notification configurable flows.

*[\>]: and then