KoltrixThe weekly inbox review: a 30-minute ritual for small teams
A minute-by-minute agenda for a 30-minute weekly team inbox review: stale threads, waiting-on-customer, recurring questions, rule tweaks and one change.
On this page(6 sections)
Daily triage keeps a shared inbox moving. It doesn't tell you whether the inbox is healthy. Threads quietly age, the same question arrives for the fifth time, a rule starts misfiring, and nobody notices because everyone is busy handling today.
A short weekly review is where you step back. Thirty minutes, same time every week, with a fixed agenda. This runbook gives you that agenda minute by minute, plus a notes template so each week builds on the last.
Who, when and where
Who: Everyone who regularly handles the shared inbox. For a team of three to eight, that's usually everyone. If the team is larger, include whoever was on triage that week plus one person from each function that receives routed threads (engineering, finance, sales).
When: Late in the week works well. Thursday afternoon gives you time to act on anything you find before the weekend, and the week's patterns are visible. Avoid Monday mornings; the inbox is at its noisiest and everyone is catching up.
Where: A call or a room with the inbox on a shared screen. The facilitator drives; others call out what they see.
Facilitator: Rotate it weekly. The facilitator keeps time, takes notes and makes sure the meeting ends with one decision.
The agenda
Minutes 0–2: Open and numbers
The facilitator reads out three numbers from the inbox, without commentary:
- Threads currently waiting on us
- Threads waiting on customers
- The oldest thread waiting on us (how many days)
Write them in the notes. Over a few weeks, the trend matters more than any single week's numbers.
Minutes 2–10: Stale threads
Filter for threads waiting on us that are older than a few working days. Go through each one briefly:
- Who owns it? If nobody, assign an owner now.
- What's blocking it? Waiting on engineering, a decision, information?
- What's the next step and when? Agree on it out loud.
Keep each thread to under a minute. This isn't the place to solve the problem, just to unstick it. If a thread needs a real discussion, schedule it separately with the right people.
This is the most important part of the meeting. A thread that gets talked about in the weekly review rarely stays stuck for another week.
Minutes 10–14: Waiting on customers
Look at threads where you asked the customer something and haven't heard back.
- Older than a week? Decide: send a gentle follow-up, or close the thread with a friendly note that they can reply any time.
- Pattern? If customers often go quiet after the same kind of question, maybe the question is confusing or asking for too much.
Closing stale waiting threads keeps the inbox honest. A thread that's been waiting on a customer for a month isn't really open.
Minutes 14–20: Recurring questions
Ask the room: "What did we answer more than twice this week?"
Typical findings:
- A how-to question that the docs don't cover, or cover badly
- Confusion caused by a recent product change
- A billing question that follows every renewal email
- Bug reports that are all the same underlying issue
For each recurring question, pick one fix:
| Fix | When it fits |
|---|---|
| Write or update a docs article | The answer is stable and self-serve is possible |
| Create a reply snippet | The answer needs a human touch but is mostly the same |
| Raise it with product | The question exists because something is confusing |
| Change an automated email | A message you send is causing the question |
Write the fix and its owner in the notes.
Minutes 20–25: Rules and sorting
Quick check on automation:
- Misfiled mail this week? Anyone notice customer email landing in the wrong place, or noise leaking into the main view?
- New senders? A new tool or newsletter often needs a rule.
- Rules nobody understands? Flag them for the quarterly prune.
Make small rule changes in the meeting if they're obvious. Note bigger ones for later.
Minutes 25–30: One change, then close
End by agreeing on one process change for the coming week. Just one. Examples:
- "We'll add follow-up dates to every waiting-on-customer thread."
- "Billing questions go to Dee directly, not through triage."
- "We'll try a midday check on Mondays, since that's when the backlog builds."
One change per week is sustainable and easy to evaluate next week. Five changes per week means none of them stick.
Read back the action items and owners, then end on time.
The notes template
Keep a running document with one section per week, newest on top:
Weekly inbox review – [date]
Facilitator: [name]
Numbers
- Waiting on us: __ Waiting on customer: __ Oldest: __ days
Stale threads unstuck
- [thread] → owner: __, next step: __, by: __
Closed (waiting on customer too long)
- [thread], [thread]
Recurring questions
- [question] → fix: __, owner: __
Rule changes
- [change made / to do]
This week's one change
- __
Last week's change: did it work? __
The last line is easy to forget and the most valuable. It turns the review into a feedback loop instead of a status meeting.
Keeping the ritual alive
Weekly meetings die quietly. A few things keep this one going:
- Never skip twice in a row. If the usual slot doesn't work, move it rather than cancel it.
- Keep it at 30 minutes. Running over makes people dread it. If there's more to discuss, book a follow-up.
- Don't let it become a complaint session. The facilitator's job is to turn every frustration into a fix with an owner, or move on.
- Celebrate the boring weeks. A week where the numbers are low and nothing is stuck is the goal, not a waste of a meeting. Those reviews can end in ten minutes.
Runbook checklist
- Recurring 30-minute slot booked late in the week
- Facilitator rotation set
- Notes document created with the template
- Filters saved for stale threads and waiting-on-customer threads
- First review held, with one agreed change
- Second review starts by checking last week's change
Key takeaways
- Daily triage handles today; a weekly review keeps the inbox healthy over time.
- Spend most of the time unsticking stale threads and turning recurring questions into fixes.
- Close threads that have waited on customers too long.
- End every review with exactly one process change, and check it the following week.
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.
