The Problem with WhatsApp on Personal Phones
Every support team using WhatsApp eventually hits the same wall. An agent handles a customer from their personal phone. The customer's history is locked to that device. When the agent is sick, on leave, or resigns, the conversation is gone. Nobody knows what was promised, what's been resolved, or who is waiting. There's no way to measure response times, track which agent is handling what, or ensure every message gets answered.
The WhatsApp Business API, paired with a shared inbox platform, solves every one of these problems. Here's how to set it up properly for a support team.
What "Shared Inbox" Actually Means
A shared inbox means every inbound WhatsApp message goes to a single browser-based interface that your entire team can access simultaneously. No one needs a phone in front of them. Messages don't go to any one person's device — they go to the inbox, where:
- Any available agent can see and claim unassigned conversations
- A supervisor can assign conversations to specific agents
- Every team member sees the full conversation history, regardless of who replied before
- Resolved conversations move out of the active queue, keeping it clean
This is possible only with the WhatsApp Business API — not the regular WhatsApp Business app, which limits you to one device and no shared access.
Setting Up Your Shared WhatsApp Inbox
Step 1 — Connect your WhatsApp number to Tenreply
If you're starting fresh, Tenreply's guided onboarding connects your WhatsApp Business Account through Meta's Embedded Signup. You'll need:
- A Facebook account with admin access to a Meta Business Manager
- A phone number not currently on any WhatsApp account (or willing to migrate)
- Business verification details (optional for low volume, required above ~1,000 messages/day)
The full setup takes 20–40 minutes. Once connected, inbound WhatsApp messages start appearing in the Tenreply inbox immediately.
Step 2 — Invite your support team
Go to Settings → Team Members → Invite by email. Agents receive an email, create a password, and log in from any browser. Tenreply doesn't charge per seat — add as many agents as your team needs.
Roles:
- Owner — full admin, billing access, can see all settings
- Admin — can manage settings and view reports, cannot change billing
- Agent — inbox access only, no settings changes
Step 3 — Set up conversation assignment
Tenreply supports both manual and automatic assignment:
- Manual — a supervisor or senior agent assigns each conversation to a team member from the inbox
- Automatic (round-robin) — configure an automation rule to distribute new conversations evenly across your team
- Keyword routing — route conversations containing "refund" or "billing" to your billing specialist; "technical issue" to tier-2 support
Assigned agents receive a push notification (if the mobile app is installed) and the conversation appears at the top of their queue.
Step 4 — Configure SLA rules and status workflows
Define what "resolved" means for your team. In Settings → Conversation Statuses, create custom stages like:
- Open (default for new messages)
- Waiting on Customer (agent replied, waiting for customer)
- Escalated (needs senior review)
- Resolved
Agents update status as they work through conversations. The queue view filters by status so supervisors can see what's stuck, what's pending, and what's done.
Step 5 — Create canned replies for common questions
Support teams spend a huge amount of time typing the same answers repeatedly. Canned replies (saved responses) let agents type a shortcut like /refund and instantly expand it to your full refund policy explanation. This reduces handle time and ensures consistent, accurate information across your team.
Set these up in Settings → Automations → Quick Replies. Build a library of 20–30 responses covering your most common queries and your response time drops immediately.
Tracking Team Performance
Once your team is running on a shared inbox, the data that was previously invisible becomes measurable.
First Response Time
How long from when a customer message arrives to when your team first replies. For most support teams, a target under 5 minutes during business hours is achievable with a properly staffed inbox. Tenreply's analytics dashboard shows this per agent and as a team average.
Resolution Rate
What percentage of conversations reach "Resolved" status, and how long does it take. A conversation sitting Open for 48 hours is a flag.
Volume per Agent
How many conversations each agent handled. Useful for workload balancing and identifying whether round-robin assignment is working.
Channel Breakdown
If you're running WhatsApp + Instagram + Facebook Messenger in the same inbox, the analytics break down volume and response times by channel — useful for staffing decisions.
What Changes When You Move Off Personal Phones
Teams that switch from personal WhatsApp apps to a shared inbox typically report three immediate improvements:
- Nothing falls through the cracks — every unassigned conversation is visible to everyone; it's someone's job to claim it
- Handoffs become seamless — when an agent is away, the next agent sees the full conversation history and picks up without asking the customer to repeat themselves
- Supervision becomes possible — team leads can see the real-time queue and intervene when conversations go off track
Next Steps
If your team is currently managing WhatsApp from personal phones or a single-agent Business app, the move to a shared inbox is one of the highest-leverage operational changes you can make. Start a 14-day free trial on Tenreply — connect your number in under an hour, invite your team, and see the difference on day one.