The moment a business sends its first large WhatsApp broadcast, the replies arrive faster than the team can read them, and by Monday afternoon nobody knows which of the 300 unread chats were already handled. WappBlaster's shared team inbox puts every conversation on one number in front of the whole team, with assignment, internal notes, tags and resolution states. What it cannot do on its own is decide your response promise, your ownership rules or your night-time plan. Those are management decisions, and this piece covers them.
Deciding the shared inbox SLA you promise customers
Write the SLA down in plain terms before configuring anything. A Dubai real estate brokerage might commit to "first reply within five minutes, 9 am to 9 pm, seven days", while a Pune B2B parts supplier might promise "within 30 minutes on working days". Both are fine if the team can meet them. What does not work is an unstated promise, because then every agent has a different one in their head.
- First response: the time from a customer's message to a human or useful bot answer.
- Resolution: the time until the question is closed, which may span days for a refund.
- Staffed hours: the window the promise applies to, stated per team if sales and support keep different hours.
WhatsApp shared inbox assignment rules that leave no orphans
Shared inboxes fail through politeness: everyone sees a new chat and nobody takes it. Fix this with explicit rules rather than goodwill.
- New chats from a campaign go to the team that owns that campaign, tagged with the campaign name.
- Existing customers go to their account owner if one is set on the contact.
- Everything else lands in a general queue that one person per shift is responsible for clearing.
- Reassigning a chat requires an internal note explaining what was already said or promised.
The shared inbox keeps the full thread visible on reassignment, so the next person does not ask the customer to repeat their order number.
Covering nights, weekends and holidays in a shared inbox SLA
A message that receives no reply until morning often turns into a second, angrier message. A small chatbot flow solves most of this: it acknowledges the message, tells the customer when a person will reply, and asks two or three questions (order number, issue type, a photo if relevant). When the shift starts, agents find chats with the details already collected. Customers who need urgent help can be given a phone number in the bot's reply. For more on the bot-to-human handover pattern, see this guide to WhatsApp chatbots for customer support.
Staffing the WhatsApp shared inbox for the hour after a broadcast
Replies cluster in the first hour or two after a campaign lands. Schedule campaigns for a time when the team is fully staffed, not at 7 pm on a Friday. If a broadcast includes quick-reply buttons such as "Call me" or "Send details", let the bot handle "Send details" automatically and route only "Call me" taps to people. Slow replies after a broadcast also matter beyond customer mood: unanswered customers are more likely to block or report the number, and that affects quality rating.
Reviewing shared inbox SLA performance beyond message counts
| Look at | Why |
|---|---|
| Chats open longer than your promise | Shows where ownership broke down |
| Resolution state mix (solved, pending customer, escalated) | Separates real backlog from waiting on the customer |
| Tags by issue type per week | Reveals recurring questions a bot or FAQ could answer |
| Chats reassigned more than twice | Usually a routing rule that needs fixing |
A weekly 20-minute review of these with team leads does more than a dashboard nobody opens.
Habits that quietly break a shared inbox SLA
- Agents also answering customers from personal phones, so half the history lives outside the inbox.
- Marking chats resolved to clear the queue when the customer is still waiting.
- A bot that loops with no way to reach a person.
- Promising a five-minute response for a team of two covering twelve hours; set a promise your rota can keep.
What running the WhatsApp shared inbox costs
The WappBlaster platform is a flat ₹7999 a year in India ($200 elsewhere). Replies your agents send inside the 24-hour customer service window are free-form messages, and whatever Meta charges for the templates you send is billed at Meta's own rate with nothing added.