> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user/crm-v2/inbox/use-tags-in-live-chat-for-better-management.md).

# Use Tags in Live Chat for Better Management

### How to Create a Tag

**1.** Go to **CRM → Live Chat**\
**2.** Click **Add Tag** (top right)\
**3.** Enter a clear **Tag Name** (e.g., Hot Lead, Follow-Up, Support)\
**4.** Select a **Color** (predefined or custom hex code)\
**5.** Preview the tag → Click **Add**\
**6.** Click **Save Changes**

You can also **edit or delete tags** anytime to keep your workspace organized.

### How to Apply a Tag to a Chat

**1.** Open a conversation\
**2.** Click the **Three Dots (⋮)**\
**3.** Select **Update Tags**\
**4.** Choose the required tag\
**5.** Click **Save Changes**

The tag will now appear on that chat.

### Additional Chat Actions

From the same menu, you can:

* Mark chat as **Done / Closed / Unread**
* **Pause Automation**
* **Archive Chat**
* **Transfer to another team member**

Tags remain visible even after transfer, maintaining full context.

{% embed url="<https://youtu.be/u34tFfFnMhY>" %}


---

# 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://helpdocumentation.gitbook.io/user/crm-v2/inbox/use-tags-in-live-chat-for-better-management.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.