01 · The problem
When one phone cannot keep up
Growth brings more conversations, more roles, and more people who need to see what is happening. A phone in one pocket cannot do that.
Sales, support, and bookings all compete for one device
Shared logins and screenshot handovers lose context
Nobody knows who answered what, or what is still unanswered
02 · The setup
The team inbox setup
Connect the number once, add your agents, and everyone works from the same inbox. WhatsApp and Telegram conversations sit side by side.
Connect once via Meta Cloud API or QR session
Add agents; each gets the shared inbox on any device
Roles control who sees what
The full conversation history lives in the workspace, not on a phone
03 · The rules
Rules that keep it clean
A shared inbox works when the rules are explicit.
Assignments: an agent takes a conversation; the team sees the owner
Collision avoidance: one active agent per conversation, no double replies
Tags: pipeline stages and topics stay visible at a glance
AI drafts: the first reply is written in seconds, human-reviewed before send
04 · The handover
Handovers
When the assigned agent is away, reassign with a note. The customer never sees the change; the context lives in the conversation.
05 · The templates
Copy-paste templates
Adjust the placeholders and send. These work as WhatsApp templates (utility category) or plain messages inside the service window.
Ready to use
Copy, adapt, send
Adjust the placeholders, then copy and paste. Works as WhatsApp templates or plain messages.
Assignment note
Copy
Assigned to {agent}: {task} for {customer}. Context: {summary}. Due {time}.
Handover
Copy
Hi {name}, {agent2} here. {agent1} passed your chat to me. I've got your order {order_no} and will take it from here.
Tag reminder
Copy
Tag {tag} on {conversation}. Next step: {action} by {time}.
Team update
Copy
Update: {conversation} is now {status}. Owner: {agent}. Open item: {next_step}.
Common questions
As many as you need. Every agent gets the shared inbox with assignments and history.
No. Collision avoidance keeps one active agent per conversation until it is closed or reassigned.
No. All replies come from the single business number; agents work from Wutt.
Yes. Assignments and notes leave a full history of who did what.
Roles control who sees which conversations; assignments keep ownership explicit.
A QR session connects a personal number and suits small teams. The Meta Cloud API scales further with templates and campaigns.