What is a unified inbox, and why one customer should be one thread

A unified inbox is one place where every message from every channel arrives: SMS, Instagram DMs, WhatsApp, Facebook Messenger, web chat and email. The important part is not the list of channels; it is that a customer who texts on Monday and DMs on Wednesday is one thread, with their record and history beside it, owned by one person on your team. Without it, the same customer is three conversations in three apps and nobody knows the whole story.

The problem it solves

A salon gets bookings by DM, questions by text, and complaints by Messenger. The DM app is on the owner's phone, the texts are on the front desk phone, and Messenger is checked when someone remembers. A customer who asked a question by DM and then texted to book is a stranger to the person reading the text. Replies are slow because nobody is watching all three, and things get missed because nothing counts what was missed.

What "unified" has to mean

One thread per customer, across channels. The DM and the text are the same conversation, because they are the same person. This needs the system to recognise the customer across channels, which is harder than it sounds and worth asking about.

The record beside the thread. Who they are, their appointments, what they were told last time, what they consented to. The person replying should not have to open another tool to find out.

One owner. Every conversation is assigned to a person or a queue, and it is visible who. Unowned conversations are how things get missed.

Reply on the customer's channel. The customer who DMed gets a DM back, from the same inbox, without the team member opening Instagram.

Same rules everywhere. The AI answers from the same knowledge on every channel, the same handoff rules apply, and the same consent and quiet-hours rules apply to anything outbound.

What it changes for a small team

The front desk works from one screen. The owner can see every conversation without holding every phone. Response times can be measured because every message has a timestamp in one place. The AI can take the first reply on every channel. And when someone is out, their conversations can be reassigned rather than sitting in an app on their phone.

What it does not replace

The phone. Calls are answered or missed; the missed ones become texts and land in the inbox, but the phone is still the phone. And it does not replace the customer record; it sits beside it. Our post on CRM vs inbox explains the split.

What to look for

Which channels are actually supported, natively, today. How the system matches a customer across channels and what happens when it is not sure. Whether assignment is enforced or optional. Whether the AI works on every channel or only on SMS. Whether you can see response time per channel and per person. And whether the record is in the same screen or a link away.

Frequently asked questions

Do I need every channel connected?

No. Connect the ones customers actually use. For most service businesses that is SMS first, then Instagram or Messenger, then WhatsApp if customers ask for it, then web chat.

What happens to conversations when a team member leaves?

They are reassigned in the inbox. Nothing lives on a personal phone.

Can the AI answer on Instagram the way it does on SMS?

Yes, from the same knowledge, if the platform supports Instagram natively and the account is connected.

What Frontiva does here

Frontiva's unified inbox brings SMS and its website chat widget together end to end today, with Instagram, Messenger and WhatsApp wired and waiting on Meta's app review for self-serve connection. Conversations can be assigned, tagged, prioritised, snoozed and annotated with internal notes, and each contact's CRM timeline holds every channel's thread. See inbox assignment.