By Tina16 Nov,2026
When several people answer the same WhatsApp account, “someone replied” is not the same as “someone owns the case”. A shared inbox becomes useful when it makes ownership, context and pending work visible, not merely when it lets another employee open the messages.For ecommerce teams, there is a second question: how does WhatsApp support sit alongside marketplace conversations? A buyer's phone number and a marketplace username should not be treated as the same identity without reliable evidence.
1. Decide what you need beyond access
List the problem that prompts the purchase. It may be overlapping replies, missing handovers, supervisor visibility or the need to see WhatsApp and supported shop messages in one workspace.
Do not assume every team needs the same technical setup. The WhatsApp Business App supports linked-device use, with limits and additional capabilities depending on the plan and current availability. A provider-based Business Platform setup serves different workflow requirements and brings its own costs and migration questions.
| Requirement | What to ask a supplier to show |
|---|---|
| Conversation ownership | Assignment, reassignment and absence coverage |
| Human and bot coordination | How automatic sending changes on takeover |
| Message visibility | Which message types and history reach the inbox |
| Marketplace support | Exact supported channels, countries and shop permissions |
| Supervisor review | Relevant access without sharing unnecessary credentials |
| Connection failure | Alert, fallback and recovery process |
Ask whether the proposed setup uses the Business App, an approved Business Platform route or another officially supported arrangement. Do not accept an ambiguous “WhatsApp integration” label as a technical explanation.
Confirm what happens to the existing number, app use and history. Coexistence or migration behaviour depends on the supported route and provider. Request a written explanation for your account before changing a number used by active customers.
The Business Platform is not, by itself, a complete agent workspace. The inbox and workflow are supplied by the chosen application or provider. Check those capabilities separately from the underlying messaging connection.
Avoid unofficial connection methods that put the account at risk. Verify the supported setup through current WhatsApp guidance and the provider's documented process rather than sharing a QR code or account access with an unverified party.
Use a sample where an agent answers a product question, then the buyer reports an order problem. Assign it to the appropriate colleague and inspect what moves with the conversation.
The next person should see the issue, relevant facts and outstanding action. Test whether the previous agent can still send accidentally and whether AI continues to answer. A colour-coded status is not useful if staff cannot tell who is responsible.
Check a shift change as well. Have the first owner become unavailable and confirm how the backup receives the pending work. This is often more revealing than assigning a brand-new conversation during a sales demonstration.
A unified inbox can reduce switching without proving that every contact belongs to the same customer. Ask how the product matches records, handles uncertainty and prevents an agent from seeing the wrong order.
For example, a buyer may message on WhatsApp about a Lazada order while using a different name. The safe next step is an appropriate order verification workflow, not automatically merging accounts because the names resemble each other.
Use only the information needed to handle the enquiry. Avoid requesting payment credentials or broadcasting order details in a shared group. Review role access and data handling with the responsible business owner.
| Cost item | Question to settle |
|---|---|
| Inbox subscription | Which seats, channels and workspaces are included? |
| WhatsApp charges | Which current message categories, destinations and provider fees apply? |
| AI usage | What event creates a billable unit? |
| Setup | Who configures the connection and templates where required? |
| Maintenance | Who updates knowledge and monitors failed transfers? |
| Exit | How can the business retain records and move the number appropriately? |
Ask for a worked quotation using your likely inbound workload and any permitted outbound messaging. Do not assume a seat price includes all WhatsApp or AI usage. Equally, do not compare a complete quote with another vendor's entry-level headline alone.
Treat sending eligibility and message cost as separate questions. Paying for a provider does not remove the need to follow current WhatsApp policies and the supported messaging workflow.
Run one representative shift with clear success criteria: complete reception, fewer overlapping replies, faster handover and no loss of order context. Include knowledge maintenance and supervision in the effort assessment.
Duoke is worth evaluating when WhatsApp sits beside supported marketplace channels and the team wants coordinated routine answering. Verify the specific WhatsApp setup, channel scope and Lite functions in your account. Do not infer every WhatsApp API capability from the fact that an inbox can receive messages.
Choose the setup that your staff can operate reliably, including during absences and service interruptions. Extra features add little value if nobody can explain where an unresolved conversation goes next.

Email:[email protected]
Address:6/F MANULIFE PLACE, 348 KWUN TONG ROAD, KOWLOON, Hong Kong, 999077