Waiting on someone else: tracking pending threads in a shared inbox
Some conversations stall because you wait on a customer, a teammate or a vendor. A simple way to mark them, check them on a schedule and stop them going silent.
On this page(9 sections)
Most shared inboxes handle new mail well and handle waiting badly. A customer sends a question, you reply asking for a screenshot, and the thread sits there. Nobody is working on it, nobody has closed it, and three weeks later the customer writes again, annoyed.
The problem is not the message you sent. It is that "waiting" has no home. The thread looks the same as one that needs action today, so it either clutters the list or gets buried. This post describes a small system for conversations that are paused on someone else, and how a team of two to ten people can keep it honest.
Three kinds of waiting
Not all waiting is equal, and mixing them is what makes it messy.
| Waiting on | Example | Who can move it |
|---|---|---|
| The customer | You asked for an order number or a log file | Only the customer, but you can nudge |
| A teammate | Billing needs to approve a refund | A named person on your team |
| An outside party | A vendor, a bank or a registrar | Nobody on your side, so you need a check date |
Each one needs a different follow-up. The first needs a reminder to the customer. The second needs a message to a colleague. The third needs a date on which you look again, and a plan for what to do if nothing has changed.
Give waiting its own marker
Pick one way to mark a thread as paused and use it every time. In many teams that is a label such as "waiting-customer" or "waiting-internal". If you want ideas on keeping label sets small, see labels versus folders in a team email taxonomy.
A few rules keep the marker useful:
- One marker per thread. A thread is either waiting or it is not. Do not stack three labels on it.
- The marker means "I am not the blocker". If the next move is yours, remove the label and do it.
- Every waiting thread has an owner. Someone's name is on it, even if the thread is paused. An unowned waiting thread is the one that goes silent. The rules in shared inbox ownership rules apply here too.
- Write the reason in a note. One line is enough: "Asked for the invoice PDF on Oct 14. Check again Oct 17." In Koltrix you can add an internal note and mention a teammate, as described in teams in Koltrix: assign conversations, notes and mentions. The customer never sees it.
Set a check date every time
A marker alone does not bring a thread back. A date does. When you pause a conversation, decide when you will look at it again. As a starting point:
- Waiting on a customer for information: check after 2 business days, then again after 5.
- Waiting on a teammate: check the next business day.
- Waiting on an outside party: check on the date they promised, or after one week if they gave none.
Write the date in the note. Then use a calendar reminder, a recurring calendar slot or your weekly review to look at everything with a waiting marker. The weekly habit in the weekly team inbox review ritual is a good place to put it: open the waiting label, sort by oldest, and deal with each thread in turn.
Nudging a customer without nagging
When the check date arrives and the customer has not replied, send a short follow-up. Keep it easy to answer:
Hi Maya, I wanted to check back on the invoice PDF. If you send it, I can finish the correction today. If it is easier, tell me the invoice number and I will look it up.
Three things make this work. It restates what you need in one sentence. It offers a smaller alternative. It does not blame. A second nudge a few days later can be even shorter.
After the second nudge, decide what happens next and say so. For a support request a common last message is: "I will close this for now. Reply any time and it will reopen." Then close it. What happens when that reply arrives is covered in repeat contacts and reopened conversations by email.
Chasing a teammate
Internal waiting is the easiest to fix and the easiest to ignore. A teammate saw your message in the middle of something else and forgot it.
- Mention the person in the note rather than sending a separate chat message that nobody can find later.
- Say what you need and by when: "Can you approve this refund today? The customer wrote twice."
- If the person is away, reassign the thread to someone who can act. Do not leave it parked under an out-of-office name.
If you share an inbox across time zones, a waiting thread is also a handoff. The notes you write are what the next person reads first. See inbox handoffs across time zones for how to keep those notes useful.
Measuring it without gaming it
Waiting time matters when you report response times. If a thread sits for four days because the customer was away, counting that against your team is unfair. If it sits for four days because you forgot, it is your fault. Good habits make the difference visible.
A few simple measures work for a small team:
- How many threads are in the waiting state right now. A number that keeps growing means check dates are being skipped.
- Age of the oldest waiting thread. This one catches the stragglers.
- How many waiting threads passed their check date. The target is zero at the end of each week.
The distinction between first response and the full resolution time is covered in first response versus resolution time, and targets for small teams are in email SLA targets for small support teams. If you pause the clock while waiting on a customer, write that rule down so everyone counts it the same way.
What to do with very old waiting threads
Every inbox collects a few threads that have been waiting for months. Clear them in one sitting:
- Sort the waiting label by oldest first.
- For each, ask: "Would the sender still care?" If the answer is probably not, send one final message and close it.
- If it still matters, move it out of waiting and into active work with a new owner.
- Remove labels that no longer apply.
Do this once a quarter and the backlog never gets large.
A short checklist
- Choose one marker for waiting, and one per kind if you need to tell them apart.
- Assign an owner to every paused thread.
- Write a one-line note with the reason and the check date.
- Review everything marked as waiting at least once a week.
- Nudge twice, then close with a clear message.
- Reassign when the owner is away.
- Count overdue check dates and keep them at zero.
Key takeaways
A paused conversation is not a finished conversation. Give it a marker, an owner and a date, and it comes back at the right time instead of when the customer gets frustrated. The system is light: a label, a one-line note and a weekly look. That is enough to keep a shared inbox from filling up with threads that nobody is quite responsible for.
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.
