Every small company reaches the same moment. A customer writes to support@, and two colleagues answer within the hour: one promises a refund, the other asks for order details. The customer now has two contradictory emails and one clear impression: nobody here talks to each other.
The week after, the opposite happens. Everyone sees the message, everyone assumes someone else has it, and nobody answers at all.
Both failures have the same cause: the tool. A forwarding rule or a cc list distributes copies of a message, but it cannot distribute responsibility. That is the job of a shared inbox.
What a shared inbox is
A shared inbox is one email address, support@, hello@, whose conversations live in a single workspace the whole team can see. Every message exists exactly once, with a visible status: open or answered, assigned to a specific person or waiting for one. Anyone can look at the queue and know what is handled and what is not.
Customers notice nothing. They write a normal email and receive a normal email. The change happens entirely on your side of the wall.
Five signs you have outgrown forwarding
- Double replies. Two teammates answer the same message because neither could see the other typing.
- Silent gaps. Messages everyone saw and nobody took, the classic diffusion of responsibility.
- "Who has this?" messages. Coordination has moved to Slack, where you now maintain a second, worse inbox about the first one.
- Vacation black holes. The answer to a current customer question sits in an absent colleague's personal mailbox.
- History walks out the door. When someone leaves, every conversation they handled leaves with their account.
Two or more feel familiar? The forwarding rule has done its job and can retire.
Distribution list, shared inbox or helpdesk?
| Forwarding / cc list | Shared inbox | Full helpdesk | |
|---|---|---|---|
| Where messages live | Copies in personal mailboxes | One shared workspace | One shared workspace |
| Ownership | Invisible | Assigned per conversation | Assigned, plus queues and SLAs |
| What customers see | Normal email | Normal email | Often ticket numbers and portals |
| Setup effort | Minutes | An afternoon | Days, plus ongoing admin |
| Typical cost | Free | Low, often flat | Per agent, per month |
The middle column is where most small teams belong, and many stay there permanently. The right column, ticket queues, SLA policies, approval flows, earns its complexity in larger support organizations, not at five people.
The features that actually matter
Shopping for a shared inbox, you will meet long feature lists. Four things carry the weight:
- Assignment. One click that makes a conversation someone's job.
- Collision detection. Seeing that a colleague is already replying, before you both do.
- Internal notes. Discussing a tricky case inside the conversation instead of in a parallel Slack thread.
- Basic metrics. At minimum your first reply time, so you know whether you are actually getting faster.
Everything else, workflow engines, custom fields, dashboards, is optional at small scale.
Where AI changed this category
A classic shared inbox organizes work; it does not do any of it. That has changed. A modern inbox can categorize incoming messages, detect their language, and draft a reply from your own knowledge base before anyone opens the conversation. The team's job shrinks to reviewing and sending, and for routine categories, even that can be automated.
That combination, shared inbox underneath and AI on top, is what FirstReply is: email, WhatsApp, Instagram and other channels in one queue, every conversation arriving pre-sorted and pre-drafted, at a flat price rather than per seat.
The point is not the tool
A shared inbox is thirty minutes of setup. What it buys is the thing customers actually measure you by: every message gets exactly one answer, reasonably fast, from someone who clearly knew what they were doing. The rest is decoration.