Why the inbox cannot catch it
An email client has exactly one axis: this thread is in front of me, or it is archived. That is a good model for correspondence and a bad one for support, because support has a second axis the client cannot see.
Consider the sequence. Someone reports a crash. You reply asking for a log. They send it. You archive the thread so your inbox is clear, and go and reproduce the bug. Two days later you ship a fix. At that instant the conversation is in the archive, next to every conversation that genuinely ended, and there is no property of it that distinguishes the two. The customer hears nothing.
They did not receive a broken product. They received silence, and silence is the part they will remember and tell other people about.
The three usual fixes, and how each one fails
Stars and labels
They work right up until the evening you are debugging at speed and archive without starring. The system needs an act of attention precisely when attention is scarcest, so it fails on the busy days, which are the only days it matters.
Snoozing
Snoozing asks you to predict how long the work will take, at the moment you know least about it. Guess short and the thread returns before there is anything to say, so you snooze it again and teach yourself to dismiss it. Guess long and the customer waits for no reason.
A separate task list
Now there are two systems and neither is authoritative. Reconciling them is work, so it does not happen, so the real state lives in your head. Which is where it started.
The common defect: all three depend on remembering, and the problem is forgetting. A fix that requires the thing that is broken is not a fix.
The two-axis model
Ask two questions of every conversation and stop asking any others. Have you done the work, and have you told them. Two yes-or-no answers give four states, and each one asks something different of you.
| State | What it means |
|---|---|
| Needs you | You owe them work, a reply, or both. This is the list you open in the morning. |
| Waiting on them | The ball is in their court. It comes back on its own if they go quiet. |
| Reply owed | You fixed it. They still don't know. This is the one that used to slip. |
| Closed | Handled and told. Only now does the customer leave your list. |
“Reply owed” is the whole point. It is the state your mail client has no name for, and it is where customers are lost. A conversation in it is not finished no matter how finished the work is, and it should look unfinished until you have written back.
Running it, with or without a tool
- One list, not two. Whatever holds this has to be the only place the state lives, or you are back to reconciling.
- Nobody leaves on work alone. Shipping a fix does not close a conversation. Only telling the person does.
- Waiting on them is a real state, not a closed one. If they go quiet it should come back to you, not disappear.
- Say the boring version.“This is fixed in the version that went out this morning” is worth more than a well-written apology sent a week late.
You can run this in a notebook and it will work. The reason to use software is narrow and specific: software can move a conversation into “reply owed” without you remembering to, and can refuse to let it look finished. That is the one job at the exact moment a manual system breaks.
Questions people actually ask
Why do I keep forgetting to reply after I fix something?
Because the two acts are separated by hours or days, and only one of them has a system behind it. You archive the thread to clear your head, do the work, ship it, and the trigger to write back never fires. It is not carelessness, it is a missing step in a process that has no owner.
Do reminders or snoozing fix this?
Partly, and they fail in a specific way: they require you to guess a date at the moment you start the work. Snooze until Friday and a one-hour fix sits for four days; a two-week fix comes back with nothing to say and gets snoozed again. The state you need is not time-based, it is "the work is done and they have not been told".
What is the actual cost of not replying?
A slow reply annoys someone. Silence after you fixed their problem loses them, and it loses them quietly: they do not churn with a complaint, they just stop. You also lose the single highest-value message you can send, which is "you asked for this, it shipped today".
Can I do this without buying software?
Yes. Keep one list with two columns, done and told, and refuse to remove a name until both are ticked. The reason to use software is that software can put a conversation into the "owed a reply" state without you remembering to, which is the exact moment a manual system fails.