> For the complete documentation index, see [llms.txt](https://support.closer.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.closer.app/guide/getting-deeper/set-up-skill-based-routing.md).

# Set up skill-based routing

### Add routing tags to customers

We’re giving to your disposal a powerful and flexible system of matching new customers with the appropriate advisers in your team. Just use the tag parameter in the **closer.identify** method to describe which team this customer should be routed to.

```
closer.identify({
  tag: "example",
});
```

Currently, customers can have one tag assigned.

After you’ve added routing tags to your customers based on their context, you should add skills to your team to enable routing.

### Define your team’s skills

Skills are used in conjunction with customer routing tags. When tag is matched with skill, routing is directed to that person(s). Add skills of your team in the [Admin / Assignment rules](https://closer.app/dashboard/settings/assignment-rules) section. Advisers can have multiple skills.

![Skills management](https://storage.googleapis.com/helpdocs-assets/j77potoidz/articles/vc1soyire4/1560434104164/skills-management.png)

### Routing rules

New customers with a tag will be distributed between **available** advisers with the matching skill, until they reach their chat limits. Consecutive customers will be put in the **waiting queue** for that skill. Advisers can pick customers from the waiting queue manually.

Returning customers with unchanged tag will be routed to the assigned adviser (if available) or to the queue for that skill. If there are available advisers with matching skills, the customer will be instantly assigned, as long as chat limits allow for it.

Returning customers with changed tag will be routed as if they were new customers - they will be put in the appropriate queue and routed to the correct team.


---

# 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://support.closer.app/guide/getting-deeper/set-up-skill-based-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.