> 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/set-up-a-shared-front-desk.md).
# Set up a shared front desk
Several people, one number, no double replies.
When three people answer the same WhatsApp number, two things go wrong: the same customer gets answered twice, or everyone assumes someone else has it and nobody answers at all.
This setup takes about fifteen minutes and fixes both.
#### 1. Give everyone their own login
Do not share one account. Each person gets their own, so you can see who replied to what, and so conversations can be assigned to a named human.
[Add your team](/docs/inbox/hosted-inbox/quickstart.md#add-your-team)
#### 2. Agree one rule: assign before you reply
{% columns %}
{% column %}
The rule that does the work is simple. **Before you type, assign the conversation to yourself.** Everyone else can then see it is handled.
It only works if it is the whole team's habit, not a suggestion. Agree it out loud once, on day one.
See [how to assign chats](/docs/inbox/hosted-inbox/working-chats.md#assignment)
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
#### 3. Make the unassigned queue the shared to-do list
Filter to unassigned conversations. That is the queue — anything sitting there has nobody on it. When it is empty, nothing has been dropped.
Whoever opens the inbox first in the morning clears it.
#### 4. Save the answers you all repeat
Opening hours, address, how to book, what you charge to deliver. Save them once and everyone answers the same way, in the same words, without retyping.
See [Quick Replies](/docs/inbox/hosted-inbox/working-chats.md#quick-replays)
#### 5. Hand over at the end of a shift
At the end of a shift, reassign anything still open to whoever is on next, or unassign it back to the queue. The next person reads the thread and picks up mid-conversation — the full history is right there.
{% hint style="success" %}
Once this is running, the natural next step is tagging conversations by what they are waiting on. That turns a tidy queue into something you can prioritise: [Run a sales pipeline with tags](/docs/inbox/hosted-inbox/playbooks/run-a-sales-pipeline-with-tags.md).
{% 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/set-up-a-shared-front-desk.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.
