Every channel, one shared inbox.

Every conversation your flows hand over lands in one queue your team claims, replies to and resolves together. No juggling browser tabs to keep up with four channels.

Handles Webchat Intercom WhatsApp Telegram
The UniversalInbox agent workspace

Built for the way support teams actually work.

Every feature here exists because a team asked for it while working a real queue.

One unified queue

Every channel's conversations in one list. Filter by Mine, Unassigned, All or Snoozed, and search across the lot.

One thread, whoever spoke

Flow turns, customer turns and agent turns interleaved on one timeline, so nobody has to guess what was already said.

Claim and release

Replying claims the conversation and takes it off everyone else's queue. Release it when you're done, or hand it to someone better placed.

Internal notes

Work a conversation out with a teammate inline. Your team sees the note, the customer never does.

Drafted replies

SupportBuddy is built in. Switch it on and every conversation opens with a draft from your knowledge base for your agent to edit and send.

One customer, not four

The same person on WhatsApp and Intercom is one contact with one history, however many channels they use to reach you.

The flow, the customer and your team. One timeline.

When a flow reaches the end of what it can do, it pauses and passes the thread on. The next person picks up with the whole transcript already there, and no copy-pasting between tabs.

The flow steps aside

The moment an agent replies, the flow pauses. A conversation is driven by the flow or by a person, never by both. Put the flow back in charge when things are routine again.

Nothing gets re-asked

Whatever the flow already collected is in the thread and in the conversation record, so your agent starts from what the customer already told you.

Act from the thread

Claim, reassign, snooze or resolve from the thread header, without leaving the conversation you're reading.

Delivery you can see

Every outbound reply is tracked to sent or failed, on every channel, so a message that didn't land doesn't quietly disappear.

How it fits with the rest.

Every conversation starts in UniversalFlow and lands here. SupportBuddy drafts the replies for any flow you've turned it on for.

UniversalFlow
Required. Every inbox conversation comes from a UniversalFlow deployment, which owns the channel connection and everything the flow says before a person is involved.
SupportBuddy
Optional. Turn it on for a flow and drafted replies appear inline in the inbox. Leave it off if your team would rather write every reply by hand.
Knowledge
The wiki, documents and links those drafts are grounded in. Correct an answer once and both the flow and the drafts pick it up.

Put every channel in one queue.

Tell us which channels your team is juggling today and we'll show you the same conversations in one place.

Request a demo
This form is running on UniversalChatbot.