How to set up a team inbox on the WhatsApp Business API
A single WhatsApp Business number can only be logged into the app on one phone at a time — which is exactly why growing support and sales teams outgrow it fast. A team inbox on the official WhatsApp Business API lets several agents answer the same number simultaneously, with conversation assignment, internal notes and a full audit trail. This guide walks you through setting up a shared team inbox in InfiQ end to end: inviting agents, defining roles, routing incoming chats, and going live without breaking your quality rating or opt-in compliance.
What you'll do
Connect your WhatsApp Business API number in InfiQ, invite agents and assign roles, configure routing rules and canned replies, test with your own number, then go live. Most teams finish in under 30 minutes because InfiQ handles the platform plumbing for you.Step 1 — Confirm your API number is live in InfiQ
A team inbox sits on top of an active WhatsApp Business API number, so this has to be in place first. Open your InfiQ dashboard and check that your number shows a Connected status with a green quality rating and a completed display-name approval. If you are still on the consumer WhatsApp Business app, you cannot share it across agents — you first need to migrate to the API. This is the one part of the process that involves Meta Business Manager verification, and it is worth getting fully done before you invite anyone, so agents land in a working inbox rather than a half-configured one.
- Verify the number status reads Connected, not Pending or Flagged
- Confirm your Meta Business Manager is verified and the display name is approved
- Note that your BSUID (Business-Scoped User ID) stays under your ownership on InfiQ
- If you are on the WhatsApp Business app, migrate to the API first
Step 2 — Invite your agents and assign roles
Go to Settings and then Team (or Users) and invite each agent by email. Every person you add gets their own login, so nobody shares a device or a session — this is the core advantage of the API inbox over the phone app. As you invite, assign a role that matches how much each person should see and do. A tight role setup prevents junior agents from reassigning conversations they shouldn't touch, while giving managers the oversight they need. Start conservative: it is easier to widen permissions later than to claw them back after a mix-up.
- Admin — full control over settings, billing, numbers and every conversation
- Manager — sees all conversations, can reassign and pull reports
- Agent — handles chats assigned to them, adds internal notes, uses canned replies
- Send invites in batches so you can test routing before the whole team is in
Step 3 — Set up routing so chats reach the right person
Without routing, every incoming message lands in one shared pile and agents step on each other. Routing rules decide who a new conversation goes to. In InfiQ you can auto-assign by team (sales versus support), round-robin across available agents to balance load, or route on a keyword or the template the customer replied to. The single most important rule is the fallback: define a default agent or team that catches anything no other rule matches, so a chat is never left unassigned and ignored. Once an agent picks up a conversation, it stays with them until it is resolved or explicitly reassigned, which keeps the customer talking to one person.
- Round-robin to spread load evenly across online agents
- Team-based routing to split sales enquiries from support tickets
- Keyword or template-based routing for structured entry points
- A fallback rule so unmatched chats always land somewhere
Step 4 — Add canned replies and internal notes
Canned replies (saved quick responses) are what make a team inbox fast. Create a small library for your most common answers — order status, business hours, return policy — so any agent sends a consistent, on-brand reply in one click instead of retyping it. Pair these with internal notes: private comments agents leave on a conversation that the customer never sees, perfect for handing a chat over with context. Remember that free-typed replies only work inside the free 24-hour service window that opens when a customer messages you; once that window closes, re-opening the conversation requires an approved template in the correct category, so keep a couple of well-worded utility templates ready for that case.
- Build canned replies for your top 10 repeat questions first
- Keep wording consistent so the number feels like one voice
- Use internal notes for handovers — they never reach the customer
- Have utility templates approved in advance to re-open expired windows
Step 5 — Test with your own number, then go live
Before your team relies on it, prove the whole flow end to end. Message the business number from your personal WhatsApp and watch what happens: the conversation should appear in the inbox, hit the right agent per your routing, and show delivery and read status correctly. Try a canned reply, add an internal note, and reassign the chat to a second agent to confirm handover works. When that behaves as expected, announce the number to customers and switch monitoring on. In the first days after going live, watch response times, delivery failures and your quality rating closely — a team inbox usually improves speed, but faster replies still have to respect opt-in and the right template categories.
- Send a test message from your own phone and follow it through routing
- Check delivery and read receipts are updating in the inbox
- Test a canned reply, an internal note and a reassignment
- After launch, monitor response time, delivery failures and quality rating