Aksel Distribution — Inbox
4 conversations- 09:47
Everest Hardware
Messenger · Can we open a trade account?
- 09:41
Bikash Traders
Instagram · Do you have the 12mm in stock?
- 09:52
Gorkha Builders
Facebook · Commented on your contractor post
- 09:44
Sunita Rai
WhatsApp · Reorder — same as last month, Pokhara
Four channels, one ordered list. Live, over a socket — not on a refresh.
Unified inbox
Four channels arrive. One list, in the order they were sent.
Instagram, Facebook Pages, Messenger and WhatsApp deliver into the same thread list. The identity that decides which thread a message joins is composed server-side from your own connection row — never from the webhook payload, which is what stops one customer becoming two conversations.
In the workspace
The thread, with everything attached to it
An owner, the branch it belongs to, the tags it carries, the notes your team left, and the history of every channel this customer has used.
Example workspace — Aksel Distribution, branches in Kathmandu, Pokhara, Biratnagar.
One conversation identity per customer per channel, resolved server-side
Assignment, tagging, notes and unread state shared across the team
Delivery status from the platform, including a rejected send
Real-time delivery over Socket.IO — not on a refresh
Channels
What is connected
Each channel with the state it is actually in. Two of these are planned, and say so here rather than in a footnote.
- InstagramDirect messages and comments on Business accountsAvailable
- Facebook PagesPage messages and Messenger threadsAvailable
- WhatsApp BusinessCloud API, plus a QR-linked Web connectionAvailable
- Web chatA chat widget on your own sitePlanned
- TikTokComments and direct messagesPlanned
Delivery you can see fail
Outbound messages carry the platform's own delivery status. A send the platform rejected is shown as rejected, rather than sitting in the thread looking sent.