> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/settings/departments.md).

# Departments

Organize support in Hablla with Departments: define teams, schedules, SLAs, and transfer conversations to humans efficiently and in a structured way.

{% embed url="<https://youtu.be/-RucWqJ1gBI?si=b100CyWJ2CzSedbu>" %}

## Departments in Hablla

The **Departments** organize your company's customer service within Hablla.\
They define **who serves, when they serve and how service should be transferred between people and teams**.

Creating departments is fundamental to structure workflows, distribute responsibilities and configure transfer rules for human interactions.

***

### What are Departments?

A **Department** is a functional area of your company within Hablla.\
Common examples of departments:

* Customer Service
* Sales
* Finance
* Technical Support

Each department can have assigned users, operating hours and its own SLA (Service Level Agreement) rules.

***

### Main functions of Departments

1. **Define service team**
   * Each department brings together the users responsible for responding to and following up on requests for that area.
   * This ensures that the customer always talks to the correct team.
2. **Configure transfers to humans**
   * The **Transfer** component directs the conversation to a human agent.
   * This routing only works correctly when associated with a department.
3. **Organize service hours**
   * Each department can have a **business hours** set.
   * Example: the Sales department may only operate Monday to Friday, from 9am to 6pm.
   * Outside of these hours, flows can direct automatic messages or waiting queues.
4. **Manage SLAs**
   * Set response and resolution timeframes for each department.
   * Example: the Finance department may have a 24-hour SLA to respond to requests, while Technical Support may have a 4-hour SLA.

***

### How to create a Department

1. In the Workspace top menu, click on **Departments**.
2. Click on **Create new department**.
3. Fill in the information:
   * **Department name** (e.g.: Sales, Customer Service, Finance).
   * **Description** (brief explanation of the department's role).
   * **Assigned users** (who will be part of this department).
   * **Operating hours** (optional at creation time, can be configured later).
   * **SLA rules** (if applicable).
4. Click on **Save** to finish.

***

### Summary

Departments are the foundation for organizing human interactions and workflows in Hablla.\
With them you can:

* Route conversations to the right teams.
* Ensure efficient transfers to humans.
* Define specific service hours and SLAs.
* Better structure the operations of Marketing, Sales, CS and Support.

***

📌 **Practical tip**: create departments aligned with your company's real structure. This makes management easier and improves the customer experience, since each area will have well-defined rules and responsible parties.


---

# 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://docs.hablla.com/hablla-docs-en/hablla/settings/departments.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.
