What Is a Unified Inbox?
TL;DR
A unified inbox is a single view of incoming mail from several mailboxes, so replies to outreach sent from many addresses arrive in one queue. It exists because outbound at volume spreads sending across multiple mailboxes, and checking each one separately is how replies go cold.
Why does outbound need a unified inbox?
Because the reply and the mailbox that earned it are separated by design. Spreading sends across mailboxes protects each one, and it scatters the responses across as many inboxes, several of which nobody opens as their own daily mail.
Response time is the cost. Interest from a cold email decays quickly, so a reply found two days later is answered after the reason for it has passed, and the campaign gets recorded as having produced a reply and no meeting.
What does a unified inbox need to do beyond collecting mail?
Classify, attribute, and stop the sequence. Inbound has to be separated into genuine replies, automatic replies, opt-out requests and bounces, because those need four different responses and only one of them is a person to answer.
It also has to carry state: which campaign and contact the reply belongs to, who owns it, and whether it has been handled. Collecting mail into one place without that state moves the problem rather than solving it, since a shared queue with no ownership is a queue two people answer and one nobody does.
Frequently asked questions
A shared mailbox is one address that several people can open. A unified inbox is many addresses presented as one view, with the campaign and contact context attached to each thread, which is what outbound needs because the sending is deliberately spread across addresses.