Every address in the firm ends at one person. The fix is structural. Create one shared address per kind of work, enquiries, billing, support, that the whole team can see and answer. Name one person responsible for each address and write down what gets escalated and how. Keep your own address for the few things only you decide. Then read what is left in two fixed blocks a day with the phone's mail notifications off. This takes less self-discipline than you are already spending, and more setup.
One week of sorting
Spend one working week writing down what arrives, sorted by kind. The sender is the wrong thing to sort on: your biggest client sends enquiries, billing queries and status chatter, and those three go to three different places. A useful set of buckets for a firm of three to twenty people runs: enquiries from people who have not bought yet, project questions from current clients, billing and invoices, supplier mail, software notifications, newsletters, and internal status from your own staff.
Internal status is the cheapest bucket to remove. It does not need to arrive as a message that pulls you off a task; it needs saying once, in a fixed place. Move it into a 30 minute weekly review and the inbox loses a category.
The shared addresses
Create enquiries@, billing@ and support@ as addresses several people can open, then point each kind at its address. Three tools do this inside suites small firms already pay for, and they differ on who can see that a message has been answered.
In Microsoft 365, a shared mailbox stores up to 50 GB of data with no license assigned to it, and several people can be given permission to open it. Going past that limit is a licensing job. Raising it to 100 GB needs an Exchange Online Plan 2 license on that mailbox.
In Google Workspace, turn a group into a Collaborative Inbox and members can assign a conversation to themselves or to another member, then mark it resolved with printed statuses of complete, needing no further action, or duplicate. Assignment and resolving need moderation permissions, so somebody has to switch those on before staff can use the workflow. Google's page states no plan requirement for the feature, so the cost under it is seats: Business Starter shows $3.50 per user per month on a first-term promotion and $7.00 per user per month at the standard annual rate, prices as shown 2026-10-28. Ten staff at the standard annual rate is $70.00 a month.
Dedicated shared inbox tools buy workflow. Front lists its lowest paid plan, Standard, at $19 per user per month billed annually with a free tier below it, and Help Scout shows Standard at $25 per user per month, both prices as shown 2026-10-28. A firm answering one enquiries address rarely needs either.
Exhibit 1
Mail routed by kind to shared addresses leaves far fewer kinds sitting on the owner than mail routed to one personal address
The shared address beats forwarding because the question is answered by whoever is free, and the thread stays visible to everyone who comes after. A forwarded message is a copy living in one person's account. When that person is on site all week, nobody else knows it exists.
One named person per address
Each shared address gets one named person responsible for it, and that is a different job from answering it every day. Responsible means the person who notices when nothing has been answered and keeps the routing rules current. That person tells you when volume has outgrown the arrangement. This is a good pick for the first real responsibility you hand over, and it fails when nobody writes down what escalation means.
Write one rule per address. Our default reads: escalate by forwarding to the owner with one line saying what you want, never by cc. A forward is a request with an ask attached. A cc tells everyone on the line that somebody else is watching.
On Gmail, delegation is the lighter option: a delegate can read, send and delete mail in your account, and the delegate's address appears on messages they send. Gmail Help, as read on 2026-10-28, allows up to 5 delegates on a personal account and up to 10 on a work or school account. It suits an assistant handling your calendar; a team answering enquiries wants a shared address.
Filters, receipts and the unsubscribe pile
Your own address keeps only what you decide, and everything that files itself gets a rule. In Gmail on a computer, open Show search options in the search box, enter the criteria, then click Create filter at the bottom of the window. One action a filter can take is Skip the Inbox (Archive it), which removes matching mail from the inbox without deleting it: receipts, appointment confirmations, software notifications, hosting invoices, newsletters. Filters act on mail that arrives after you create them, so the old pile needs one separate pass.
Unsubscribe requests belong in the routing plan. The FTC's CAN-SPAM guide says you must honor a recipient's request to stop email within 10 business days, so those requests go to a shared address with a name against them. The clock counts business days, so a request that lands before a long weekend has less slack than it looks.
Two reading blocks and a phone with mail off
Set two fixed blocks, morning and late afternoon, and let everything that survives the filters sit until then. Gloria Mark reported in ACM Queue in 2022 that the average person checks their email 15 times per day, a summary of her own logging samples. Watch how often you check on your own account, since message count tells you less.
In a 2016 CHI study by Gloria Mark and colleagues, 40 information workers were tracked with computer logging, biosensors and daily surveys over 12 workdays, and batching email went together with higher rated productivity. The same paper reports no evidence that batching lowers stress, so do not buy this arrangement on a calm promise. The study's framing is the useful part. People who check email on their own terms report better productivity than people who jump when a notification fires.
In the 2012 CHI study by Dabbish, Babu, Iqbal and Mark, email awareness such as new mail notifications and unread counts was associated with more frequent checking. The finding points at the visible badge, which is why the phone's mail notifications go off. A check becomes a decision you take in one of the two blocks, which is what the context switching research covers for the rest of your day.
Microsoft's Work Trend Index special report of June 17, 2025 says the average worker receives 117 emails daily, most skimmed in under 60 seconds, and puts the average gap between meeting, email and notification pings at two minutes during core hours for its heaviest 20% of users. It also measures traffic outside hours: more than 50 messages per employee sent or received outside core business hours, and nearly a third of active workers back in the inbox by 10 pm. Those are aggregated Microsoft 365 telemetry figures from a corpus ending February 15, 2025, and they describe employees inside big companies.
Two small mechanics make the blocks survivable. Snooze in Gmail takes a message out of the inbox and returns it to the top at a time you pick, so a mid-afternoon arrival waits until your morning block. Snooze is personal. It clears your view of an address while your colleagues keep theirs, so never snooze something a colleague still needs to see. Schedule send holds a written message and sends it at a time you set, which keeps drafting hours and sending hours apart, and Google warns that a scheduled message may go out a few minutes after the time you set.
The first day, in order
- Write the list of kinds on one page from the week's notes.
- Create one shared address per kind, three at most to begin with.
- Give every staff member permission to open all three, and remove permission from anyone who has left.
- Turn on assignment and resolving in Google Groups, which needs moderation permissions set first, or add team permissions to the Microsoft 365 shared mailbox.
- Write one routing line per kind: who answers it, in what order, what a full answer contains.
- Write the escalation rule in one sentence where staff can see it.
- Build filters on your own address for receipts, software notifications and newsletters, using Skip the Inbox (Archive it).
- Point every unsubscribe request at the billing address, with one person owning the 10 business day clock.
- Move status updates into the weekly review, set the two reading blocks in the calendar, turn off mail notifications on the phone.
Day one ends with a bulk archive of everything that arrived before today.
Exhibit 2
Nine setup steps take an address from first arrival to answered by the team on day one
Cc is where the cost hides
The cc field lets a sender stop carrying a message. It buys the sender the feeling of having informed people, and it costs everyone on the line a decision about whether to open it. Nobody on a cc line is responsible, so a long cc thread goes unanswered. Clients get told once that enquiries go to one address, and staff get told that copying the owner is not an escalation. A cc on a complaint leaves no name against the reply.
What still reaches you personally
Keep your own address for the short list where someone is asking for your judgment. A client who asks for you by name gets your address and keeps it. A complaint comes to you, because a complaint is about the firm, which makes it yours. Anything with a signature attached comes to you, and anything that moves money comes to you: a payment dispute, a vendor invoice you have not approved, a client asking to change terms. Staff matters that are not status, meaning a person, a pay packet or a resignation, come to you.
Everything else never arrives: newsletters, receipts, software notifications, appointment requests, supplier promotions, cc'd threads, and the general questions your repeated customer questions already have a written answer for. Your address becomes a decision queue, and the rest of the week gets built around it.
Exhibit 3
Only four kinds of mail need the owner's own address and everything else is filed by rule
Tell clients once, then prove it works
One line in every signature covers the change: enquiries go to the enquiries address, billing questions to the billing address, and both are answered by the team. Put the same line in the out-of-office message you write today and leave it there after you stop being away. Change the address on your website contact page the same week, because a form that posts to a personal mailbox rebuilds the problem in one click.
The sign the arrangement worked is a week you were away. You come back and find the enquiries address answered, with a resolved status on each thread and nothing forwarded to you except the things that needed you. Merlin Mann's Inbox Zero defined zero as the share of your own attention sitting in the inbox, not the number of messages in it, from his 2006 articles and his 2007 video. It is a practitioner's slogan and never a study, and the definition is the part worth keeping: an inbox full of unread newsletters can be at zero, and one client message you keep rereading is not.
Where an AI pass fits, and when
An AI triage pass belongs after the structure exists. A model sorting a mailbox with no routing rules makes a faster pile. A model reading one shared address can label what needs a reply, what is a repeat question with a written answer, and what is a complaint a person should read first. Set the addresses, the owners and the escalation rule, then add an AI triage pass to draft routine replies inside the hours you have already fixed.
The part we take on in a firm this size is the routing plan: the list of kinds, which address each one lands at, who is responsible, what gets escalated and how, and the two reading blocks written into the week. That is the management consulting we do before touching anyone's mail settings.