A Weekly Inbox Sweep for Unanswered Website Messages: Sort by What Is Waiting, Not by Date

Most shared inboxes are sorted by date, which hides the one fact that matters: whose move is it? A message from three weeks ago may be waiting on the customer and need nothing, while one from yesterday may be waiting on you. This article proposes a weekly sweep that sorts by who is waiting. It is a routine to adapt to your own team.

The inputs you need

Gather the following before you start:

Every thread from the last month that has no clear ending.
A simple status list with three values: waiting on us, waiting on them, finished.
A fixed slot in the week, about fifteen minutes, and one person responsible.
A note field where you can write the next action in a few words.

The sweep, step by step

Open each unresolved thread and read only the last two messages. Ask who spoke last and what they asked for.

If the customer spoke last and asked something, mark waiting on us and write the next action, such as "send revised dates".

If you spoke last and asked something, mark waiting on them and write the date you will check again.

If nobody is asking anything, mark finished and archive it.

If you cannot tell, mark waiting on us. It is cheaper to look twice than to leave a customer unanswered.

Branching decisions for stale items

For waiting on them items older than your check date, choose one: send one polite nudge, or close the thread with a sentence that invites them to write again. Do not send a third nudge. A customer who has not replied after one nudge has probably decided something.

For waiting on us items older than a week, reply first with an honest holding message, then do the work. Do not wait until you can write the perfect reply.

For threads that involve a dispute, a payment question or anything sensitive, do not close them in the sweep. Flag them for a named person.

A hypothetical worked example

Imagine a small bike repair shop with eleven open threads. Four have the customer speaking last: two ask for a pickup time, one asks about a part, one asks for a status. Those go to waiting on us, each with a next action. Five have the shop speaking last, with a quote sent; three are under a week old and left alone with a check date, and two are older, so the owner sends one nudge to each. Two have no question at all, just thanks, so they are archived. The whole sweep takes about fifteen minutes and produces a short list of four replies for the next morning.

Stop conditions

Stop the sweep when the timer ends, even if threads remain. Carry the rest to next week and note how many were left. Stop and escalate if the same customer appears in several waiting on us threads, because that is a pattern to fix rather than a queue to clear. Stop if you find yourself rewriting replies instead of sorting.

Small acceptance checks

At the end of the sweep:

Every open thread carries one of the three statuses.
Every waiting on us thread has a next action and an owner.
Every waiting on them thread has a check date.
No thread was closed while a customer question was still unanswered.
You can state in one sentence how many are waiting on us now.

Track that last number week by week in a simple note. If it keeps growing, the issue is capacity or routing, not the sweep itself, and that is a decision for the team rather than for the inbox.