---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Add decision nodes

# Add decision nodes to a sequence {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Activate the next stage in the playbook based on the outcome of the previous stage by adding decision nodes while creating or updating a sequence.

## Vorbereitungen

Hinweis:  
Decision-based stages and the demo data are available only starting with Playbook version 28.3 on the Zurich release. The sample Lead nurturing tele-sales sequence available with the demo data shows how to configure a decision-based, telesales sequence with the schedule call activity.

Delegated developer roles must be assigned to designated users. For more information, see [Grant delegated developer permissions for managing sequences](https://servicenow-prod.fluidtopics.net/XVQRqcqtcAClAOfQR1unEQ "Assign delegated developer roles to designated Customer Engagement Sequences users so they can create and manage sequences without needing a system admin role.").

Role required: sn_crm_sequence.admin, sn_crm_sequence.writer  
Hinweis:  
If you're using Customer Engagement Sequences 1.0.0, you need the playbook.admin or pd_author role to create sequences.

## Prozedur

1. Navigate to WorkspacesCSM/FSM Configurable Workspace.
2. Select the List icon .
3. Navigate to SequencesAll Sequences.
4. Select a sequence that you're creating or updating.
5. In the sequence diagram, hover over the object that you want to insert a decision activity next to, and select the icon to add an activity.
6. Select the Add a decision icon ![]().  
   A decision is added with two branches and the Decision properties side panel opens for configuration.
7. Under the Details tab, enable the Start with delay option to add delay between the two call attempts.  
   For example, if you want the agent accessing the workflow to wait two days before calling the prospective lead or customer again, you would set Duration type to Explicit duration and set Days to <kbd class="ph userinput">2</kbd>.  
   For more information, see [Start with delay input properties](https://www.servicenow.com/docs/access?context=start-with-delay-properties&version=australia&pubname=australia-build-workflows&ft:locale=en-US).
8. Under the Branches tab, expand New branch and enter a unique name for the branch in the Branch label field.
9. Select Add Condition.  
   For example, to execute the branch when the outcome of the previous call attempt was unsuccessful, you would set the condition \[Schedule call \> Output \> State\]\[is\]\[Cancelled\].  
   For more information, see [Decision activities](https://www.servicenow.com/docs/access?context=create-a-decision-activity&version=australia&pubname=australia-build-workflows&ft:locale=en-US).
10. Select Save and close.
{#add-decision-nodes-sequences__steps_r2q_2qs_ghc}

## Nächste Maßnahme

Add a stage for the new branch you created earlier, and repeat the steps to add more activities as needed. For more information, see [Add and configure a stage in a playbook](https://www.servicenow.com/docs/access?context=add-configure-stage&version=australia&pubname=australia-build-workflows&ft:locale=en-US).
**Zugehörige Informationen**   

* [Decision stages](https://www.servicenow.com/docs/access?context=create-decision-stage&version=australia&pubname=australia-build-workflows&ft:locale=en-US)