> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/appendix/skills-based-routing/queue-skills.md).

# Queue Skills

Navigate to Queues & IVRs | Queues | Select queue | Edit | Enable Skills Routing | Select Routing Type.

Routing types for Skills:

| Routing Type | Description                                                                                                                                 |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Serial       | Alerts are sent to agents based on best match to least match. In case of equal agents, they are alerted in a system generated random order. |
| Longest Idle | Alerts are sent to agents based on best match to least match. In case of equal agents, they are alerted based on longest idle.              |

Navigate to the skills tab | select the required skill category(s) | On a scale of 1 - 1000, set the level of importance for each skill category in the field below each category.

{% hint style="info" %}
More than one skill category can be set to a high level of importance. For example, you would like to route all calls to an English speaking agent in the sales department.
{% endhint %}


---

# 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://cc.docs.landis.cloud/appendix/skills-based-routing/queue-skills.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.