# Labels

Labels help teams classify, filter, route, and report on conversations. They are lightweight, visible, and flexible.

Use labels for information that helps people act on a conversation. Do not use labels as a dumping ground for every detail. If the value belongs to a customer profile or needs structured reporting, use a custom attribute instead.

## Create Labels

Go to **Settings -> Labels**.

1. Create a short label name.
2. Choose a color that helps agents scan the inbox.
3. Save the label.
4. Apply it manually or through automation.

Good labels describe intent or state, such as `billing`, `bug`, `vip`, `refund`, `trial`, or `needs-review`.

## Naming Rules

Pick one naming style before launch:

* Lowercase words.
* Hyphenated phrases for multiple words.
* No duplicate singular and plural versions.
* No temporary labels unless they have an owner and removal date.

Consistent naming keeps filters and reports reliable.

## Using Labels In Workflows

Labels can support:

* Inbox triage.
* Automation rules.
* Team assignment.
* SLA policies.
* Reporting and trend review.

For example, a `vip` label can route a conversation to an enterprise team or trigger a shorter SLA target.

## Maintenance

Review labels monthly. Merge duplicates, remove labels no one uses, and document labels that drive automation. Never delete a label without checking whether a rule, macro, report, or SLA policy depends on it.


---

# Agent Instructions: 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:

```
GET https://developers.easydesk.live/labels.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.