> 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/hand-over-an-inbox-to-a-client.md).
# Hand over an Inbox to a client
Set WhatsApp up for someone else and leave them with something that works without you.
If you are an agency, a dev shop or an integrator, you are often the one who sets WhatsApp up and never the one who answers on it. The job is to hand over something a non-technical client can run on their own — and not become their permanent operator.
#### 1. Enable the Inbox, even if the client will mostly automate
It costs nothing on Premium and it gives the client a human fallback from day one. A number with an API integration and no inbox means every question that the automation cannot handle goes nowhere — and comes back to you.
See the [Quickstart](/docs/inbox/hosted-inbox/quickstart.md).
#### 2. Create logins in the client's own domain
This is the step that decides whether the handover holds. Create accounts for the people who will actually answer, on the client's own email addresses — not one shared login, and not your agency's address with the password passed along.
If the only login is yours, you are still the operator six months from now.
#### 3. Get their first templates approved before you leave
Templates need Meta approval, which takes time and can be rejected. Do not leave the client to discover this on a Friday afternoon when they need to send a delivery update.
Get the obvious ones approved while you are still engaged: a greeting, an order or booking update, a reminder. Show them where templates are created in the Hub — [**Channels → their channel → Templates**](https://app.360dialog.com/templates) — so they can add more. See [Templates](/docs/hub/template-management-ui.md) for more details.
#### 4. Set up how the bot and the humans share the number
If you built an automation, decide what happens when it cannot answer, and make sure a human sees those conversations. Your integration and the Inbox are looking at the same conversations, so the handover can be as simple as the bot going quiet and a person picking up in the Inbox.
See our [Messaging API](/docs/messaging-api/api-reference.md) to build any custom integration, or directly leverage our native [Zapier](https://zapier.com/apps/360dialog/integrations/360dialog/255731527/respond-to-new-inbound-messages-via-360dialog), [n8n](https://www.npmjs.com/package/@pmartino/n8n-nodes-360dialog) or [Make](https://eu1.make.com/public/shared-scenario/zh21aRie6uI/receive-and-send-your-first-message) apps.
#### 5. Walk them through it once, on their own screen
Twenty minutes, on their machine, with their login. Cover four things and nothing else:
* Where conversations appear and how to reply
* Assigning, if more than one of them will answer
* How to send a template when a conversation has gone cold
* Who to contact for support
#### 6. Leave them a one-page note
Which number, which logins exist, which templates are approved, what the automation does, and what to do if something stops. It is the difference between a client who calls you and a client who does not.
{% hint style="info" %}
Running WhatsApp for several clients? Each channel has its own Inbox. Keep the same handover checklist for every one of them — the accounts you fail to create in the client's name are the ones you end up staffing.
{% endhint %}
---
# 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/hand-over-an-inbox-to-a-client.md?ask=&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.
