Shared Inbox for Small Business: Why Five Inboxes Fail

A shared inbox for small business is one email address — hello@, office@, bookings@ — that more than one person can open, answer, and see the full history of. It replaces the arrangement most small businesses actually run on: four or five personal inboxes, each holding a different part of the story, none of which anyone else can read. It costs nothing extra on the email account you already pay for, takes an afternoon, and you notice the difference the first week somebody is off.

If customers currently reach you at your own name@ and you forward the ones that are not yours, this is the change worth making before you automate anything else.

What is a shared inbox, and how is it different from forwarding?

Forwarding moves a copy of a message. A shared inbox moves the whole conversation — the original, every reply, and the record of who said what — into a place two or three people can stand in at once.

The difference sounds administrative until you watch it fail. When you forward an enquiry to your colleague, you now have two half-conversations: yours, which ends at the forward, and theirs, which the customer sees but you do not. Nobody owns the thread. If the customer replies to the original message rather than the new one, it lands back with you, three days later, with no sign that anything happened in between.

A shared address has one thread, and everyone who needs it can read the whole thing without asking anybody to dig it out.

Why do five personal inboxes fail?

They do not fail loudly. They work perfectly well on an ordinary Tuesday with everyone at their desk, which is exactly why the problem is invisible until it is expensive.

The week someone is off

Somebody is ill, or on holiday, or has simply gone to a job with no signal. Their inbox is still receiving. Quotes, complaints, a supplier chasing payment — all arriving, all unread, all invisible to everyone else in the business. You find out when the customer rings, annoyed, and you have nothing to look at while they talk.

An out-of-office does not solve this. It tells the sender nobody is reading, which is honest, and then nobody reads.

The customer who asks twice

People do not remember which of your addresses they used last time. They send to whichever one is in their phone. So the same question arrives at two people, gets two answers, and the two answers are slightly different — different price, different lead time, different tone. The customer is not being difficult. They are watching your business disagree with itself.

The handover that cannot happen

Somebody leaves, or moves off the front desk, and years of conversation leaves with them. Not stolen, just unreachable: everything a customer agreed, every quote given, every promise made, sitting in a personal mailbox that nobody else has a reason to open. This is the same problem as not knowing who can reset the password, and it has the same cure — put the thing in the business’s name, not a person’s.

What does a shared inbox for small business actually change?

Four things, in the order you will notice them.

Cover becomes possible. Anyone on the rota can answer, because anyone can see. Being off stops meaning work stops.

Answers get consistent. When the last six replies to the same question are sitting there in the thread, the seventh matches them without anybody writing a script.

The address outlives the person. Staff change; office@ does not. Customers never have to be told a new address, and nothing has to be migrated when somebody moves on.

You can finally see the volume. Once everything arrives in one place, you can count it. How many enquiries a week, how many are the same five questions, how long replies actually take. That count is the only honest starting point for deciding what is worth automating — and most owners have never had it.

How do you set one up without buying anything new?

You almost certainly do not need new software. Both of the big email providers include this, and you are probably already paying for one of them: Microsoft 365 calls it a shared mailbox, and Google Workspace does it with a collaborative inbox. Helpdesk products are worth money later, at volume. They are not the first step.

Pick one address, and make it boring

hello@, office@, bookings@, accounts@. Say what it is for, not who reads it. Resist having six — one per department is a structure for a business with departments. Two is usually right: one for customers, one for money.

Decide who answers what, in writing

A shared inbox with no owner becomes a room everyone walks past. Decide who is responsible on which days, and what “done” looks like — replied, or replied and the job is in the diary. This takes ten minutes and it is the step people skip, which is why they conclude shared inboxes do not work.

Move the history, then redirect the old addresses

Do not start empty. Move the live threads in so the context comes with it, then forward the personal addresses to the shared one and tell regular customers once. Keep the old addresses alive for a year — people do not update their contacts because you asked them to.

A real example: the addresses we gave Receiply before it had a single user

When we launched Receiply, our receipt-scanning app, it shipped with support@receiply.co and privacy@receiply.co. Neither is a person. At the time there was no team to share them with and it would have been quicker to use a personal address — nobody was writing in yet.

We did it anyway, for one reason: those addresses are printed inside the app and in the store listings on two platforms. An address published in a place you cannot easily edit is a decision you only get to make once. Had it been a name@, changing who answers would have meant a store update on iOS and Android and a release of the app itself.

That is the general version of the rule, and it holds for a plumber’s van livery as firmly as it does for an app listing. Wherever an address is printed somewhere you cannot easily change, it should never be a person’s name. You are not planning for a team you do not have. You are avoiding a change you will not be able to make cheaply later.

When is a shared inbox the wrong answer?

When the business is genuinely one person and intends to stay that way, the overhead is real and the benefit is mostly the address-outlives-you point. Still worth it, but do not expect it to change your week.

It is also the wrong answer if you are reaching for it to fix a workload problem. A shared inbox makes the volume visible and shareable; it does not reduce it. If four hundred emails a month are drowning two people, four hundred emails will still arrive. What changes is that you can now see the pattern, which is what tells you whether the fix is another pair of hands, a better FAQ, or an automation worth paying for.

FAQ

Does a shared inbox cost extra?

Usually not. Shared mailboxes in Microsoft 365 and collaborative inboxes in Google Workspace are included in the plans most small businesses already have. Dedicated helpdesk tools are priced per user per month and are worth it at volume, not at the start.

Will two of us accidentally reply to the same email?

Occasionally, early on, and it is embarrassing rather than costly. Both providers show when a message has been read or replied to. A rota — who is on the inbox today — prevents it far more reliably than any feature.

Should customer emails and invoices go to the same address?

No. Keep money separate, because the people who answer customers and the person who chases payment are usually not the same, and the urgency is different. Two addresses is plenty for most small businesses.

What about GDPR and customer data in a shared inbox?

A shared inbox is generally easier to defend than personal ones, not harder: access is granted and removed deliberately rather than sitting in somebody’s mailbox after they have left. Grant access to the people who need it, remove it when they move on, and write down who has it.

Is this worth doing before automating anything?

Yes, and it is the main argument for doing it now. Nobody can sensibly automate what nobody can count. One address gives you the volume, the repeat questions and the real response times — the three numbers any honest automation quote should start from.

Where this leads

Once everything lands in one place, the repeat questions become obvious, and the case for automating the dull half of them makes itself. We build workflow automation for businesses, and the first question we ask is always how many of these you actually get in a week. If you cannot answer that yet, a shared inbox is the cheaper thing to do first — and if you can, tell us what arrives and we will tell you which parts are worth automating and which are not.