A WhatsApp shared inbox for Singapore SMBs is the operational foundation that makes WhatsApp work as a team channel rather than a personal one. Once more than one person needs to reply to a business WhatsApp number — or once inquiry volume grows past what one person can manage — the shared inbox is the architecture that determines whether that team operates as a coordinated unit or a group of individuals stepping on each other's conversations.
This post covers the setup and structure of a WhatsApp shared inbox: what it actually is, what roles and permissions look like in practice, how conversation history is stored and shared, and why the free WhatsApp Business app can't replicate the same function no matter how many linked devices you add. If you're already clear on why you need a shared inbox and are looking for the day-to-day routing and assignment strategies for managing conversation queues across a team, that ground is covered separately in the companion post on managing a WhatsApp team inbox without chaos.
This post is for the business that is choosing an inbox architecture and wants to understand what it's buying before committing — what the setup involves, what capabilities it unlocks, and what technical constraints govern the whole system.
What is a WhatsApp shared inbox and what does it actually let a team do?
A WhatsApp shared inbox is a single business WhatsApp number that multiple team members can access simultaneously from their own devices, with conversations centrally managed on a platform rather than tied to any individual phone. Each team member logs into the platform — a web app or mobile app — and can see, reply to, and manage conversations without needing physical access to a single shared phone.
The word 'shared' is doing specific work here. It doesn't mean multiple people watching the same WhatsApp app on the same phone. It means the conversation queue is hosted on a platform that all authorised users can reach independently, with their own credentials, from wherever they are. A team member in the Jurong branch and a supervisor working from home both see the same conversation queue, in real time, and both can take action on it.
What this unlocks is coordination at a level the free app simply doesn't support: conversations are assigned to named team members, so there's no ambiguity about who is handling what; supervisors see the full queue at any time; conversation history is stored on the platform and doesn't disappear when someone is on leave; and there's a record of who said what, when, and what stage each conversation is at.
| Capability | Single phone (free app) | Shared inbox (WhatsApp Business API) |
|---|---|---|
| Multiple agents reply to one number simultaneously | No — effectively one active replier at a time | Yes — unlimited concurrent agents, each with their own login |
| Conversation assigned to a specific team member | No — first person to see it replies | Yes — visible assignment in the shared queue |
| Full conversation history accessible to all agents | No — tied to the primary device | Yes — stored on the platform, accessible to all authorised users |
| Supervisor can see all open conversations | No — would need physical access to the phone | Yes — full queue visibility from any device |
| Internal notes on a conversation | No | Yes — private notes visible only to the team, not the customer |
| AI agent handling first response | No — basic away messages only | Yes — AI agent trained on your knowledge base |
Why can't the free WhatsApp Business app handle multiple agents?
The free WhatsApp Business app is a single-device application. It was designed for one person managing one business number from one phone. The device that registers the number is the primary device, and everything else — including the linked-device feature — depends on that primary phone being online and functional.
When a second person needs to reply, the only options within the free app are: share the physical phone (operationally impractical for a real team), add a linked device (which has strict limits and specific limitations), or register the number on a second account (which WhatsApp prohibits for the same number). None of these are designed for a multi-agent team, and none of them provide conversation assignment, shared visibility, or centralised conversation history.
This isn't a gap that Meta will eventually fill in the free app. The Business API is where team-scale functionality lives by design — it's the infrastructure for platforms that build on top of WhatsApp to deliver multi-agent, multi-device, and automation capabilities. The free app is the right tool for a solo operator. The API is the right tool for a team.
| Free WhatsApp Business app | WhatsApp Business API (via a BSP platform) |
|---|---|
| One primary phone required — all functionality depends on it being online | Cloud-hosted — no single device is required to be online for the inbox to work |
| Up to four linked devices — read and reply, but no assignment between them | Unlimited concurrent agents — each with their own login and role |
| No conversation assignment or queue management | Full conversation assignment, visible to the whole team |
| No internal team notes on conversations | Private notes and @mentions within conversations |
| No AI agent or intelligent automation | AI agent trained on a knowledge base, integrated into the inbox |
| No reply-time or volume reporting | Reporting dashboard with response metrics |
Linked devices do not solve the shared inbox problem
WhatsApp Business linked devices let additional phones access your number's messages, but they don't provide conversation assignment, centralised history management, or any coordination between users. Two people with linked-device access can still both reply to the same message at the same time, with no indication that the other has already responded. A shared inbox is an architecture, not just additional device access.
What are linked devices on WhatsApp Business and why aren't they enough?
WhatsApp Business allows a number registered on a primary phone to also be accessed on up to four additional 'linked' devices — other phones, tablets, or WhatsApp Web sessions. Linked devices can read and reply to messages without the primary phone being online, which is genuinely useful for a solo operator who wants web access. But they have specific limitations that make them unsuitable for a team managing shared inquiry volume.
The most significant limitation is that linked devices share one conversation view with no assignment layer between them. If three staff members each have the same WhatsApp number linked to their devices, all three see the same unread chat, and all three can reply to it independently. The first to type sends their message. If the second is also partway through a reply, their message also sends. The customer now has two or three replies to one question, potentially with different information.
A second limitation is that conversation history on a linked device syncs from the primary phone. If the primary phone is unavailable — because the person who owns it is on leave, or because it's lost or broken — the linked devices may lose access to historical conversations or functionality until the primary phone is back online. For a business where customer context matters across multiple conversations, this dependency on one device is a structural risk.
Linked devices are for solo-operator convenience, not team coordination
If you're a solo operator who wants to switch between your phone and a laptop without losing access to WhatsApp, linked devices are well suited for that. If you have two or more people who need to reply to the same inbox, you've already passed the threshold where linked devices create more problems than they solve.
Linked devices vs. a shared inbox — the practical difference
- Three staff with linked devices
- All three see the same unread customer message. Two start typing independently. Both replies send. Customer receives contradictory information. No one knows who replied.
- Three staff with a shared inbox
- Conversation appears in the unassigned queue. One staff member picks it up — it moves to their assigned view. The other two see it's already being handled. One reply sends.
How does a WhatsApp shared inbox handle roles and permissions?
A well-architected WhatsApp shared inbox platform organises team members into roles that determine what each person can see, do, and access. The specific role names vary by platform, but the functional distinctions are consistent across most serious implementations. Understanding the role structure before onboarding the team saves a significant amount of confusion about who does what.
The three-tier structure used by most platforms maps onto the natural hierarchy of a Singapore SMB customer-facing team: the agent who replies to customers, the supervisor who manages the queue and reviews quality, and the admin who configures the system and manages access.
- Define who needs which role before you add anyone to the platformWrite down every person who will use the inbox and which role they should have. Agents see only what they need to reply; supervisors see the queue to manage it; admins configure the system. Giving everyone admin access creates a maintenance and security problem — most customer-facing staff should be agents, with one or two supervisors and a single admin.
- Add agents before you transfer inquiry volumeOnboard each team member to the inbox platform, confirm they can log in from their own device, and let them read a few existing conversations before the inbox goes live. Staff who first encounter the shared inbox while a queue of real customer messages is building will make setup mistakes under pressure.
- Set response-time expectations by roleAgents need a clear expectation for how quickly they should pick up an unassigned conversation — for example, within 30 minutes during business hours. Supervisors need to know at what point an unassigned conversation escalates to them. These rules don't need to be complex; they just need to be written down and agreed on before the inbox goes live.
- Assign the AI agent role before human agents, not afterIf you're using an AI agent for first response and FAQ handling, configure it before the human agents start replying. The AI agent should handle the first message automatically and route conversations to the human queue only when it reaches a question beyond its knowledge base. Getting this sequence right means human agents start their shift with a queue that has already been triaged, not one full of first-response FAQ messages.
| Role | What they can do | Who this is in a Singapore SMB |
|---|---|---|
| Agent | View assigned conversations, reply to customers, leave internal notes, escalate to supervisor | Customer-facing staff: shop floor, F&B front-of-house, service coordinators |
| Supervisor | View all conversations (assigned and unassigned), reassign conversations, monitor reply times, review agent performance | Team lead, ops manager, senior staff member |
| Admin | Configure the platform: add/remove users, set roles, manage the AI agent knowledge base, set business hours, view all reporting | Business owner, operations manager, or IT lead |
How does conversation assignment work day to day?
Conversation assignment is the mechanism that replaces the 'whoever picks up the phone first replies' approach of a single device. In a shared inbox, every conversation sits in one of three states: unassigned (visible to all, waiting for someone to take it), assigned (belonging to a named agent who is actively handling it), or resolved (closed, but still visible in history).
The practical day-to-day experience for an agent depends on the inbox's assignment method. Some platforms use manual assignment — a supervisor looks at the unassigned queue and distributes conversations to agents. Others allow agents to self-assign from an unassigned pool. Some platforms support auto-assignment based on rules — conversations from new customers go to the next available agent, returning customers go to whoever handled their last conversation, conversations tagged with a specific keyword go to a specialist.
For most Singapore SMBs starting out with a shared inbox for the first time, manual or self-assignment from a visible unassigned pool is the simplest place to start. It requires no configuration beyond role setup, it's immediately transparent to the whole team, and it's easy to audit when something is missed. Automated routing rules are worth adding once the team has a few weeks of experience with the inbox and can see where the assignment bottlenecks actually are.
Conversation assignment in a Singapore services business
- Before shared inbox
- Customer messages arrive on a single phone. Whoever is free checks it. Three messages get replied to. One gets missed. On Monday morning, no one knows whose responsibility the missed one was.
- With shared inbox + assignment
- Customer messages appear in the unassigned queue. Each staff member self-assigns from the pool. Every conversation has an owner visible to the whole team. The supervisor sees at a glance which are unhandled.
How does the team see a customer's full conversation history when one person is on leave?
This is one of the clearest daily advantages of a WhatsApp Business API shared inbox over the free app, and it's the failure mode that tends to crystallise the need for a proper setup: a team member goes on medical leave, or resigns, and every customer conversation they were handling is suddenly inaccessible — either locked on their personal phone or gone entirely.
In a shared inbox on a WhatsApp Business API platform, conversation history is stored centrally on the platform, not on any individual device or personal account. When a customer who was being handled by one staff member sends a follow-up message while that person is away, the conversation appears in the queue with its full history visible to any team member who picks it up. They can read every previous exchange, see any internal notes left by the original agent, and reply with full context.
This also matters for quality consistency across a team. A new staff member picking up a conversation mid-thread can see exactly what commitments were made, what information was given, and what the customer is expecting next — without having to call the original agent or ask the customer to repeat themselves.
- All conversation history is stored on the inbox platform, independent of which agent handled the chat or which device they used.
- Any team member with the right role can access the full history of any conversation — not just the conversations assigned to them.
- Internal notes left by the original agent are visible to anyone who picks up the conversation, providing context that doesn't need to be retransmitted verbally.
- When a staff member goes on leave, their assigned conversations can be reassigned to another agent by a supervisor in a few clicks — with no history lost.
- Resolved conversations remain searchable in history, so a customer who returns after months can be understood in context without starting from a blank record.
Conversation history is a business asset stored where the business controls it
On a WhatsApp Business API platform with proper role-scoped access, conversation history is stored on infrastructure the business authorises and controls — not on a personal device. Access is limited to the roles you define: agents see their assigned conversations, supervisors see the full queue, and admins control who can access what. This is the architecture required for treating customer data as a business asset rather than a personal one.
What does it take to set up a WhatsApp shared inbox for the first time?
Setting up a WhatsApp shared inbox for the first time involves three distinct workstreams: getting the WhatsApp Business API access, configuring the inbox platform, and onboarding the team. None of these steps are technically complex for a non-technical business owner, but they happen in a specific sequence and have a few common points where setup stalls.
- Get your WhatsApp Business API access through a Business Solution Provider (BSP)SMBs cannot access the WhatsApp Business API directly from Meta — access is exclusively through approved BSPs. Your shared inbox platform (KlyoChat and others like it) operates as or through a BSP. When you sign up, the platform guides you through the process of connecting your WhatsApp number and verifying your business with Meta. This step typically takes one to three business days, depending on Meta's verification queue.
- Verify your phone numberYour WhatsApp Business number needs to be verified with Meta before it can be used on the API. If the number is currently active on the free WhatsApp Business app or a personal WhatsApp account, you will need to migrate it to the API — which involves moving the number off its current app. Have this step planned in advance so you're not surprised by any gap in availability during the migration.
- Configure the inbox: set roles and add team membersOnce API access is live, add each team member as a user in the inbox platform, assign them the right role (agent, supervisor, or admin), and confirm they can log in from their own device. This step is usually the quickest — it's administrative rather than technical.
- Build and test the AI agent knowledge baseBefore the inbox goes live, train the AI agent on your most common FAQ answers: operating hours, pricing or menu, delivery zones, booking steps, and any product- or service-specific questions that come up daily. Test the agent by sending in the questions yourself and reviewing the responses — adjust any answer that is incorrect, incomplete, or phrased in a way that doesn't match your brand's tone.
- Run in parallel before full cutoverFor the first week, run the new shared inbox alongside whatever your current setup is. Watch how the team uses the assignment queue, check that the AI agent is handling FAQs correctly, and confirm that conversation history is persisting as expected. Then complete the cutover by directing all new inquiry traffic to the shared inbox and letting the old setup wind down.
What is a Business Solution Provider and why do you need one?
SMBs in Singapore — and anywhere else — cannot sign up for WhatsApp Business API access directly through Meta's developer portal without going through an approved Business Solution Provider (BSP). The BSP is the technical intermediary between your business and Meta's WhatsApp infrastructure. In practice, this means the WhatsApp shared inbox platform you choose is either itself a Meta-approved BSP or builds its WhatsApp connectivity on top of one.
When you sign up for a platform like KlyoChat, the platform handles the BSP relationship on your behalf. You connect your WhatsApp number through the platform's guided setup, the platform handles the Meta verification and API provisioning, and you end up with a live inbox without needing to manage the API connection directly. The practical implication is that you're choosing an inbox platform rather than directly choosing a BSP — but it's worth knowing the BSP layer exists so you understand why the onboarding involves Meta verification steps that take a few days, rather than an instant account creation.
Because WhatsApp API access is BSP-gated, switching platforms means migrating your WhatsApp number from one provider's infrastructure to another's — a process that's possible and reasonably straightforward, but involves another round of verification and a brief transition window. It's worth choosing a platform you expect to use for a year or more before you go through setup, rather than treating it as a quick experiment.
You choose a platform, not a BSP directly
Most Singapore SMBs will never need to interact with the BSP layer directly. When you sign up for KlyoChat or a similar platform, the platform manages the Meta API connection for you. What matters for your decision is the platform's inbox features, pricing, and support — the BSP infrastructure underneath is a technical detail the platform handles.
How many agents can share one WhatsApp Business number?
On the WhatsApp Business API, the number of agents who can access a shared inbox is determined by the platform's plan limits, not by a fixed WhatsApp cap. Meta does not set a hard limit on concurrent users for a given WhatsApp Business API number the way the free app limits you to four linked devices.
In practice, this means the answer to 'how many agents' depends on the platform you choose and which plan you're on. Most serious platforms offer enough agent capacity for any SMB team — the limits relevant to SMBs are usually conversation volume and contacts, not headcount.
| Setup type | Agent limit | Simultaneous replies | Conversation assignment |
|---|---|---|---|
| Free WhatsApp Business app (primary phone only) | 1 active replier | 1 at a time | None |
| Free app with linked devices | Up to 4 additional linked devices | Multiple, but with no coordination | None — whoever replies first sends |
| WhatsApp Business API via shared inbox platform | Platform-determined (most SMB plans: 5-20+ agents) | Unlimited concurrent — each agent handles their assigned queue | Full assignment with queue visibility |
Is a WhatsApp shared inbox different from WhatsApp's own multi-device feature?
Yes — and the difference matters enough that conflating them creates real setup confusion. WhatsApp's multi-device feature (available in the free Business app) lets a single WhatsApp account be accessed on up to four devices simultaneously, with the primary phone as the source of truth. It's a convenience feature for one person, not a coordination tool for a team.
A WhatsApp shared inbox is a different architecture entirely. It runs on the WhatsApp Business API, stores conversations on a platform rather than a device, and supports multiple named users with distinct logins, roles, and assignment. The conversation data lives on the platform — not on any phone — so it's accessible from anywhere, by anyone with the right role, without depending on a primary device being online.
The simplest way to tell them apart: with multi-device, you're still one person accessing one account from multiple places. With a shared inbox, you're a team of people accessing a shared account from their own accounts, with coordination built in.
Multi-device and shared inbox solve different problems
Multi-device is for the solo operator who wants laptop access while keeping their phone nearby. A shared inbox is for a team that needs two or more people to reply to the same number with coordination, visibility, and accountability. They're not competing options — they're designed for fundamentally different scenarios.
Multi-device feature vs. shared inbox — what each is actually for
- WhatsApp multi-device
- One person, one account, multiple access points. Useful for switching between phone and desktop. No team coordination.
- WhatsApp shared inbox (API)
- Multiple people, one business number, coordinated access with assignment. Each person has their own login. Full team visibility.
What should I look for when choosing a WhatsApp shared inbox platform?
The platform choice matters most at the point where the inbox needs to grow with your team — either in agent count, conversation volume, or the sophistication of automation you want to add. The basics (multi-agent access, conversation assignment, conversation history) are table stakes on any serious platform. The differentiators are in the details.
- AI agent capability: does the platform include a real AI agent you can train on your own knowledge base, or just basic keyword-triggered quick replies? There's a meaningful difference in what each can handle.
- Multi-channel support: if your team also handles Facebook and Instagram inquiries, a platform that unifies all three into one inbox is more useful than a WhatsApp-only tool — especially if you're running ads on Meta.
- Pricing model: does the platform charge per agent, per conversation, or a flat monthly fee? For a growing team, flat pricing is more predictable. Verify whether WhatsApp's per-message fees from Meta are included or separate.
- Mobile access: can agents and supervisors use the inbox from their phones, or is it desktop-only? For Singapore SMBs where staff often don't sit at desks, mobile access is practical, not optional.
- Onboarding support: does the platform offer hands-on help with WhatsApp number migration and initial setup, or is it self-serve only? Given that the BSP verification step can stall first-time setups, direct support is worth having.
- PDPA-compatible data handling: is data stored in a way that is private by default, role-scoped, and exportable? For Singapore businesses handling customer personal data, these are operational requirements, not nice-to-haves.
| Feature to assess | What a basic platform offers | What a stronger platform offers |
|---|---|---|
| AI agent | Keyword triggers and quick-reply menus | LLM-based agent trained on your own knowledge base — handles open-ended questions |
| Channel support | WhatsApp only | WhatsApp, Instagram, Facebook, Telegram, and others in one unified inbox |
| Assignment | Manual assignment by supervisor | Manual assignment plus auto-routing rules by keyword, tag, or returning customer |
| Reporting | Basic conversation count | First-response time, resolution time, agent workload, conversation trends |
| Mobile access | Inbox read/reply on mobile | Full inbox and automation management from mobile, not desktop-only |
How does KlyoChat's shared inbox work for Singapore SMBs?
We build KlyoChat, and this is the section where we walk through what the product actually does for a Singapore SMB moving from a single WhatsApp phone to a team inbox — because this is a MOF post and you're evaluating options, the details matter.
KlyoChat's inbox is a unified team inbox that brings WhatsApp, Facebook, and Instagram conversations into one view. Every conversation across all three channels is visible in the same queue, with the same assignment and routing tools. For a Singapore SMB that runs Facebook or Instagram ads alongside WhatsApp — which is most of them — this means one inbox for the inquiry volume from all three, rather than three separate tools your team has to check independently.
For WhatsApp specifically: KlyoChat connects to your WhatsApp Business number through the WhatsApp Business API. The guided setup walks through number verification with Meta and typically takes one to three business days. Once live, conversations appear in the shared queue immediately — no additional configuration is needed for the basic inbox to work.
- Unified inbox: WhatsApp, Facebook, and Instagram conversations in one view — no tab-switching between apps.
- Conversation assignment: conversations are assigned to named agents and visible as assigned to the whole team — no duplicate replies.
- Full conversation history: stored on KlyoChat's platform, accessible to all authorised agents regardless of device or shift.
- Internal notes and @mentions: team members can leave private context on a conversation and mention colleagues for input without the customer seeing it.
- AI agent included from Pro: custom AI agents trained on your knowledge base are included in the Pro plan, not a separate add-on. Pricing is flat — Basic $19/month ($15 billed yearly), Pro $49/month ($39 yearly), Business $129/month ($109 yearly).
- Private by default: conversations are encrypted, access is role-scoped, activity is audit-logged, and KlyoChat does not train models on your data. You can export or delete your data at any time.
- Honest limit: WhatsApp's per-message fees are charged by Meta on any platform, KlyoChat included — the platform subscription and Meta's fees are two separate costs. Verify current per-message rates on Meta's pricing page.
- Sign up and connect your channelsCreate a KlyoChat account at app.klyochat.com/signup — no credit card required for the 7-day trial. Connect your Facebook Page, Instagram Business account, or WhatsApp Business number through the guided OAuth flow. WhatsApp requires Meta verification and a business profile in good standing, which the setup wizard walks through.
- Add your team members with the right rolesIn the Settings section, add each team member by email and assign them a role: agent, supervisor, or admin. Agents see their assigned conversations and the unassigned queue; supervisors see the full team queue; admins configure everything. Most Singapore SMB teams have two to four agents, one supervisor, and one admin — often the same person who runs the business.
- Build the AI agent knowledge baseIn the AI Agents section, create an agent and add your knowledge base content: your operating hours, pricing or menu, delivery information, booking process, and the ten to fifteen FAQ answers that come up most often. You can add content as plain text documents, structured Q&A pairs, or by pasting your website content. The agent draws on this knowledge base to answer customer questions automatically.
- Set conversation assignment rulesDecide whether conversations will be self-assigned from the unassigned queue or auto-assigned by a supervisor. For most Singapore SMBs starting out, self-assignment from the pool is the simplest approach — agents take conversations from the unassigned queue and move them to their own view. You can add auto-routing rules later once you can see where assignment bottlenecks actually form.
- Test with real messages before full launchSend a few test messages to your WhatsApp number from a personal phone, walk through the assignment flow as a team member, and verify that the AI agent answers the questions it should. Check that conversation history persists correctly and that supervisor visibility works as expected. Run this test with the team before the inbox goes live to real customers.
A Singapore retail business moving to KlyoChat's shared inbox
- Before: single phone setup
- 3 staff sharing one business phone. Duplicate replies weekly. After-hours inquiries unanswered. No visibility into response times. History lost when one staff member left.
- After: KlyoChat shared inbox
- 3 agents with individual logins on their own devices. AI agent handles FAQ volume 24/7. Supervisor sees full queue. History persists across team changes. Zero duplicate replies in the first month.
A WhatsApp shared inbox is the first structural upgrade that makes WhatsApp work as a team channel rather than a personal one — and it's the foundation on which everything else, including AI agents and automation, becomes more effective. Without assignment and shared visibility in place first, automation creates a different kind of chaos: automated messages arriving in a queue where no one knows who's supposed to follow up. Get the inbox architecture right first, and the layers on top are straightforward to add.
