How to Set Up a WhatsApp Shared Inbox for Your Support Team

WhatsApp is where your customers want to talk. The problem is that the standard WhatsApp Business app only lets one person use it at a time. The moment your team grows beyond two or three people, you have a coordination nightmare: missed messages, double replies, no visibility into who owns what.

A WhatsApp shared inbox solves this by connecting your WhatsApp number to a team platform where every agent can see, claim, and reply to conversations — with full visibility, no duplication, and proper ownership tracking.

This guide explains exactly how it works, what you need, and how to get your team set up.

What is a WhatsApp shared inbox?

A WhatsApp shared inbox is a team platform connected to your WhatsApp Business API number. Instead of one person holding the phone or computer logged into WhatsApp Business, your entire support team logs into a central tool where all incoming WhatsApp messages appear in a shared queue.

Each conversation can be assigned to a specific agent, labelled, escalated to a ticket, or replied to — all with a complete audit trail so nothing gets missed. Think of it like a help desk, but built for WhatsApp.

Why the standard WhatsApp Business app is not enough

The WhatsApp Business app works fine for solo operators. For teams, it has serious limitations:

• Only one person can use it on one device at a time (or up to four with WhatsApp Business Multi-Device, but with no assignment or ownership)
• No way to assign conversations to specific team members
• No internal notes or handoff context
• No SLA tracking or escalation rules
• No integration with email, Instagram, or Facebook
• No audit trail for compliance or management visibility

For any team handling more than 20–30 conversations a day, the app becomes a bottleneck.

Step 1: Get access to the WhatsApp Business API

The WhatsApp Business API (now called the Cloud API) is what enables third-party platforms to connect to your WhatsApp number. Unlike the WhatsApp Business app, the API allows multiple users to access the same number simultaneously.

To get access, you need:

• A Meta Business Account (formerly Facebook Business Manager) — free to create at business.facebook.com
• A phone number that is not already registered with a personal WhatsApp account. You can port a number by deleting the existing account, or use a new number entirely.
• Business verification — Meta will ask for basic business details. Most businesses are approved within 1–3 business days.

Once verified, you connect your phone number to a WhatsApp Business API provider — which in this case is your shared inbox platform (like Resolvenyx). The platform handles all the technical setup and gives you a permanent webhook connection.

Step 2: Connect WhatsApp to your shared inbox platform

Once your WhatsApp API access is approved, you connect it to a shared inbox platform. Resolvenyx, for example, walks you through this in about 10 minutes:

1. Go to Settings → Inboxes → WhatsApp and click “Add WhatsApp inbox”
2. Enter your WhatsApp Business Account ID, phone number ID, and access token from Meta Developer Console
3. Copy the webhook callback URL shown in the platform and paste it into Meta — this is how Meta delivers incoming messages to your inbox
4. Set your verify token in both Meta and the platform to authenticate the webhook
5. Send a test message to your number to confirm the connection is live

After this, every WhatsApp message sent to your number will appear instantly in your team inbox.

Step 3: Invite your team and set up routing

With the inbox connected, invite your agents under Settings → Users. Assign them roles (Admin or Agent) and — if you use team-based routing — create team inboxes for Sales, Support, Billing, etc.

Good routing setup from the start saves a lot of headaches. A few things to decide:

• Manual assignment: agents claim conversations from an unassigned queue. Works well for smaller teams.
• Auto-routing rules: conversations are automatically assigned based on keywords, time of day, or customer data. Reduces response time significantly.
• Workload balancing: the platform monitors each agent’s active conversation count and distributes new ones to the least-loaded agent.

Step 4: Set up quick replies and templates

WhatsApp Business API requires that you use pre-approved message templates to initiate conversations with customers (i.e. send the first message). For replies to customer-initiated messages, you can send free-form text within a 24-hour window.

Set up quick replies for your most common responses (shipping updates, opening hours, return policies) so agents can respond in one click. This is a major time-saver once conversation volumes grow.

Best practices for managing a WhatsApp shared inbox

• Always assign ownership. Every conversation should have an owner. An unassigned inbox is a missed-message inbox.
• Use labels and tags. Tag conversations by topic, product line, or urgency so you can filter and report on them later.
• Set SLAs. Define target first-response times. Surface SLA breaches before they happen, not after.
• Use internal notes for handoffs. When handing a conversation to another agent, leave an internal note with context. Never make the customer repeat themselves.
• Create tickets for complex issues. Not every WhatsApp conversation is a quick fix. Convert complex ones to tickets so they get tracked properly.

The result: a support team that actually scales

Teams that move from the WhatsApp Business app to a shared inbox consistently see three things happen: response times drop, missed conversations drop to near zero, and agent satisfaction improves because the chaos goes away.

The setup takes a few hours, but the leverage is permanent. If your team is handling WhatsApp manually, this is the single highest-return infrastructure investment you can make.