WhatsApp shared inbox for teams working from one business number

Without a unified inbox or clear ownership, conversations on separate numbers can become fragmented. A customer who messages twice can reach two different people, and neither sees the other's answer or any earlier promise.

Centralized chats give you one inbox and one record. Multi-agent live chat then becomes a question of ownership: who answers this message, and who picks it up if they are away?

Treat WhatsApp as a channel, not your system of record. Orders, invoices and approvals should still live in the tools built for them, with the chat pointing to the correct item.

Two agents answering one customer is the classic shared-inbox failure. One offers a refund while another asks for a photo, and your customer now has conflicting answers from a single number.

Set one rule for your team: claim the chat before you type. Agents who see a claimed chat leave it alone, and add anything useful through its owner.

Test this before launch. Ask two colleagues to open the same thread at once, then check that both can see who holds it.

One real hazard is that someone may send an internal note back to the customer. On a shared number, that mistake reaches the person the note was about.

Keep internal discussion visibly separate from the reply box. If your workflow has no separate note field, use your team chat and paste in the customer's reference instead of their message.

Write every note as if it could be read aloud. That habit helps limit the damage from a misplaced paste.

Early chat routing does not need software logic. Write down your topics, name one owner per topic, and let agents pick from a shared pool when nothing matches.

For example, send delivery questions to dispatch, new inquiries to sales, and complaints to a team lead. Balanced chat distribution matters less at first than making sure every topic has a named person.

Review the rules monthly. Suppose one person keeps getting reassigned chats from a topic. That topic has the wrong owner, or your team needs another agent there.

Tags are useful when they drive an action. Keep a short list such as new lead, awaiting customer, awaiting supplier and refund. Then filter chats by tags at the start of each shift.

Follow-ups need a date as well as a label. Add the next action in a custom field or your tracking sheet, so nothing depends on an agent's memory.

Retire any tag your team has not used in a month. Long lists produce inconsistent labels, and reports built on inconsistent labels mislead you.

Decide who sees what before you add staff. Typical roles are owner, manager, team lead and agent. Some tools let agents see only their own client chats.

Sensitive threads need extra care. Payment disputes, health details and HR matters should have a named owner and a written rule on who else may read them. Assess security terms, contracts and controls before handling protected health information.

Put one direct question to any tool you evaluate: can you see who sent, assigned or changed what? An audit trail settles disputes faster than recollection.

Saved replies keep answers consistent for hours, returns and delivery times. Store your approved wording centrally, and let agents adapt the opening line to the customer's actual question.

Plan for images, videos, documents and voice notes too. Customers send photos of faults and receipts, so agree on where your team saves them and how long those files stay on devices.

For broadcasts, WASenderPlus allows up to 3 message body variants, each with merge fields. These are WASenderPlus operational settings, not WhatsApp-published limits or guarantees.

Pacing spreads outbound sends over time; replies may arrive immediately or much later. WASenderPlus defaults to a gap of 4–40 seconds between sends, and allows up to 250 sends a day on a fresh number.

At that spacing, 250 sends span roughly 17 minutes to 2.8 hours, excluding processing delays and pauses. That arithmetic comes from the setting alone, and it is not a delivery or response-time estimate.

A warm number allows up to 6,000 a day, after 2 weeks of warm-up. These are configurable WASenderPlus caps, not WhatsApp-published limits or guarantees. Platform restrictions may still apply below them. Staff the inbox for your send window.

A reply such as yes means nothing without its campaign. Before each broadcast, tell agents what went out, who received it, and what a correct answer looks like.

Add a campaign column in your Google Sheet, then share that sheet with whoever covers the inbox. Agents can check a contact quickly instead of guessing which offer they mean.

Track delivered, read and replied status where your tool shows it. Use those signals to plan cover and follow-up, not as proof of what caused a sale.

Customers message outside your schedule. Set a business-hours reply or away message that states when your team returns, and avoid promising a response time you cannot staff.

Plan for absence as well. Name a backup for every owner, so a vacation or sick day triggers reassignment rather than a queue of unanswered chats.

At the start of each shift, review anything left overnight. An unanswered chat should sit at the top of someone's list until it has a reply.

Pick two measures: first-response time and resolution time. Set targets from your own staffing and past threads, rather than borrowing another company's figures for a different kind of customer.

Where your tool lacks reports, sample manually. Review a set number of chats each week and note the wait, the owner, and whether the customer had to repeat anything.

Add an escalation rule for chats past your target. Name the person who takes over, so a late reply becomes a team problem instead of an individual one.

The free WhatsApp Business app allows linked devices, and WhatsApp's current pages set the device and messaging limits. Read those pages directly, because these details change, before you decide whether it can carry your team.

The app may suit you if a few people answer modest volume, and your customers mostly start conversations. It offers basic quick replies, welcome messages and away messages.

You have probably outgrown it when chats need owners, staff change often, or broadcasts create replies that one person cannot clear. Moving means new habits, so budget for agent training.

List three things before any migration: your number, your existing chat history, and every device currently connected. Establish what WASenderPlus imports, how long history is retained, and how it can be exported or deleted.

On the WhatsApp Business Platform, Meta makes approval decisions and sets its own process. Read Meta's current requirements, then check whether coexistence is available for your account, provider and US market.

Tell agents what changes on day one: where they log in and how they claim chats. Also name who answers questions during the first week.

Inbox pricing mixes several things. Separate your per-seat fee, your platform fee, and any Meta template charges. Then model your actual team size against each line before comparing tools.

WASenderPlus lists two plan prices: Entry at $6/mo and Team at $19/mo. Check the pricing page for agent terms, billing basis, currency, additional charges and what each plan includes.

If you use the API route, read Meta's current rate card and your provider's terms. Rates change and vary by market, so a saved screenshot soon goes stale.

Plenty of tools add no-code chatbot builders, keyword triggers and AI conversation summaries. They suit high volumes of repeated questions, provided a human handoff carries the full thread to the agent.

Others combine Instagram Direct, Facebook Messenger and web chat, or link to Shopify, Zapier and webhooks. Treat none of these as a WASenderPlus feature unless current documentation for your plan confirms it.

Start from your workflow. If your list lives in a spreadsheet and WhatsApp is your main channel, a Sheets-based setup may cover what you need.