NextoraOne queue for every channel: what omnichannel actually has to do
Omnichannel is not a list of logos on a pricing page. It is one queue, one thread per customer across sources, an owner on every conversation, and a start-here tab. Here is the anatomy that makes it work.
Every vendor claims omnichannel. In practice most deliver a set of separate inboxes wearing one skin: Telegram here, email there, the website widget somewhere else, and a human in the middle doing the joining. The customer who wrote on the site at 11:00 and on WhatsApp at 11:20 becomes two conversations and, eventually, two answers.
The test is simple. Does the same person, writing from two places, produce one thread with one owner? If not, what you have is a channel aggregator.
One queue, two kinds of row
In Nextora the Inbox is a single queue for the whole company: a message on Telegram, WhatsApp or Instagram, an SMS, an email to your work address, a chat with the website bot — all of it lands in one list. The job is always the same: read it, give it an owner, reply, close it.
The list holds two kinds of row, and they behave differently:
| Row | Where it comes from | What you can do |
|---|---|---|
| Customer conversation | Telegram, WhatsApp, Instagram, SMS, work email | Assign, reply, close |
| Bot dialogue | The chatbot on your site or in a messenger | Take over, hand back to the bot |
A customer conversation carries an unread count, a channel pill and an owner. A bot dialogue carries the bot's state instead of an owner, because there is nobody to hold accountable until a person steps in.
One customer, one thread
If someone chats to the site bot and then writes on Telegram, that is one row and one feed: messages from both sources run together in time order, each labelled with where it came from. Only an anonymous visitor's dialogue — nobody to tie it to yet — stays on its own row, and it renames itself the moment they leave a name or become a lead.
This is the part that is genuinely hard to retrofit, and the part that decides whether agents trust the tool. A merged thread means the reply you are typing has the whole story above it.
The row that tells you where the customer is standing
A website visitor writes into the widget before introducing themselves, so the row reads "Guest · /pricing" — the page they wrote from. Search finds them by that page too. Knowing someone is asking from the pricing page changes the answer.
Tabs slice by owner, chips slice by channel
These are two different questions and they should not share a control. The tabs answer "whose is this": All, Mine, Unassigned, Snoozed, Closed. The channel chip answers "where did it come from": only Telegram, only email, only the site widget.
Two design details are worth copying:
- Unassigned is where a shift starts. Making "nobody owns this" a first-class tab with its own counter turns an invisible failure into the first thing anyone sees.
- The channel list is built from the conversations on screen, not from a catalogue of everything the product supports. You never filter by a channel you do not use. And every mail transport — Gmail, Outlook, Resend, your own SMTP — counts as one Email channel: when triaging, what matters is that it is a letter, not what sent it.
What does not belong in the queue
Your personal mailbox. It lives in its own section. The shared queue holds what a customer wrote; the moment it also holds newsletters and internal threads, the counter stops meaning anything and people stop reading it.
The same discipline applies to search and loading: the queue loads in batches and search looks at the rows on screen, so an older enquiry needs Load more or the Closed tab. Being explicit about that beats a search box that silently pretends to cover everything.
Triage is a workflow trigger, not a habit
Once conversations are one queue with owners, the routine parts stop needing a human. "Message received" and "email received" are workflow triggers like any other — assign by rule, tag by keyword, create the lead, escalate when nothing has happened for N hours. Which of the four automation tools to reach for is a separate question, covered in pipeline, workflow, form or template.
And when a bot cannot answer, the handoff has somewhere to go: a supervising AI employee on duty picks up the dialog, answers under her own name, or passes it to a person with a reason.
A short checklist for evaluating any inbox
- Two messages from the same person on two channels — one thread or two?
- Is there a tab for conversations nobody owns, with a number on it?
- Does a reply from an agent go out on the channel the customer used, without them thinking about it?
- Does the conversation attach to the customer record, so the next person sees it on the lead or the deal?
- Can an automation start from an incoming message, or is triage forever manual?
Anything that fails the first two will fail on a busy day, no matter how many logos are on the pricing page.
See the queue in the product on the conversations page.
See it on your own process.
Nextora is in private alpha: CRM, projects, ERP, omnichannel conversations and AI employees on one record model. Bring the process you want to fix and we will shape the workspace around it.