The invoice question went out on a Monday. It was the last line of a message that was mostly about the schedule. It’s the twenty-fourth now. The schedule went over, it got thanked for, and that thread sits in your mail marked read with your own words last in it. Nobody has done anything wrong. There’s a question in there that stopped being live somewhere in the past three weeks, and you’d have a hard time saying which week it was.
The chapter before this one ended on the thing you produce every time you accept an ask: a second loop, pointing the other way, where the next move belongs to somebody else. This chapter is about that loop. It moves while you wait.
- Silence is one word covering several different situations, and you hold more evidence about which one you have than you use.
- Their intention to answer holds. What climbs is the cost of answering, and people do the cheap things.
- The message that brings a thread back is a shorter one, doing different work from the first.
- A loop you can’t get answered can still be ended, by you, on purpose, in one paragraph.
What gets more expensive while nothing happens
Threads are usually described as going cold, which makes it sound like a temperature. It’s closer to a price.
The cost of answering rises every week. On the Tuesday after you sent it, answering meant typing a date. Today it means opening a long thread. Then scrolling past the schedule discussion, working out which invoice, checking whether the extra site visit was ever agreed. Then typing the date. The question is exactly the same size. The job wrapped around it is four times bigger, and it grows again with every message that lands on top of it and every week their memory of the matter thins. Nobody decides to abandon your thread. They open it, find a five-minute job where there used to be a fifteen-second one, and close it. Each time they do that, the thread gets a little heavier to pick up.
The standing of the question falls. Send again on the Thursday and you just ask. Send five weeks later and the message starts explaining itself, and the explanation is an admission. “Sorry to keep coming back to this” grades your own ask on the way in. Whatever you meant by it, what the reader takes from it is that the thing you’re asking about was optional. What usually comes back is the worst available answer: a friendly apology, and still no date.
The question can stop being answerable. This is the real death, and it’s a different thing from being ignored. The invoice was for a scope that has since been revised. The approval was for a version the client has already seen two rounds past. The decision got made in a meeting you weren’t in and nobody thought to tell you, because from their side it was settled. Send the original question now and you’re asking somebody to travel backward to a week that’s over. The honest move at that point is to withdraw the old question and ask a new one, out loud, so that both of you know which one is live.
There’s a quieter fourth thing, which is that the reader changes. Controllers move on. An assistant takes over a mailbox. The office manager who knew what the March schedule was leaves in the fall. The thread survives that. Its reader doesn’t, and your mail stays quiet about it.
So a thread dies on the day answering it stops being a small thing to do. Almost everything worth doing about a quiet thread is aimed at that one number.
The evidence you already hold about the silence
You know more about this thread than you think. Before you write anything, spend a minute working out which silence this is. The right message differs by more than tone, and you usually have enough to tell.
Have they written to you at all since? This is the strongest single signal available and the one people most reliably skip. Say your contact answered you on Thursday about the payroll question and left the invoice question sitting. Then the silence is about that question: it’s harder, or it needs somebody else, or they’d rather not say. If they’ve gone quiet on everything you’ve sent for two weeks, the silence is about their month. The useful move there is smaller, later and gentler than a chase.
Was there anything small to do? “Any thoughts on when to issue it?” asks somebody to compose. “The 30th or the 5th?” asks for one word. A question that requires writing gets treated like writing, and writing is what people postpone.
Was the ask visible at all? Asks arrive inside paragraphs about something else, which is where this series started, and the last line of a long message about the schedule is the single most missable place to put one. If that’s what happened, you’re sending a first message that happens to be second. Write it that way: the question on its own, no reference to the gap, no apology.
Can the person you asked actually answer it? Sign-off, spend above a threshold, anything a partner has to see. Their silence is their own internal wait, and it sits there whatever you write. As a signal it’s a good one, because it tells you the delay is structural rather than about you, and it points at a different move: find out who decides. That case and three others where a better second email is the wrong instrument are set out in the follow-up email that gets answered.
And the dull check, once. Right address, no bounce, no automatic reply you cleared at 7 in the morning without reading. It’s rarely the answer. It costs ten seconds, and it’s embarrassing to find on the fourth attempt.
How long quiet has to run before it means anything at all is a separate question with real numbers behind it. What reply times actually look like. Why the mail that asks for something is answered slowest of all. The two different dates you form in your head the moment you press send. Unanswered emails, and the threads that come back works through those. Everything below assumes you’ve already decided this thread is quiet rather than early.
Where to put a message this old
Reply in the thread, or start something new. It’s normally an easy call, and the normal answer is to reply in the thread. Your original travels underneath it, so nothing has to be retyped and nothing has to be hunted for.
An old thread is one of the places that answer stops holding, and it’s worth knowing why rather than taking it on trust, because there’s a mechanism under it. Mail apps assemble chains by subject line, an arrangement taken apart in how to catch up on a long email chain. Google’s help page for Gmail is specific about where the assembling stops: a conversation “breaks off into a new conversation when the subject line changes, or the conversation gets to more than 100 emails” (checked September 6, 2026).
So the subject line decides whether your message continues the old conversation or begins a new one, whether or not you meant to decide anything.
Keep it, and your words arrive as the newest line of a conversation the reader has already opened, considered and finished with. It’ll be unread and near the top of their inbox, so they’ll see it. What surrounds it is the trouble. Your question arrives in the context where it already failed to get answered, and on a long chain, opening it means facing the whole thing again.
Change it, and in Gmail you’ve left that conversation. The history stops traveling underneath. That’s a real loss, and occasionally it’s the entire point, since what lands is a message about one thing with nothing above it. If you go that way, carry the history yourself: the old thread forwarded below your new words rather than assumed.
The line to draw sits roughly where you stopped being able to describe the thread in a sentence. Up to there, reply underneath. Past it, send a new message about one thing, with a subject line that names the thing rather than naming what you’re doing.
Paying down the cost of answering
The first message was written while the matter was in both your heads. The second one is written into a gap, and the gap is the whole design problem. Everything the reader has lost since is work you’re about to ask them to do again.
How a follow-up is built, line by line and with examples, belongs to the follow-up email that gets answered. What’s worth adding at this end is what the age of the thread changes. A message sent on the Thursday and the same message sent five weeks later are two different messages.
The older it is, the more of their reading you do for them. On day three, “the invoice question” is understood. On day twenty-four you write the question out: whether to issue the March invoice at the original $8,400 or at the revised scope, and that you can do either. Fifteen seconds of yours takes four minutes off them, and four minutes is what has been stopping this.
The older it is, the fewer things it can carry. If your original message asked three things and one of them went unanswered, bring back the one. A message repeating all three reads as a summary of the project, and summaries get filed rather than answered.
The older it is, the more tempting the apology. “Sorry to keep coming back to this” grades your own ask on the way in. Warm is fine, and with a client it’s usually right. Apologetic is a discount you’re applying to your own work before anybody has asked for one.
One sentence in a revival deserves a caution, because it’s the most useful one available and the easiest to over-read. Saying what you’ll do if nothing comes back gives you a date on which this loop closes, reply or no reply. A default you announce organizes your side of it, and only your side. The place that question has actually been argued is contract law, where it arrives as whether somebody has agreed to something by saying nothing. The case is Southern Cal. Acoustics Co. v. C. V. Holder, Inc., decided by the Supreme Court of California on August 5, 1969. The court put it in a line: “Silence in the face of an offer is not an acceptance, unless there is a relationship between the parties or a previous course of dealing pursuant to which silence would be understood as acceptance.” That’s California, and a case about a construction bid rather than a rule about your mail, so take the shape of it rather than the citation. If what you needed was their agreement, a Friday you set for yourself hasn’t produced it, however carefully you worded the sentence. If what you needed was permission to stop waiting, it has. Which of the two you were short of decides whether the thing you do on Friday is safe to do.
The point where more messages stop being the answer
There’s one corner of accounting where a missing reply is a hole in the work rather than an irritation, and because of that somebody had to write down what to do about it. An auditor sends a confirmation request to a bank or a customer, and nothing comes back. The standard sets out the next step.
The Public Company Accounting Oversight Board’s confirmation standard, AS 2310, effective for audits of financial statements for fiscal years ending on or after June 15, 2025, sets out two steps in order. Paragraph .21: “If the auditor does not receive a confirmation response to a positive confirmation request, the auditor should follow up with the confirming party.” Then paragraph .23: “In the case of a nonresponse or an incomplete response, the auditor should perform alternative procedures for the selected item in accordance with Appendix C.”
That governs audits performed under PCAOB standards, which is public companies and registered broker-dealers, and that’s the whole of its reach. Most readers of this series do no audit work at all, and nobody is going to ask you for your alternative procedures on an unanswered invoice question. What’s worth borrowing is the sequence, because the profession arrived at it out of necessity. You ask again, once. When that fails, you stop asking and get the fact another way.
For ordinary work the other ways are all unglamorous.
The telephone. Three weeks of silence is very often ninety seconds of somebody’s afternoon. People reach for a fourth email instead because an email can’t be declined in front of them. Call somebody who has left two of yours unanswered.
A different person. The bookkeeper who answers everything, the assistant who keeps the partner’s mail, whoever it turns out actually decides.
The thing itself. A surprising share of what you’re waiting on can be had without the person: the portal, the bank feed, the last statement, the signed engagement letter, the prior year’s file. Getting the fact yourself is often faster than the third message asking for it, and always faster than the fourth.
Proceeding without it, and saying so. This is a legitimate ending. It belongs on the list rather than at the bottom of it.
Underneath all of them sits a counting rule. A second message that differs from the first is worth sending. A third that repeats the second is worth very little. A fourth is worth less than nothing, because what it teaches the reader is that your messages can be ignored at no cost, and that lesson travels well past the thread you taught it on.
Ending it yourself, on purpose
The chapter before this one made the point that every way a loop can end is something somebody does. Accepting, declining, delivering, agreeing that it was delivered, withdrawing. Time passing is on nobody’s list. That cuts in a direction almost nobody uses. When the other person leaves it sitting, you can still end it, because withdrawing is an act and it’s entirely yours to make.
The closing note is four sentences at most.
What you asked, in one line. That you’re taking it off your list. What that means in practice, which is the part that makes it a real ending rather than a sulk: the invoice goes out at the original figure, the section stays as drafted, the scope question gets picked up at the review in October. And what would reopen it, offered properly. “Say the word whenever and I will pick it straight back up” only works if it’s true, and it costs you nothing to make it true.
Two things about that note are worth knowing before you send your first one.
It’s frequently the message that gets answered. Send it as an ending and mean it as one, rather than as a clever piece of pressure. It’s simply the only message in the sequence that costs the reader something to ignore, since ignoring it now has a visible consequence with their name near it. If the reply comes, take the reply and drop the closing.
And closing a loop leaves the relationship exactly where it was. Everything in the note can be warm. A client who reads it as a rebuke has read it wrong, usually because it was written in the mood of the fourth attempt rather than in the mood of the first.
Write down that you closed it, and when. Six months from now, the question in the room is whether you ever asked, rather than whether they answered. A sent message with a dated closing note under it settles that in about four seconds.
The exception is worth naming, because it’s the one place this move does damage. Sometimes the answer is required rather than wanted: a signature that has to exist, a confirmation that has to be on file, a decision somebody is entitled to make and you are not. That loop gets escalated rather than withdrawn. Escalating is a different message to a different person with its own date on it, and quietly taking it off your list is the worst available option.
How Point holds the half you are waiting on
You’re already carrying this half in your head, and that’s the part Point takes. Point is the mail client rather than something attached to one, so both halves of a quiet thread live in the same place: the message you sent, and the reply you’re waiting on.
Say on the thread, in ordinary words, that the next move belongs to them. The wait becomes a dated item on the same list as the work you owe, with the conversation a step away from it. What you were carrying around as a fact about a client turns into a row you can look at, and the register keeps itself. Come the day, a thread with nothing new in it rises back to the top of your feed, and you’re prompted to write the second message. Writing it is still your job, which after everything above is where it belongs.
If the reply lands first, the thread is live again, and nothing is raised at all.
Some of what you’re waiting for is an event rather than a reply. For those you can ask, in plain words, to be told the moment it happens: the statement arrives, the surveyor comes back, the portal shows the return accepted. A request like that sits on the list as a watch. It speaks once, when it fires, instead of every time you wonder. Writing one is setting your first watch in plain words.
You set how far Point goes without you, separately for each kind of action. The range runs from suggesting and stopping there, through preparing something and holding it for you to look at, to getting on with it. Every kind begins in the middle, so raising one is something you go and do rather than a setting you inherited. Point’s work leaves a record you can read straight through, in plain sentences. Reversing an action starts from the entry that logged it, with the obvious limit that mail already delivered to another company’s server can’t be pulled back. What else Point does with your mail sits on the benefits page.
The loop that never became a message at all
Everything in this chapter assumes two things about the quiet thread. That it exists as an object you can open. And that the person at the other end is somebody you write to.
Both hold for a client. For the largest category of things you’re actually waiting on in a working week, neither does.
You asked Marcus on Tuesday to get the Hallett file over to the surveyor. He said yes, in the kitchen, between two other things, and he meant it. There’s no thread, no subject line to rewrite, nothing to reply underneath, no closing note to send, because there was never an opening one. What you have is a memory of a kitchen, and a suspicion that’s been growing since Thursday.
He’s eight feet away and has been all morning. You’ve decided four times not to ask, on the grounds that it would look like checking up on him, and the fourth time took longer than the first. That’s the next thing this series has to fix, and not one of the tools in this chapter goes anywhere near it.