Shared inbox
What is a shared inbox and when do you outgrow it?
A shared inbox lets a team work in the same mailbox. It works well until questions start running longer than a day.
In short
A shared inbox is a mailbox multiple people work in at the same time, where everyone sees the same messages and replies from the same address. Think info@ or support@. The difference from a personal mailbox is that a message belongs to nobody until someone picks it up, and that difference is both the strength and the problem of the format.
What a shared inbox does well
Everyone sees everything. A colleague can read along, take over a question and see what was answered before without forwarding anything. For a small team sitting together this is nearly always enough. You coordinate over the edge of your screen who does what, and it costs no admin at all.
The second strength is that customers write to an address, not a person. If someone goes on holiday the question still arrives somewhere people are looking. That's exactly why nearly every company starts with an info address.
Where it grates once questions run longer
As long as everything is done the same day, the inbox stays manageable. It starts to slide the moment a question has to wait on something: a delivery, a supplier, a colleague from another department. That email is neither finished nor active, and a mailbox has no word for that.
In practice self-invented habits appear. Marking as unread as a reminder. A folder called Waiting. An email to yourself. Each of those tricks is a status you keep in your head instead of in the system.
- Two people on the same email
- There's no owner, so two colleagues start an answer at the same time. The customer gets two emails, or worse: two different answers.
- Nobody knows how long something has been open
- A mailbox sorts by arrival date, not by how long the customer has been waiting. Last week's question sinks below this morning's.
- Forwarding is where the trail ends
- The moment a question goes to the warehouse or finance, it disappears from view. Whether an answer ever comes back depends on one person.
- There's nothing to measure
- How many questions came in, what were they about, how fast were they answered. A mailbox knows the answer to none of the three.
How many people fit in a shared inbox?
The question is usually asked as a number of people, but the number is rarely why it breaks. Two people with questions that run three days need statuses sooner than six people who close everything the same morning.
Lead time is more useful. If you close nearly every question within a day and rarely route anything to another department, a shared inbox is workable. If work structurally runs across multiple days, you're missing an owner and a status, and that gap grows with your volume.
What you take with you when you move
The address stays. Customers don't have to learn anything, because support@ remains support@. What changes is where you work as a team: the message still arrives at the same address, but gets a number, an owner and a status.
History is the second point. Old mail is where you look up what you agreed with this customer last time. Make sure that history moves along or at least stays searchable, otherwise the switch costs more lookup work in the first weeks than it saves.
Shared inbox or ticket system?
| Shared inbox | Ticket system | |
|---|---|---|
| Owner | Implicit, you agree verbally | Recorded on the ticket |
| Status | Read or unread | Open, in progress, waiting, resolved |
| Waiting time | Not visible | Timer per ticket, with SLA |
| Other channels | Email only | Chat, phone and forms alongside |
| Reporting | Manual counting | Volume, topic and response time |
| Learning curve | None, everyone knows email | A day of onboarding, plus agreements about statuses |
If you close nearly everything the same day without other departments getting involved, stay with the inbox. Once work sits waiting on something, status is the piece you're missing, and you can't rebuild that in a mailbox.
Where it goes wrong
Using folders as status
A Waiting or In progress folder looks like a status, but it's personal and invisible. If someone drags an email in and then leaves for a week, the question stalls without anyone noticing.
Marking as unread as a to-do list
This is the most common workaround and immediately the most fragile. A colleague opening the email just to read along accidentally switches off your reminder.
Rules that file mail away before anyone saw it
Filters that automatically move messages into subfolders take them out of the team's sight. What lands in a subfolder gets picked up structurally later than what stays in the main inbox.
Personal addresses alongside the shared address
If an agent replies from their own address, next time the customer emails that person directly. That question never reaches the team again and disappears when they're ill or leave.
Is your shared inbox still working?
Walk through these points before you think about a system. If more than two are true, the format is the problem, not the workload.
There's work in there nobody has picked up
Scroll to the emails older than three days. Every one without a reply that nobody misses is a question you can't see without statuses.
You can't say how many questions you got last week
Without that number you can't plan staffing and can't see whether a change on your site did anything.
Questions to other departments sometimes never come back
Forwarding without an owner means the customer reminds you instead of your system.
Customers send chasers
An email saying "haven't heard anything yet" is duplicate work you caused yourself. Count how many you get over one week.
Chat, phone or WhatsApp arrive too
As soon as the same customer writes through two channels, a mailbox can't tie the two conversations together.
What to do this week
Search your shared inbox for phrases like "haven't heard anything" and "following up" over the past month. The hit count is your cheapest measurement: that's work you gained because a question sat still. Then check five of those cases to see what the question was waiting on. Nearly always it's one of three things: another department, a supplier, or nobody.
What this looks like in a system
In Cuego the address stays and the workplace changes. Email arrives with the team, gets an owner and a status, and the customer card with orders sits next to it. Chat, phone and WhatsApp land in the same list, so the same customer doesn't become two separate conversations. If a question waits on another department, that becomes a task with a name on it instead of a forwarded email.
Shared inboxRelated terms
Ticket system
A ticket system gives every customer question a number, an owner and a status. That sounds administrative and is exactly what stops questions from getting lost.
Read onTicket routing
Ticket routing determines which question lands with which agent. Set up poorly, it costs you the first twenty minutes of every morning.
Read onOmnichannel
Omnichannel doesn't mean being reachable everywhere. It means a customer who switches channel doesn't have to tell their story again.
Read on