One shared WhatsApp inbox for your whole team.
Real-time assignment, round-robin routing, internal notes, and seamless handoff between AI and humans. Built so agents never step on each other.
Real-time collaboration
Socket.io-powered updates. Every agent sees new messages, status changes, and assignments the moment they happen.
Rich media in both directions
Send images, video, voice notes, and PDFs from the composer. Inbound media renders inline — images, video/audio players, document cards — with private mirrored storage.
Every WhatsApp message type
Reactions as emoji pills, locations with Google Maps, contact cards, reply quotes, forwarded badges, deletions. No "[unsupported]" placeholders.
Smart assignment
Round-robin, least-busy, or manual. Only available agents enter rotation — mark yourself away and conversations skip you.
Human takeover
The second an agent replies, automation pauses for that conversation. No bot interruptions mid-chat.
Full audit trail
Every message, status change, and agent action is logged. Review who replied, when, and what the customer saw.
How it works
Connect WhatsApp
Use Embedded Signup to onboard in minutes, or bring your existing WABA. Your business account stays yours.
Invite your team
Add agents, admins, or analysts. Role-based access ensures everyone sees exactly what they should.
Start handling chats
New messages land in the shared inbox. Auto-assignment routes them; agents reply from any device.
Media that just works — inbound and outbound
Drop an image, video, voice note, or PDF into the composer and send; the file goes straight to WhatsApp’s media servers via the Cloud API, no public URL required from your side. Incoming media is mirrored to private object storage on receipt — your agents get instant previews backed by short-lived signed URLs, no more dead-link embarrassment when Meta rotates their CDN.
- Image, video, voice note, sticker, PDF, DOC, XLS, PPT supported
- Per-type size caps enforced client and server side (5MB image, 16MB video/audio, 100MB document)
- Signed URLs with 15-min TTL; bucket stays private
- Inbound media mirror protects against Meta’s 30-day retention window
Every WhatsApp message type, rendered natively
Customers send a lot more than text. WapiSnap parses each type and gives it a purpose-built bubble instead of a "[unsupported message]" fallback that most shared inboxes leak.
- Reactions shown as emoji pills overlaid on the target message (WhatsApp-native)
- Replies render a quoted strip above the body, just like the phone
- Location shares with map pin, coordinates, and a Google Maps link
- Contact cards with name, phones, emails, and org
- Order cards from your commerce catalog with line items and totals
- Forwarded badge, referral-from-ad source, deleted-message placeholder all first-class
Assignment that respects your workflow
Round-robin balances load across available agents. Least-busy keeps fast-responders productive without burning them out. Or assign manually when a specific agent owns an account.
- Workspace-scoped rotation pointers — fair across reconnections
- Mark yourself "away" to temporarily leave the rotation
- Re-assign with one click; customer never sees the churn
AI and agents, working together
Our flow engine runs automation until an agent takes over. The handoff is detected automatically — no checkbox, no special command. Resume the bot when the conversation closes, or let it stay in human mode.
- Per-conversation "human_handoff" state managed by the server
- Flow runs halt on takeover; future triggers are suppressed
- Typing indicator shown during flow execution (refreshed every 20s)
Frequently asked questions
Can multiple agents handle the same WhatsApp number?+
Yes. WapiSnap is built for teams — every agent in your workspace can reply from the same shared inbox. Assignment is per-conversation, so two agents never step on each other.
What kinds of media can agents send and receive?+
Images, videos, voice notes, and documents (PDF, DOC, XLS up to 100MB) flow both ways. Drop a file into the composer, add a caption, send — it lands on the recipient’s phone just like any WhatsApp message. Inbound media renders inline in the bubble: images open fullscreen, video and audio get native players, PDFs show as download cards.
How are reactions, replies, locations, and contact cards handled?+
Every WhatsApp message type is rendered natively — not a generic placeholder. Reactions appear as emoji pills on the target message, replies quote the original above the body, location shares link straight to Google Maps, contact cards list name + phones + emails, forwarded messages get a small badge, and deleted messages flip to "This message was deleted" automatically.
How does automation and human handoff work together?+
The moment an agent replies, the conversation is flagged as "human takeover" and all flow automation pauses for that contact. Automation resumes only when you explicitly end the session or after a cooldown window.
Do you support round-robin assignment?+
Yes. New conversations can auto-assign via round-robin, least-busy, or to a specific agent. Only agents marked "available" enter the rotation — mark yourself away and the next conversation skips you.
Are inbound messages real-time?+
Delivery is sub-second. We persist every inbound webhook and push updates over Socket.io — your agents see new messages instantly without refreshing.
What roles are supported?+
Four roles: Owner, Admin, Agent, and Analyst. Agents can chat and view assigned conversations; Admins configure flows, templates, and broadcasts; Analysts have read-only access to reporting.
Your WhatsApp. Your AI. Your rules.
Join businesses automating WhatsApp without vendor lock-in.