← All posts

Sorting a shared inbox without reading every email

Automation · 19 November 2026 · 8 min read

A shared info@ inbox is a decision queue disguised as a mailbox. A five-step method for a five-person electrical contractor: name what actually arrives, filter on sender domain and thread rather than subject, surface one urgent list, make the reply carry the four questions you always ask, then give each category an owner.

The scenario

A five-person electrical contractor in Brisbane. The office has one inbox, info@, and everyone sees it. The owner checks it on the phone between jobs. The bookkeeper checks it for invoices. The two electricians have it on their phones because, once, a client sent a photo of a switchboard and nobody saw it until the next day.

On a typical Monday the inbox holds about ninety emails. Nine of them are things that matter: a new enquiry, a variation approval, a supplier invoice, a client saying the power is off and they need someone today. The other eighty are invoices addressed to the bookkeeper, software notifications, a tender newsletter nobody reads, replies in a thread that has already been settled, and a surprising amount of spam that has decided info@ is a good address.

So the real work is not answering email. The real work is deciding, ninety times, which eight of these need a person. That decision happens morning and last thing at night, it belongs to whoever looked last, and it is exactly the kind of repetitive sorting that a machine is better at than a tired person.

This post is how that contractor sorts the inbox without reading every message, in a way that still lets a human see everything that needs a decision.

Why "auto-sort into folders" is not the fix

The first thing most owners try is rules. Anything with "invoice" in the subject goes to an invoices folder, anything with "enquiry" goes to enquiries, and so on. It takes an afternoon and it half works.

Then reality happens. A client replies to a quote email with the subject "Re: Your quote — 14 Smith St" and writes "yes, go ahead, but can you do the Thursday instead". The rule sees a quote email from an existing thread and files it as done. Nobody notices for a week. That is worse than not automating, because the email now lives somewhere nobody checks.

Folders also do the wrong job. They move things out of sight, so the only way to know nothing was missed is to open every folder, which puts you back where you started. Sorting that no one trusts is sorting you still have to verify.

What you actually want is not a tidy inbox. It is a very short list, every morning, of the emails that need a decision, with everything else visible but out of the way.

The method

Five steps. You can run the first three this week.

Step one: work out what the inbox is actually for

Sit with the person who is in the inbox most and list the kinds of email that arrive, in plain words, in rough order of how much of them there are. Not by sender, by what the sender wants. For the electrician it looks like this.

  • New work: someone wants a job done.
  • Existing work: a client on an open job, usually about timing or access.
  • Money in: supplier invoices and remittances.
  • Money out: a client telling you they have paid.
  • Noise: software notifications, newsletters, marketing.

Write it on one page. Most inboxes have four to seven real categories, and everything that does not fit is one of two things: a category you forgot, or something that should not be coming to this address at all.

That last group is the cheapest win and the one people never count. Every newsletter and notification is a small thing that a person has to re-decide about each day. Unsubscribe or redirect them before you build anything. It usually removes a third of the inbox and requires no tool.

Step two: separate the sender from the subject

Most sorting rules are built on the subject line, which is written by whoever sent the email and is often wrong. Two duller signals are far more reliable.

The first is the sender's domain. A supplier invoice from your electrical wholesaler comes from the same domain every time. A client replying from a personal address does not. A rule that says "anything from this wholesaler's billing address goes to accounts" is almost never wrong, and it never needs updating.

The second is whether the email is part of a thread you already started. If it is a reply to a quote you sent, it is about existing work, regardless of what the subject says. If it is a brand new thread from an unknown address, it is closer to an enquiry.

New thread, unknown sender: enquiry. Reply to our own thread: existing work. Known wholesaler: accounts. No reply expected: noise.

That is the whole filter, and it is four lines of logic, not a machine learning project.

Step three: pick the one sort that catches the urgent ones

Do not sort the inbox into folders in step three. Sort it into one thing: the list you look at first.

The mistake is trying to categorise everything. An enquiry that sits until lunchtime costs a job. A supplier invoice that sits until Thursday costs nothing. Same inbox, wildly different urgency, and the sort should reflect the money, not the volume.

For the electrician, the first list is: new threads from an address that is not a known supplier, plus anything containing a photo attachment, plus anything from a client who is on a job happening in the next two days. That is maybe a dozen emails. He reads those on the phone in two minutes and ignores the rest until an allocated hour.

