Every WhatsApp Chat In One Place
Both WhatsApp connection types—the official WhatsApp Cloud API and QR-linked WhatsApp—in a single inbox, with one thread per customer instead of one screen per number.
Features
One thread per customer
Open and close conversations as the work progresses, and leave internal comments the customer never sees.
Tags that do double duty
Tag a customer in the inbox and that tag becomes a campaign audience. Support context turns into marketing targeting with no export step.
An AI assistant on the side
Optional intent detection, sentiment, and suggested replies you can accept or ignore.
Everything the customer ever sent
Order confirmations, cart chases, campaign replies and bot conversations all land on the same thread, so nothing is answered twice.
Use Cases
Handoff from a bot
When a bot flow reaches its limit it drops the conversation here, in full context.
Two numbers, one history
Messages from QR-linked WhatsApp and the WhatsApp Cloud API land on the same customer profile.
Tags that drive campaigns
Tag a customer in the inbox and that tag becomes a campaign audience.
How the unified inbox actually works
Every WhatsApp conversation — whether it came in through your QR-paired number or your official WhatsApp Cloud channel — lands in one thread per customer, so no one on your team is juggling two screens. Open or close conversations as you work through them, leave internal notes your customers never see, and tag customers right from the thread to use in campaigns later. When a bot flow hands a conversation to a human, your agent inherits the full history.
- AI conversation insights: shows each conversation's intent, sentiment and a suggested next step — you decide when to look, nothing sends automatically.
- AI reply suggestions: three ready-to-send replies appear next to the message box; edit or send as-is.
- Full customer context: the profile, purchase history and segment sit right next to the conversation.
- Only WhatsApp threads live here — SMS, email and web push are send-only and don't need replies.
Documentation for this feature
Browse the full documentation
Products
