> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/inbox/tagging-conversations.md).

# Tagging Conversations

You can tag conversations with relevant keywords or labels. This makes it easy to categorize and find specific discussions or issues.

### How to create a new tag

**Step 1:** Navigate to the Inbox tab from the sidebar.

**Step 2:** Once you have the Inbox opened, click on '+ New' under the 'Tagged' section in the inbox menu.

<figure><img src="https://312952119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaFKpjLzPT7iDAWD0tQXo%2Fuploads%2FVJNcShmmfqJiwqH4xokQ%2FScreenshot%202023-11-01%20at%208.44.30%20PM.png?alt=media&amp;token=bce44150-8bb3-490b-9fcb-b0ac072d013a" alt=""><figcaption></figcaption></figure>

**Step 3:** Name the tag and designate its color, then hit the Add button. Your new tag will appear under the 'Tagged' section of the inbox menu. Clicking on a tag there will show you all the conversations with that tag.

### How to tag a conversation

**Step 1:** Navigate to the Inbox tab from the sidebar.

**Step 2:** Once you have the Inbox opened, click on a conversation.&#x20;

**Step 3:** Up at the top of the conversation window, click on the 'Assign' button. Select a tag.&#x20;

<figure><img src="https://312952119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaFKpjLzPT7iDAWD0tQXo%2Fuploads%2F0FCZJoPtJ4fD7ac8rOxm%2FScreenshot%202023-11-01%20at%208.48.42%20PM.png?alt=media&amp;token=94abbc32-b659-4b79-af7e-a3f10a7a1bb6" alt="" width="563"><figcaption></figcaption></figure>

**Step 4:** Your new tag will appear under the 'Tagged' section of the inbox menu. Clicking on a tag there will show you all the conversations with that tag.


---

# 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://help.gleantap.com/inbox/tagging-conversations.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.
