Learning Center

WhatsApp shared inbox for small teams: setup and playbook

By the Onsites AI team · Last updated August 28, 2026 · 7-minute read

WhatsApp is where your customers already are, which is exactly the problem: support that lives on one phone in one person's pocket does not survive a holiday, a sick day or a second product. A shared inbox fixes the organization, not the channel — the number stays the same, but any teammate can pick up any thread, history persists, and the conversation links itself to the customer's record. This guide covers connecting the channel and the small-team playbook that keeps it fast and sane.

What you need

Three things: a free workspace (register in two minutes), your WhatsApp Business number, and about ten minutes. Customers need nothing new — they message the number they already have saved, and nothing changes on their screen. That zero-migration property is worth as much as the software: nobody ever abandons a purchase because "your support channel got reorganized."

Connect the channel

In your workspace open Settings → Channels and link your WhatsApp Business number in the WhatsApp card. From the moment it connects, incoming messages land in the same shared queue as your website chat and email — no separate mailbox, no second login, no channel-specific muscle memory for your team to learn. Replies go out from the desk under the same identity customers already trust.

Once the pipe exists, set the visible guardrails in the same sitting: working hours and a first-response SLA in settings, so the queue escalates honestly when a message is about to breach rather than after.

The small-team playbook

1. Work the queue, not the phone

The desk queue is the single source of truth. Whoever frees up takes the oldest unclaimed conversation. If you need context mid-thread — "did engineering answer about the failing export?" — that goes into a private note, which teammates see but the customer never does. Two people never need to shout across the room to hand off a thread again.

2. Tag by intent while you reply

Tags are the cheapest reporting system ever invented. A tag added while you answer — refund, shipping-delay, order-status — becomes a filterable, countable dataset later, with zero dashboards built and zero exports taken. On WhatsApp, where conversations arrive without subject lines, tags are how Friday's "what did customers actually ask" question gets answered in ten seconds.

3. Save replies as drafts, answers as drafts-with-history

Every customer asks about order status eventually. Instead of the ninth retyping, keep your best phrasing in a draft and reuse it with the variables filled in. Copilot, if you enable it, drafts the reply for you — 6 credits for a suggested reply, and you edit rather than write. At roughly a cent per credit, the meter stays immaterial; the habit of editing instead of retyping is the real win.

4. Let context do the remembering

Conversations attach themselves to customer records automatically. The account, the contact, their open opportunities — all visible in the context panel while you type. When a support thread reveals an upsell or a renewal at risk, you see the deal next to the conversation instead of switching tools; the CRM guide covers what to build into that record.

Etiquette that keeps it humane

• Answer within the window you promise. WhatsApp trains people to expect minutes, not days. If your real first-response time is two hours, say so in the greeting — a kept "2 hours" beats a broken "5 minutes."
• Move attachments with intention. Photos and files arrive with the conversation and count toward storage; attachments are what add up beyond the free 100 MB, at $1 per GB per month in packs. Text itself is negligible.
• No broadcasts. The shared inbox serves people who wrote to you. Anything resembling outbound marketing over a support channel burns the trust that made the channel work.
• Close the loop. A conversation you solved but never acknowledged still reads as ignored. One line — "done, the refund shows tomorrow" — converts work done into service perceived.

Where WhatsApp fits among your channels

Treat WhatsApp as one card in the same deck as website chat, email, Telegram, LINE, WeChat and Messenger. The playbook above — queue, notes, tags, drafts, context — is identical on every card, which is the actual argument for a shared desk over channel-specific tools. If your audience leans Asia-Pacific, the LINE guide and the WeChat guide cover the same wiring for those channels. And if WhatsApp itself is a compliance line-item where you sell, the desk also runs self-hosted, entirely inside your network.

A word on expectations, both sides

The greeting sets the contract, the SLA measures it, and tone keeps it. On WhatsApp, shorter reads as more professional, not less: three sentences where an email would have taken three paragraphs, the photo the customer actually needs attached, and honest timing when the real answer lands tomorrow. None of that is one person's personality trait — with notes, drafts and a shared queue behind one number, it becomes how the team behaves by default. That is precisely the property that survives your first holiday season, your first sick day and your first hire, and it is the whole reason to move a channel off a phone and into a desk.