Wachat's shared inbox is built on the official WhatsApp Business Cloud API and Meta's Messenger/Instagram Graph APIs, with native connectors for Gmail and Microsoft 365 over OAuth. Every inbound message — a WhatsApp interactive button reply, an Instagram story mention, a Gmail thread, a web widget chat — lands in the same queue with the contact already deduped against your CRM. Agents see the customer's last order, last campaign, lifetime value and previous tickets in a right-hand context panel, so they never have to ask "what's your email again?"
Routing is rule-driven and channel-aware. You can pin all Hindi-language WhatsApp conversations to your Delhi team between 10:00 and 19:00 IST, route Instagram DMs containing the word "refund" straight to a senior agent, and let the web widget auto-assign by URL path — pricing-page visitors go to sales, docs-page visitors go to support. The same engine handles re-assignment when an agent goes offline, when a ticket breaches its 30-minute SLA, or when a customer replies after a snooze.
Collaboration happens inside the conversation, not in a separate Slack thread. Agents can leave private notes, @mention a teammate, attach a 50 MB voice memo or PDF, and tag the thread with one or many labels. Every action — assignment change, status flip, label edit, note added — is timestamped in an immutable audit log that admins can export to CSV for compliance reviews. Supervisors get a live "floor view" of who is typing, who is idle, and which conversations are at risk of SLA breach.
Because the inbox shares the same contact graph as Wachat's CRM, Broadcasts and Flow Builder modules, a single reply can trigger a tag update, a deal stage move, or a follow-up sequence. A customer who replies "STOP" to a marketing template is automatically opted out of all future broadcasts; one who replies "RESCHEDULE" can be handed to a booking flow without an agent ever touching it. The inbox is the surface, but the entire SabNode stack is doing the work underneath.