Omnichannel Inbox

An omnichannel inbox is a single workspace where an agent receives, reads and replies to messages from every contact channel (WhatsApp, email, web chat, Instagram, Facebook, phone) without switching applications. Unlike having one tab per channel, all conversations land in the same queue and are routed to the right agent based on capacity, priority or skill rules.

The key is that every message is tied to the same contact and their unified history: the agent sees the earlier WhatsApp conversation even if the customer switches to email later. This turns scattered service into a continuous experience, and it is part of what Sellium runs on top of the sales and service CRM, where the inbox rests on the customer record rather than on isolated mailboxes.

How it works inside

An omnichannel inbox is fed by connectors that bring in messages from each platform through its APIs (for example, the WhatsApp Business API for messaging, or webhooks from social networks and web forms). Once inside, a routing engine decides which agent handles each conversation based on availability, workload and skills. Meanwhile, the system tracks the status of each conversation (open, on hold, resolved) and applies SLA rules so nobody is left without a reply within the committed time.

The real value shows up when the inbox is connected to the CRM: every conversation is linked to the contact, their company and their history. The agent replies with full context (purchases, previous tickets, stage in the pipeline) and does not ask the customer to repeat what they already said. That is what sets an omnichannel inbox apart from a simple chat aggregator.

Multichannel is not the same as omnichannel

This is the most common conceptual mistake. A company can be multichannel (present on many channels) without being omnichannel. The difference lies in whether the experience feels continuous or whether each channel is an island.

Omnichannel is the strategic principle; the omnichannel inbox is the operational tool that makes it possible in the team's day-to-day work.

Why it matters for a business in Latin America

In Argentina and the region, WhatsApp is the dominant channel for commercial contact: many small and midsize businesses handle sales and after-sales service there. The typical problem is that three or four people share the same number from one phone, without knowing who replied to what, with no history and no metrics. When that number grows, service becomes chaotic.

A concrete example: a consumer goods distributor receives orders over WhatsApp, questions over Instagram and complaints by email. Without an omnichannel inbox, a sales rep closes an order over WhatsApp and, two days later, another agent receives the complaint by email without knowing that customer had already bought. With an omnichannel inbox on top of the CRM, both see the same record, the complaint is resolved in minutes and there is a record of who handled it and how long it took.

Common mistakes when implementing it

• Confusing having many channels (multichannel) with having them integrated (omnichannel): adding channels without unifying the history multiplies the mess.
• Not connecting the inbox to the CRM: without the customer record, the agent replies blind and the context is lost.
• Leaving WhatsApp out by using the free app instead of the API: the consumer app does not support multiple agents, routing or real metrics.
• Not defining routing or SLA rules: conversations pile up in a queue with no owner and response times skyrocket.
• Ignoring traceability: if there is no record of who replied to what, there is no way to measure productivity or service quality.

Well implemented, an omnichannel inbox reduces first response time, keeps conversations from getting lost and gives the sales team a single source of truth about every customer, no matter where the message came in.