> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/contact-center-configuration/building-your-callflow/via-dialogue-studio/set-priority-node.md).

# Set Priority node

Reference for the Dialogue Studio Set Priority node, its 0-3 scale, phase restrictions, and documented Unify connect-model scope.

{% hint style="warning" %}
Set Priority sets the current dialogue's priority from 0 (lowest) to 3 (highest), with a default of 1. The routing engine uses this setting for Unify sessions only, in the Incoming call and Waiting Queue phases. It is separate from AI Priority Analyzer.
{% endhint %}

![Set Priority node icon](https://2382362027-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgIhRKIrtrwqPt8cNlAy6%2Fuploads%2Fgit-blob-415522b9b3aafb3be344bdd64bf3d418165ad480%2Ffdf18cf820eeeee4.png?alt=media)

The Set Priority node changes the priority of an incoming call using a value from 0 to 3.

### Details

This node sets the priority of the current dialogue, assigning a level from 0 (lowest) to 3 (highest). The default priority for dialogues is 1. The routing engine uses this setting for Unify sessions only.

The node is supported in the Incoming call and Waiting Queue phases.

### Configuration

* **Priority** (*dropdown*) - Select the priority level for the current dialogue: **0 - Low**, **1 - Normal**, **2 - Priority**, or **3 - Emergency**.

### Output

* **msg** (*object*) - The input message is forwarded unchanged.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/contact-center-configuration/building-your-callflow/via-dialogue-studio/set-priority-node.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.