> 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/reasons-for-support.md).

# Reasons for support

## ✅ How to create a reason

1. Go to the menu **Settings**.
2. Click on **Support reasons**.
3. Select **Add reason**.
4. Fill in the information:
   * **Name:** Enter a clear and objective name for the reason.
   * Reason description.
   * Add a department (if this reason is used for a specific department)
   * **Type:** Select which action this reason will be used for.
5. Click on **Save**.

After saving, the reason will be available for use according to the selected type.

## **📂 Reason types**

When creating a reason, it is necessary to define where it can be used.

### 🔚 Support closure

Used when a support interaction is closed.

#### Examples:

* Request completed
* Customer did not respond
* Issue resolved
* Duplicate support ticket

### 🗄️ Support archiving

Used when a support interaction is archived for operation organization.

#### Examples:

* Old support ticket
* Conversation without follow-up
* Request closed

### 🏆 Card won (CRM)

Used when a card is marked as **Won**, indicating that the goal of the negotiation has been achieved.

#### Examples:

* Sale completed
* Contract signed
* Converted customer

### ❌ Card lost (CRM)

Used when a card is marked as **Lost**, recording the reason why the deal was not completed.

#### Examples:

* Customer gave up
* Competitor
* No response
* Out of budget

### 🚫 Unavailable for support

Used when the agent changes their status to unavailable.

#### Examples:

* Lunch
* Meeting
* Training
* Break
* End of shift

### 🔄 Support transfer

Used whenever a support interaction is transferred between users, queues, or departments.

#### Examples:

* Forwarded to the finance department
* Transfer to technical support
* Change of owner
* Support escalation

## ✏️ How to edit a reason

1. Access **Settings > Support reasons**.
2. Find the desired reason.
3. Click on the reason.
4. Make the necessary changes.
5. Click on **Save**.

## ⚠️ Deletion and hiding of reasons

After being created, a reason **cannot be deleted or hidden**.

This restriction exists to preserve the integrity of the platform's history, ensuring that all actions already performed (such as support closures, archiving, transfers, status changes, and CRM movements) continue to correctly display the reason used at the time of the record.

If a reason is no longer used by the operation, it must remain registered, even if it is no longer used in new actions.


---

# 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.hablla.com/hablla-docs-en/hablla/settings/reasons-for-support.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.