> For the complete documentation index, see [llms.txt](https://docs.bird.com/connectivity-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/connectivity-platform/advanced-inbox-automations-and-routing/sentiment-routing.md).

# Sentiment Routing

In this guide, you’ll learn how to make use of Inbox **Sentiment Routing**.

**Sentiment Routing** is an Inbox feature that allows you to create queues and automatically prioritize tickets based on the [Sentiment Analysis](/connectivity-platform/set-up-inboxs-built-in-automations/sentiment-analysis-for-inbox.md) of a message. You can even make specific tickets go to agents with particular skills, for example, senior agents can probably deal with tickets in which the sentiment analysis is negative (angry customers) better than agents with less experience.&#x20;

Head to the **Routing** page from the sub-navigation and click **Add path**  This will take you to the following modal:

* Keep in mind that only managers can set up **Sentiment Routing**. Go to [inbox.messagebird.com](http://inbox.messagebird.com/), tap **Settings** on the side navigation, select [Routing](https://inbox.messagebird.com/manager/task-routing) from the sub-navigation and click **Add path**. This will take you to the following modal:

<figure><img src="/files/hPEGSNGLSV8LwOyJ8VTW" alt=""><figcaption></figcaption></figure>

* Select **Sentiment** from the **Responsibility** drop-down menu, set **Equals** as the **Condition**, and choose the type of **Sentiment** you’re interested in from the **Expertise** drop-down menu, in our example, it will be **Negative**.

<figure><img src="/files/lrLWZfyxHXGbipVMMnZg" alt=""><figcaption></figcaption></figure>

* Ready? Awesome! To route these tickets into a specific queue, tap **+ Add another step** under **Routing Step**, This will take you to the following modal:

<figure><img src="/files/xRh621I3GIhAufxbuekI" alt=""><figcaption></figcaption></figure>

* Select the queue, in our example, **Negative Queue** and set the time limit in seconds you wish to apply for these tickets, such as 3000 seconds (50 min). Don’t know how to create queues and set agent types? Check out our [Help Center step-by-step guide](https://support.messagebird.com/hc/en-us/articles/360004466518-Routing-setup-workflow-). &#x20;

<br>

<figure><img src="/files/HJoFJMNp9cCXlO74DrOd" alt=""><figcaption></figcaption></figure>

* You can add as many steps as you want. For example, for positive tickets and natural tickets. Once you’re finished, name your routing path by clicking on the pencil next to **New** and hit **Save**. We’ll name ours **Sentiment Routing**.&#x20;

&#x20;

<figure><img src="/files/VeCIngcB8WGODSUvAfIJ" alt=""><figcaption></figcaption></figure>

* Your new path will automatically appear in your [Routing Paths Overview](https://inbox.messagebird.com/manager/task-routing). And that’s it! Now you know how to set use **Inbox Sentiment Routing**.

<figure><img src="/files/WkQ8EWKthZqiaWQ8PgKP" alt=""><figcaption></figcaption></figure>

\ <br>

&#x20;

&#x20;

&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bird.com/connectivity-platform/advanced-inbox-automations-and-routing/sentiment-routing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
