> 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/playbooks.md).

# Playbooks

Complete setups for the most common ways businesses use the Inbox.

The Inbox does not tell you how to work. These playbooks do — each one is a specific way of setting it up, taken from how customers actually use it.

Pick the one that sounds like you. They take 10 to 20 minutes each and none of them need code.

| Playbook                                                                                                               | For you if…                                                                                                                    |
| ---------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| [Run a sales pipeline with tags](/docs/inbox/hosted-inbox/playbooks/run-a-sales-pipeline-with-tags.md)                 | You sell or take orders over WhatsApp and lose track of where each one stands                                                  |
| [Set up a shared front desk](/docs/inbox/hosted-inbox/playbooks/set-up-a-shared-front-desk.md)                         | Several people answer the same number and keep replying twice, or not at all                                                   |
| [Upgrade from the WhatsApp Business app](/docs/inbox/hosted-inbox/playbooks/upgrade-from-the-whatsapp-business-app.md) | Your number lives in the app on one phone, colleagues get by on linked devices, and you want to give more people proper access |
| [Hand over an Inbox to a client](/docs/inbox/hosted-inbox/playbooks/hand-over-an-inbox-to-a-client.md)                 | You are setting WhatsApp up for someone else and will not be the one answering                                                 |


---

# 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/playbooks.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.