> For the complete documentation index, see [llms.txt](https://guide.tiledesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.tiledesk.com/manage-your-workspace/creating-a-department.md).
# Creating a department
#### Department: Definition
Departments allow you to efficiently route visitors’ requests to designated groups. This ensures that your visitors’ messages are always directed to the right agents.
#### What Are the Benefits?
One of the key metrics of efficient customer support is First Contact Resolution (FCR). It is the percentage of support inquiries that agents resolve on the first attempt. This can only be achieved with departments. You can create a department for sales and another for support. This ensures that your sales team will not receive support inquiries and vice versa. It will boost agent productivity, and your customers can receive resolutions faster.
**Departments help your business to:**
**Save Operators’ Time:** Answer your customers quicker by focusing only on the relevant chats. No more reassigning chats.
**Relevant Conversations Only:** Experience fewer interruptions during your work. Let your visitors find the right operator and enjoy fewer notifications and chats.
**Keep Your Inbox Organized:** See only the chats within the scope of your expertise. Let other departments handle the rest.
#### How to Create a Department
1. Go to [**Tiledesk dashboard**](https://panel.tiledesk.com/v3/dashboard/#/signup) and select **Settings > Routings & Depts**.
2. Click **Add Department**.
3. Enter the relevant details, as shown in the screenshot below.
4. Click on the **All Teammates** option or select a [**Group**](/manage-your-workspace/creating-groups.md) to add them to the department.
5. Click **Create Department**.
#### How to Embed Departments in the Conversation Flow
To recall departments in the conversation flow, head to the [Design Studio](https://panel.tiledesk.com/v3/dashboard/#/signup).
As shown in the image below, I use “[ChatGPT task](/ai-chatbots-and-automation/actions-explained/chatgpt-task.md)” to understand the user inquiries and categorize them.
In the prompt, I ask ChatGPT to categorize incoming inquiries into “**sales**” or “**support**”.
Then, we need to use another action called “Condition w/else”.
Click on it, and from the right popup setting, hit “Add New Condition”.
Among the Attributes, select “gpt\_reply”.
Choose “Start with Ignore Case” among the Conditions, and put “sales” as the Value.
Now, we need to connect the “Change Department” action to the green endpoint of the Condition block, as you can see in the image below.
Click on the new block and choose the relevant department.
That’s all. All inquiries about sales will be transferred to the sales department.
For support-oriented inquiries, you need to follow exactly the same process and select the support department.
Hope this helps. In case you need further support, do not hesitate to contact us at [**support@tiledesk.com**](mailto:support@tiledesk.com).
For more information, please visit: [**www.tiledesk.com**](https://tiledesk.com/)\
---
# 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://guide.tiledesk.com/manage-your-workspace/creating-a-department.md?ask=&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.