Everything else is still there, just lower. Nothing is deleted and nobody has to trust a black box. It is the same inbox, ordered by consequence.

Step four: make the reply the normal case

The enquiries don't need you to write back from scratch. Nine out of ten ask the same things: what suburb, is it a switchboard or an outlet, when it needs to happen, can you send a photo.

If the first reply asks for exactly those four things, and says when you'll get back to them, then the email is doing the work of the phone call. It also sets the shape of the answer you get back, because people tend to answer what they are asked.

Keep this in your own words and from your own address. Set it as a saved reply that can be inserted in one keystroke, not sent automatically from a robot, for the first month. You want to read the replies at this stage, because they are telling you whether the filter and the four questions are right.

Step five: make the inbox send to the right person, not just sort

Sorting still leaves the question of who acts. The supplier invoice is not for the owner, it is for the bookkeeper. The remittance is for the bookkeeper too. The job enquiry is for whoever quotes.

Once the categories are stable, which takes a few weeks, each category gets an owner and a place. Accounts go to the bookkeeper's saved view, not a folder. Enquiries land in the quoting list, which for many small businesses is a spreadsheet, and get a row with a date.

The rule of thumb: if an email needs something done that is not "read and reply in under an hour", it belongs in a list somewhere else, with a date on it. An inbox is a place for decisions, not a place for work in progress.

What will break

Three failure modes, all predictable.

The filter that hides a real client. Some client will write from a second address, or use an old thread with an old subject, and get filed with the noise. Never build a sort that is the only copy of an email. Keep everything in one inbox, filter the view, and have one person glance at the whole thing once a day. That glance is the safety net, and it takes ten minutes.

The shared inbox nobody owns. Everyone watching a shared inbox means nobody is responsible for the last message. Assign a daily owner: one person, one day, whose job is that the urgent list is empty by five. It rotates. This single change does more than any rule you write.

The automation that silently stops. Rules that break with a login expiry or a change in a supplier's billing address do not announce themselves. The symptom is a quiet inbox, which feels like a good day. Once a week, someone runs the check: how many emails arrived, how many were urgent, were any of them missed. If the urgent count is zero for a week, assume the filter is broken, not that the phone stopped ringing.

A silent inbox is not success. A short, boring list that is empty by the end of the day is.

What good looks like after a month

The inbox still has ninety emails a day in it. That part does not change, and it is not a failure of the project.

What changes is the first ten minutes of the day. The owner opens the phone, sees a list of nine, and knows those nine are the ones that cost money if left. The supplier invoices are already where the bookkeeper expects them, with a date, and nobody has to forward them. The enquiry replies are going out the same morning instead of the same evening, and the clients answering the four questions are answering them in a form the quoting process can use.

Two smaller things arrive with it. The inbox stops being a shared memory, so people stop saying "I thought you had that one". And the owner gets back the hour a day that was going on making ninety small decisions, most of which were the same decision, that could have been made once by a rule.

The first month is not the point where the automation is finished. It is the month where you find out which of your categories were guesses. Expect to delete one and add one. The list should stay short, and it should be a list you would defend to a new starter.

Do this week

Take the inbox you already have and write the one-page list of what actually arrives, by what the sender wants. Unsubscribe or redirect everything that is neither a decision nor a job. Then pick one list of urgent emails and look at only that list for a week, while someone still scans the whole inbox at the end of the day.

That is it. The rules can wait until you know what the categories are, and by then you will know which ones are real.

Common questions

How do I sort a shared business inbox without missing important emails?

Keep every email in one inbox and filter what you look at, rather than moving messages into folders. Then have one person still scan the whole inbox once a day, so a rule that files something wrongly cannot hide it for long.

Should I automate replies to customer enquiries?

Set up a saved reply that asks the same few questions every time and send it yourself for the first month, rather than letting a robot answer. Once the questions are proven to get useful answers, the sending can be automated.

Why do my email rules keep filing things in the wrong place?

Usually because the rule matches on words in the subject, which are written by the sender and often misleading. Rules based on the sender's address and whether the email is a reply in your own threads are far more reliable.

Want this done for you?

I build one small automation at a time for North Shore businesses, usually starting with whatever is costing you the most hours.

Start a project ↗