--- title: Add Guided Decisions to playbooks description: Add decision trees created using the Guided Decisions Experience application to a playbook, so customer service agents can work through it to resolve cases more efficiently. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/customer-service-management/add-guided-decision-playbook.html release: australia topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Configuring guidances and decision trees, Guided Decisions configuration, Agent tools, Organize agent workspaces, Configure, Customer Service Management] --- # Add Guided Decisions to playbooks Add decision trees created using the Guided Decisions Experience application to a playbook, so customer service agents can work through it to resolve cases more efficiently. ## Before you begin Role required: admin, pd\_content\_author ## About this task A playbook is set of steps that defines a process. A decision tree can be added as one of the steps within a playbook. Playbooks are displayed in cases on Agent Workspace based on trigger definitions defined for each playbook in the Process Automation Designer. For more details, see [Process Automation Designer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/process-automation-designer.md). Based on the context of the case the customer service agent is working on, the playbook and any associated decision trees are displayed. For more details on playbooks for Customer Service Management, see [Playbooks in Customer Service Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/setting-up-csm-playbooks.md). ## Procedure 1. Navigate to **All** > **Process Automation** > **Process Automation Designer**. Playbooks opens in a new tab. 2. Select the process you want to add the decision tree to. 3. Select **Add activity**. 4. Select **Guided Decisions Experience** > **Guided Decisions**. 5. In the Details tab, fill in the basic details of your activity.
| **Label** | Unique name for your activity. This name appears in user-facing views of your playbook. |
| **Description** | Description of your activity. |
| **Run condition** | After the activity starts, the activity runs only if specific conditions are met. |
| **When to start** | Options when your activity must start:- **After Previous**: This activity starts when the preceding activity has a state of Skipped or Complete. - **Immediately**: This activity starts when its stage starts running. Your activity doesn't depend on the state of any preceding activities. - **With Previous**: This activity starts when the immediately preceding activity starts running. |