The unified inbox

One thread per person, across text, email and web chat, with what the automation sent sitting in the same timeline as what a human typed.

Channels collapse into a person

A customer who texts on Monday and emails on Thursday is one thread, not two inboxes. Your team reads the conversation, not the channel.

The automation is not invisible

Every message an automation sent appears in the thread, marked as such, at the time it went. The most common failure in this category is a human following up on a lead who was already messaged twice by a sequence nobody could see.

Assignment and ownership

A thread can be assigned, reassigned, and left unassigned. An unassigned thread with an unanswered inbound message is the only queue that matters, and it is the default view.

Opt-out is honoured here too

A stop keyword arriving in this inbox marks the contact opted out immediately, everywhere, without configuration and without anyone having to notice it. The outbound gate reads that the moment it is written.