KoltrixHow to audit a messy shared inbox in one afternoon
An hour-by-hour runbook for cleaning up a neglected shared inbox: take stock, clear the noise, rescue waiting threads, fix labels, and add three useful rules.
On this page(9 sections)
- Before you start
- Hour 1: Take a snapshot (30 minutes) and clear the noise (30 minutes)
- Snapshot
- Clear the noise
- Hour 2: Rescue the threads waiting on you
- Hour 3: Fix the labels
- Hour 4: Write three rules and set a habit
- Three rules
- A maintenance habit
- What to do if you run out of time
- Write the after-snapshot
- Runbook checklist
- Bottom line
Shared inboxes don't become messy in a day. They drift: a few unread notifications, a couple of threads someone meant to answer, a label nobody uses. Then one day support@ shows thousands of unread messages and nobody wants to open it.
You don't need a week-long project to fix it. With a focused afternoon (about four hours) you can get a shared inbox back to a state where the team trusts it again. Here's the runbook, hour by hour.
Before you start
Block the time on your calendar and tell the team. You'll be archiving and relabeling in bulk, so people should know not to be alarmed. Two quick prerequisites:
- Confirm archiving is reversible in your email tool, meaning archived mail is still searchable. You'll archive a lot; you should delete almost nothing.
- Pick one person to run the audit. Others can help in hour three, but one person making the bulk decisions keeps them consistent.
Hour 1: Take a snapshot (30 minutes) and clear the noise (30 minutes)
Snapshot
Write down the starting numbers so you can see progress and spot anything unusual:
Shared inbox audit – [date]
Total threads in inbox: ____
Unread: ____
Oldest unread: ____
Labels in use: ____
Top 10 senders by volume (last 90 days):
1. ____ 2. ____ ...
The top-senders list is the most useful part. In most messy inboxes, a handful of automated senders account for a large share of the volume.
Clear the noise
Go down the top-senders list and handle each automated sender in bulk:
- Tool notifications (CI, monitoring, project tools): select all, archive. Note the sender for a rule in hour four.
- Newsletters and marketing: archive, then unsubscribe from anything nobody reads.
- Receipts and invoices: archive, but label them first if finance needs them later.
- Calendar notifications: archive.
Do not open these one by one. Search by sender, select everything, act. This step alone often clears most of the volume.
Hour 2: Rescue the threads waiting on you
Now the inbox is mostly human mail. This is the important hour, because buried in here are customers and partners who never got an answer.
- Filter for threads where the last message is from someone outside your team. These are threads where the other person spoke last, so you may owe them a reply.
- Sort oldest first. Skim each one. Decide in under a minute:
- Still needs a reply? Label it as waiting on us and add it to a list.
- Resolved elsewhere (chat, phone, a later thread)? Archive.
- Too old to matter (a meeting request from months ago)? Archive.
- Count the "still needs a reply" list. If it's short, answer them today. If it's long, split them among the team for tomorrow.
For very old unanswered threads that still matter, a short honest note works: "This got missed on our side, sorry. Is this still something you need help with?" Many people appreciate the follow-up even late.
Hour 3: Fix the labels
Open your label list. In a messy inbox, you'll typically find duplicates, abandoned labels and labels named after people who left.
For each label, decide one of three things:
| Decision | When | Action |
|---|---|---|
| Keep | Used recently and helps someone find something | Leave it |
| Merge | Duplicate or near-duplicate of another label | Relabel threads, delete the duplicate |
| Delete | Unused in months, or purpose unclear | Delete (threads remain, just untagged) |
Aim to finish with a short list that everyone understands. If you can, organize what remains with prefixes, for example topic/billing and status/waiting-on-us, so related labels sort together.
This is a good hour to bring in a teammate. Ask them: "Which of these labels do you actually use?" Their answers are faster than any analysis.
Hour 4: Write three rules and set a habit
Three rules
Don't try to automate everything. Write three rules that prevent the biggest sources of mess from returning. Usually:
- The highest-volume notification sender goes straight out of the main view (archived or labeled).
- Receipts and invoices get a finance label automatically.
- One critical sender (payment failures, security alerts) always stays in the main view, so it's never buried.
Test each rule against the last week of mail to check it does what you expect before turning it on.
A maintenance habit
Messy inboxes come back without a habit. Pick one, put it on the calendar, and name who owns it:
- A daily triage pass by whoever is on rota
- A 15-minute weekly review of anything older than a few days
- A quarterly label prune
What to do if you run out of time
Four hours is enough for most inboxes, but a truly neglected one may not finish. If you have to stop early, stop in this order of priority:
- Never skip hour two. Threads waiting on you are the only part of the audit with real customer impact. If the afternoon goes sideways, finish this first and leave labels for another day.
- Bulk noise can wait a day if needed; it's annoying, not harmful.
- Labels and rules can be a follow-up session. Put a 90-minute block on the calendar for next week before you leave, so it actually happens.
Also resist the urge to perfect things. An audit is about getting back to a trustworthy state, not designing the ideal system. A slightly imperfect label list that everyone uses beats a perfect one nobody understands.
Write the after-snapshot
Close the afternoon by repeating the snapshot:
After audit:
Total threads in inbox: ____
Unread: ____
Threads waiting on us: ____ (assigned to: ____)
Labels: ____
Rules added: 3
Maintenance habit: ____, owner: ____
Share both snapshots with the team. It's satisfying, and it makes the case for keeping the habit.
Runbook checklist
- Time blocked and team informed
- Starting snapshot recorded, including top senders
- Automated senders bulk-archived, unsubscribes done
- Threads waiting on us identified and owned
- Labels kept, merged or deleted
- Three rules written and tested
- Maintenance habit scheduled with an owner
- After-snapshot shared
Bottom line
Clear the automated noise first, because that's most of the volume. Spend real attention on threads where someone outside the team spoke last. Then shrink the label list, add three targeted rules, and schedule a habit so you never need another audit afternoon.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
