One queue
WhatsApp and comments share the left list. Unread first. The contact card sits on the right.
Where is my order?
Dispatched this morning — UPI receipt is on your last request.
Product / Inbox
WhatsApp, comments, and DMs in one thread, with SLA and the contact history attached.
Answer without switching apps, and keep the trail on the person who wrote.

Support and sales desks that already live in WhatsApp and keep missing Instagram comments.
One queue, suggest-reply, assign, close, and broadcast follow-ups.
This is not a full contact-center ACD. Use Calling for outbound voice lists.
Use cases
A buyer asks “where is my order?” The thread already knows the contact and last UPI link.
You reply once, with context, instead of hunting chats on a phone.
An Instagram comment lands in the same inbox as WhatsApp.
Festival questions get answered before the post dies.
After a WhatsApp broadcast, replies come back here — not as a pile of unread phones.
You close the loop on the same list you messaged.
How to use it
Recreated from the live product so you can follow along before you create an account. Red circles mean a count or a remove — they are not decoration.
WhatsApp and comments share the left list. Unread first. The contact card sits on the right.
Where is my order?
Dispatched this morning — UPI receipt is on your last request.
Type yourself, or ask Helpers for a draft in the customer’s language. Assign or close so SLA stays honest.
Usually next
Cloud API numbers, approved templates, and broadcasts from the same workspace as Studio.
See how it works →
AI outbound agents, knowledge docs, and campaigns on Twilio or Plivo.
See how it works →
The shared book used by WhatsApp, SMS, email, calling, CRM, and ads.
See how it works →