> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/docs/inbox/hosted-inbox/working-chats.md).

# Working chats

Assign chats, add tags, search and save frequently-used responses.

A shared inbox only works if it is obvious who is handling what. These four features are what turn a list of messages into a way of working. All of them are optional — you can ignore every one of them and still just reply.

### Assignment

{% columns %}
{% column width="50%" %}
Assign a conversation to a person, and it is clear that they own the reply. Everyone can still see and open the chat; assignment says who is answering, not who is allowed to.

Use it when more than one person answers the same number. If you are on your own, skip it.
{% endcolumn %}

{% column width="50%" %}

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FewKaXWxSzCuTKnBPqwMC%2Fimage.png?alt=media&amp;token=edb5d808-f204-4733-aafa-090ad0fbc9fb" alt=""><figcaption></figcaption></figure>

{% endcolumn %}
{% endcolumns %}

### Tags

Tags are free-form labels you put on a conversation. You create your own, so they can mean whatever is useful to you.

Most teams use them for one of two things:

* **Stages** — where a deal or an order has got to: *New lead*, *Quote sent*, *Awaiting payment*, *Delivered*
* **Segments** — what kind of customer this is: *VIP*, *Wholesale*, *Repeat*

Stages are the more useful of the two, because they let you filter the inbox down to the conversations that need something from you today. [Run a sales pipeline with tags](/docs/inbox/hosted-inbox/playbooks/run-a-sales-pipeline-with-tags.md) walks through setting that up.

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FlYDecycmrgd3N4cBNbTe%2Fimage.png?alt=media&amp;token=4dbfb116-ccd0-4c5e-8183-66522125f50d" alt=""><figcaption></figcaption></figure>

### Search

Search runs across your message history, not just the chats currently on screen. Useful for finding the address someone sent three weeks ago, or checking what was promised on a price.

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FRcwBGaBn89sIJwu3Yjk2%2Fimage.png?alt=media&amp;token=789106f8-292f-430c-8966-c37822ed043e" alt=""><figcaption></figcaption></figure>

### Quick replies

Quick replies are reusable snippets of text you can drop into a reply: opening hours, delivery terms, payment details, the answer to the question you get five times a day.

They are plain text you insert and can edit before sending, so they are not templates — templates are the approved messages WhatsApp requires to open a closed conversation, and those are covered in [Starting and reopening conversations](/docs/inbox/hosted-inbox/starting-and-reopening-conversations.md).

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FUhLNYSxL4qySfAyG9Kqc%2Fimage.png?alt=media&amp;token=f0fbcd78-4eae-4cf6-8bcd-3b15fc833326" alt=""><figcaption></figcaption></figure>

### Resolving a conversation

Marking a chat resolved takes it out of your active list without deleting anything. If the customer writes again, it comes back.

<figure><img src="https://3527970750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M4sMxKjL6eJRvZn6jeG-887967055%2Fuploads%2FsVA4NTRuVDqsPZal0hJP%2Fimage.png?alt=media&amp;token=606a3131-39a6-41cd-b913-706f2f5c8c45" alt=""><figcaption></figcaption></figure>


---

# 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.360dialog.com/docs/inbox/hosted-inbox/working-chats.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.
