Three hundred emails a day is one message every ninety seconds across a working day. If half need a real reply and each takes four minutes, that is ten hours of writing, which no team of two absorbs. The playbook is therefore not about replying faster: it is about cutting what needs an original reply, deciding ownership in one pass rather than three, and watching four numbers. Everything below assumes you keep your existing mailbox.
Do the arithmetic before anything else
Most teams at this volume have never counted, and the count changes what you do next. Spend one week measuring three things: how many messages arrive, how many need a reply written by a human, and how long a reply actually takes.
A typical result for a small business at 300 a day: about 40% is automated notification, supplier confirmation and copy-in noise, roughly 60% needs an answer, and an answer takes three to six minutes. That is 180 replies and nine to eighteen hours of writing per day.
Read that number honestly, because it settles the argument. If it comes out above the hours your team actually has, no amount of organisation fixes it. You are choosing between three levers: reduce the incoming volume, reduce the per-reply time, or add people. Software helps with the second and only the second.
Cut the volume before you organise it
The cheapest reply is the one you never write.
Get the notifications out of the shared address. Order confirmations, form submissions, monitoring alerts and delivery notices do not belong where humans triage. Send them to a separate address, or filter them into a folder somebody scans once a day. This alone is often 30 to 40% of the arrival rate, and it is an afternoon’s work.
Answer the top five questions publicly. At this volume the same five questions are 30 to 50% of what people ask. Opening hours, lead times, how to change an order, where to send a document, what your prices include. Put them where the question gets asked, on the page people write from, not buried in a help centre. Every one you deflect is four minutes back.
Kill the copy-in habit internally. Teams at this volume are usually copying each other on outgoing mail as a way of staying informed. It doubles the internal volume and informs nobody. A shared history replaces it: if everyone can see the conversation, nobody needs a copy of it.
Triage once, not three times
The expensive failure at volume is not slowness, it is re-reading. A message that three people open, evaluate and leave has cost three times what it should, and it is still unanswered.
The rule is one pass. Whoever opens a message decides one of three things, immediately: I answer it now, I own it and will answer later today, or it belongs to someone else and I say so. Nothing is opened and left in the same state it was found.
Two habits make that possible.
Two-minute rule, adapted. If the answer takes less than two minutes, write it now. At 180 replies a day, deferring a two-minute reply costs more in re-reading than in writing.
Ownership by topic, decided in advance. Quotes to one person, scheduling to another, complaints to whoever handles the account. Deciding at the moment of triage who takes what is a meeting held 180 times a day. Deciding once, by category, is a meeting held once.
Cut the time per reply
Templates for the top ten situations. Not thirty: ten. Enough to cover what repeats, few enough that finding one is faster than writing. And each one gets its first sentence rewritten every time, otherwise your customers can tell. Our library for a small business is in customer reply email templates.
Internal notes instead of forwards. At volume, forwarding to ask a colleague a question is what breaks the shared history, because the reply then comes from their address. A note on the conversation costs seconds and keeps the thread whole.
Stop polishing internal-facing replies. A supplier confirming a delivery date does not need three drafts. Reserve the care for the messages where it changes the outcome.
The four numbers to watch
Weekly, not daily. Daily numbers at this volume produce anxiety rather than decisions.
Unclaimed after four hours. The count of conversations nobody has taken. This is the leading indicator: it moves before response times do, and it is the one number that predicts a customer being forgotten.
Time to first reply, median. Not the average, which one bad week destroys, and not resolution time, which depends on things outside the mailbox.
Follow-ups containing “I already wrote”. The closest measurement you get of what you missed entirely. One a month in a small team is already a lot.
Storage used, as a percentage. Unglamorous and worth watching, because at 300 emails a day with attachments the ceiling arrives. A Microsoft 365 shared mailbox holds 50 GB without a licence and 100 GB with Exchange Online Plan 2, and when it fills it starts bouncing mail back to whoever wrote to you.
Two ceilings that arrive at this volume
Worth knowing before you hit them, because both are documented and neither is obvious.
The 25-user ceiling. A Microsoft 365 shared mailbox supports a maximum of 25 users, and beyond that Microsoft warns of connection failures or duplicated messages. A team at 300 emails a day that keeps growing will reach it, and the platform’s own advice at that point is to change object entirely.
The sending limits. A Google Workspace account sends 2,000 messages a day per user, with 10,000 total daily recipients. Comfortable for 180 replies, and not comfortable at all if the same account also sends a seasonal announcement: the daily allowance is per account, so everyone working that mailbox shares one. And if a third-party tool sends over SMTP, POP or IMAP rather than the Gmail API, the per-message recipient limit drops from 2,000 to 100.
The full set is in shared mailbox limits.
What the playbook looks like in one page
- Measure for a week: arrivals, replies needed, minutes per reply.
- Route notifications away from the human address.
- Publish answers to the five most-asked questions.
- Assign ownership by topic, once, not per message.
- Triage in one pass: answer now, own it, or hand it over.
- Ten templates, first sentence rewritten every time.
- Notes instead of forwards.
- Watch four numbers weekly, starting with unclaimed after four hours.
Where a shared inbox becomes non-optional
Below about fifty messages a day, spoken conventions and the rules in shared inbox etiquette hold. At 300, they do not, and the reason is mechanical rather than cultural: every convention that requires a person to signal something manually is forgotten in proportion to how busy they are.
With Trupeo you connect the mailbox you already have, Gmail, Outlook, Microsoft 365 or any IMAP provider, and the signals stop depending on memory. Each conversation carries one owner and an open or done status, internal notes live on the message, and a colleague already writing is visible before anyone opens anything. The unassigned view gives you the leading indicator directly, and the flat price means growing the team to absorb the volume is not also a budget conversation.
See the features and our pricing, or start with the complete shared inbox guide.
Frequently asked questions
How many people do you need for 300 emails a day?
Do the arithmetic rather than guessing: if 60% need a human reply and each takes four minutes, that is 180 replies and about twelve hours of writing a day. Two people can hold it only if you cut the volume that needs an original reply, which is what routing notifications away and publishing your top five answers do.
How do you organise a high-volume shared mailbox?
Triage in a single pass, with ownership decided in advance by topic rather than per message. Whoever opens a message answers it, claims it, or hands it over, and never leaves it as they found it. Re-reading is the expensive failure at volume, not slow replies.
What metrics matter for a team inbox?
Four, weekly: conversations unclaimed after four hours, median time to first reply, the number of follow-ups saying “I already wrote to you”, and storage used as a percentage of the ceiling. The unclaimed count is the leading indicator, because it moves before anything a customer notices.
Is inbox zero realistic for a team?
Not as a goal, and it is the wrong one. What matters is that nothing is unowned, not that nothing is open. A conversation that has an owner and a due answer is under control even if it sits for a day; an empty inbox where three conversations were quietly filed is not.
At what volume does a shared mailbox stop being enough?
Coordination breaks long before capacity does, typically at three people answering daily. Microsoft’s documented ceiling of 25 users on a shared mailbox, with its warning of connection failures or duplicated messages beyond, is the point where the platform itself stops coping.
Sources:
- About shared mailboxes in Microsoft 365: the 25-user maximum with its connection failures or duplicated messages warning, the 50 GB and 100 GB storage limits, and the behaviour when a mailbox reaches its limit.
- Gmail sending limits in Google Workspace: the 2,000 messages per day per user, the 10,000 daily recipients, and the drop to 100 recipients per message over SMTP, POP and IMAP against 2,000 in the interface.
- Exchange Online limits: the storage quotas applying to shared mailboxes by plan.