Why Is Your Inbox Winning?
Email overload is rarely about volume alone. It is about volume without triage, ownership or a process, which is why hiring another person into a broken inbox usually produces a slightly faster broken inbox. Twelve questions to locate the actual problem.
Answer for your busiest inbox, usually a shared one, rather than for your personal mail, which is almost always better managed.
Inbox Overload Scorecard
Answer for your busiest shared inbox, not your personal mail.
A self-assessment to structure an internal review. It is not an audit, and nothing entered is recorded or transmitted.
What the Score Measures
The scorecard measures process rather than effort. A team working extremely hard in a badly structured inbox will score poorly, and that is the finding rather than a criticism.
Triage is the highest-leverage gap
If every message reaches every person and each decides individually what it is, you are paying for classification many times over. Triage is the most automatable part of email and the part most teams have never structured at all.
Ownership prevents both duplication and silence
Shared inboxes without assignment produce two failures at once: several people answering the same message, and messages nobody answers because everyone assumed someone else had. Clear ownership eliminates both.
Measurement changes behaviour on its own
Teams that do not measure response time are consistently slower than they believe. Simply starting to measure, before changing anything else, reliably improves the number, because attention follows measurement.
The Four Areas Assessed
Twelve questions covering the places email processes most commonly fail in Australian small and medium businesses.
Triage and classification
Whether messages are sorted before they reach people, or whether everyone sorts everything individually.
Ownership and routing
Whether each message has a clear owner, or whether shared inboxes rely on someone volunteering.
Speed and reliability
Whether response times are known, consistent and covered across evenings, weekends and leave.
Repetition and follow-up
Whether repeated questions are handled systematically, and whether anything falls through the cracks.
The Four Patterns
Nearly every team scoring below seventy per cent matches one of these. Identifying yours tells you what to change first.
The everybody-reads-everything inbox
A shared inbox that several people monitor, where each reads every message to determine whether it concerns them. The reading cost multiplies by the number of watchers, and nobody feels able to stop watching in case something is missed.
- Symptom: several people can describe the same message in detail
- Symptom: nobody feels able to ignore the shared inbox
- Fix: automatic classification and assignment to a named owner
- Wrong fix: adding another person to watch it as well
The no-owner inbox
Messages arrive and sit because handling them is nobody’s explicit job. Urgent items get answered because someone notices; routine ones age quietly. The team is genuinely busy and enquiries are still being lost.
- Symptom: customers following up because nobody replied
- Symptom: messages answered twice by different people
- Fix: explicit assignment on arrival, with escalation on ageing
- Wrong fix: a rota that collapses the first busy week
The same-twenty-questions inbox
A large share of volume is the same questions repeatedly, each answered from scratch in slightly different words by whoever picks it up. The work is real but produces no accumulating value, and quality varies with who happened to answer.
- Symptom: you could predict most of tomorrow’s messages
- Symptom: answer quality depends entirely on who replies
- Fix: automated drafting from approved answers, human approval to send
- Wrong fix: a template library nobody remembers to open
The black-hole inbox
Messages are received and dealt with, but there is no record of what was promised or whether it happened. Commitments made by email are invisible to everyone except the person who made them, until a customer rings to ask.
- Symptom: nobody can say what was promised to a customer last week
- Symptom: commitments discovered only when someone chases
- Fix: extract commitments and deadlines into a tracked system
- Wrong fix: asking people to be more careful, which never scales
Next Steps
Email Time Cost Calculator
Put an annual dollar figure on the pattern the scorecard identified.
Calculate the cost →Email Response Time Calculator
Model what replying faster would be worth in additional won work.
Model the revenue →Email Automation Setup Checklist
The rollout plan for triage, routing and drafting.
Open the checklist →Frequently Asked Questions
No: shared inboxes solve a real problem, which is ensuring customer contact does not disappear into one person’s mailbox when they are on leave. What causes trouble is a shared inbox without assignment, where the sharing is of visibility rather than of clearly allocated responsibility. A shared inbox where each message is assigned to a named owner on arrival, with escalation when it ages past a threshold, works well. One where everybody watches and anybody might respond produces both duplicated effort and dropped messages.
Usually not, and this is worth knowing before spending the money. Adding a person to an inbox without triage or ownership adds another set of eyes reading the same messages and making the same individual classification decisions. Response time improves somewhat because there is more capacity, and the structural problems remain. Fix the process first (triage, assignment, escalation) and you frequently find the existing team handles the volume comfortably. If volume genuinely exceeds capacity after that, hire with a much clearer idea of what the role does.
It depends on what the inbox is for. A sales or enquiry inbox in a competitive category should target under an hour during business hours, because enquirers are actively comparing providers. A support inbox can usually work to same business day for routine issues, with a faster path for anything urgent. An accounts or administrative inbox can typically operate to one to two business days. The essential thing is to set an explicit target per inbox, measure against it, and cover the out-of-hours gap with at least an acknowledgement.
Triage and classification are highly automatable, deciding what a message is, who it belongs to and how urgent it is follows rules well. Routing and assignment likewise. Drafting standard responses works well with a human approving before sending. What should not be automated is anything involving judgement, negotiation, complaint handling or a difficult conversation. For most business inboxes, that puts the genuinely automatable share somewhere between a third and a half, and pushing much beyond that tends to produce responses that customers notice as wrong.
Dedicated shared inbox and helpdesk tools handle assignment, internal notes, status tracking and reporting far better than a mail client with a shared mailbox, and for any team of more than two or three people they are usually worth the cost. That said, a well-structured process in a standard mail client beats a poorly configured tool. If you are scoring badly, fix the process first (decide who owns what, set targets, agree escalation) because moving a broken process into new software reproduces the same problems with a better interface.
No. Everything runs in your browser, nothing is transmitted, and there is no email gate on the result. Feel free to screenshot it for a team discussion. The questions ask only about process, so no email content or business detail is requested or collected at any point.
Know Which Pattern You Have?
Tell us which of the four matches your inbox and we will tell you the cheapest way out of it, which is sometimes a process change rather than a product.