Follow-ups that get answered

Somewhere in your sent folder is a message that says "Just bumping this!" It did not get a reply. It was never going to, because it asks the reader to do all the work: scroll back through the thread, reconstruct what the ask was, figure out whether it still matters, decide on a next step. Only after all that can they start typing. "Just bumping this" is the worst sentence in professional writing. It sounds polite while quietly handing the entire job to the other person.

Here is the model that fixed follow-ups for me. An ignored message is almost never a rejected message. It is an expensive one. Nobody answers email in the order it arrived, or even in the order it matters. They answer whatever costs the least to answer, in the ninety seconds between meetings, on a phone, with one thumb. A message that needs ten minutes of archaeology loses to a message that needs one word, every single time.

I see this from the receiving end too, in my own inbox. I know exactly which messages I answer first: the ones I can answer in one line. Not the most important ones. The cheapest ones. I am not proud of it, but I have stopped pretending I am the exception.

There is a corollary that took me longer to accept: the silence is not personal. If you read it as rudeness, you get resentful, and the resentment leaks into your next follow-up, which makes it colder and vaguer, which raises the price of replying again. The thread spirals down while both people privately blame each other. Treating silence as a pricing problem instead of a character flaw breaks that loop.

So the entire craft of the follow-up is one move: lower the price of replying until it drops under the reader's threshold. Every technique below is that move wearing a different shirt.

Carry the context instead of pointing at it

"Circling back on this" points at context that lives somewhere below, in a quoted thread the reader has to excavate. Restate the context in one line instead. You do the archaeology so they don't have to.

Before: "Hi Priya, circling back on the below. Any thoughts?"

After: "Hi Priya, two weeks ago you asked for a revised quote for the March workshop. It's attached. Does the new number fit your budget?"

The second version is longer to write and cheaper to answer, and that is the trade to make every time. You spend thirty extra seconds so she can reply in five. Never make someone scroll to understand you. Scrolling is where replies die.

Make it answerable in one word

One ask per message. I mean that literally. Every extra ask raises the price, because most people will not reply until they can address everything, and "until I can address everything" is a euphemism for never.

Before: "Following up on the contract, and also wondering where we landed on the timeline, and whether Dana should join the kickoff?"

After: "Can you sign the contract by Friday? Timeline and kickoff can wait until it's signed."

Then shape that one ask so it can be answered with a yes, a no, or a choice between two named options. "What are your thoughts?" is an essay assignment. Nobody has room in their day for essay assignments from you.

Before: "What are your thoughts on the proposal?"

After: "Is the proposal approved as written, or should I book fifteen minutes to walk through changes?"

The same instinct gives you the smallest-next-step move. If what you need is a meeting, "let me know when you're free" is scheduling homework. Do the homework yourself.

Before: "Let me know when you're free to discuss."

After: "I put a placeholder on your calendar for Tuesday at 2. Move it anywhere, or reply 'call me' and I'll call you for five minutes."

Some people find the placeholder pushy. I find it kind. A tentative block they can drag around beats an open negotiation they have to run in their head. If they hate it, they can decline it in one click, and a one-click decline is still an answer, which is more than the old thread ever produced.

Chat has its own version of the expensive message. It is the naked "hey" with nothing after it, or the ask smeared across six separate messages so the notification preview says nothing useful. In chat, one complete self-contained message wins: "Can you approve invoice 4821 in the finance channel? It unblocks the vendor for the March event." The reader can act from the notification without even opening the app.

Deadlines, consequences, and the apology habit

"No rush!" is a lie you tell to seem easygoing, and it costs you the reply. A message with no deadline never becomes urgent. It just becomes old. Name the date, and name what happens after the date. The second half matters more than the first, because it lets the other person do nothing and still get an outcome, which, honestly, is what a lot of silence is quietly asking for.

Before: "Whenever you get a chance, no rush!"

After: "I need an answer by Thursday to hold the print slot. If I don't hear from you, I'll book the later date and confirm it with you."

That is not a threat. It is certainty, offered for free. One rule, though: the deadline and the consequence have to be true. If Thursday passes and nothing happens, you have taught them that your deadlines are decorative, and every future one gets ignored for free. Pick a consequence you will actually execute, even a small one.

While you are at it, delete the apologies. "Sorry to bother you again" does two damaging things at once: it frames a legitimate ask as a bother, and it signals that ignoring you carries no cost, that you will absorb the awkwardness on their behalf. Apologize often enough and people learn your messages are optional. If the ask deserves a follow-up, follow up like it deserves one.

Before: "So sorry to keep pestering you about this, I know things are crazy on your end..."

After: "Third try on this one, because I can't order parts without your sign-off. Yes or no on the vendor?"

Naming the count ("third try") is information, not rudeness. It tells them the thread has history and that you are still standing in it, calmly.

Calmly is the hard part. By the third silent follow-up I am no longer writing to communicate, I am writing to be right, and drafts written to be right have a smell. That habit, the redrafting loop I have written about elsewhere, is a big part of why I built Unvent: now I type the annoyed version straight into the reply box, hit one keystroke, and send the version that still names the ask but has put the grudge down. Vent first, send the good one.

When to stop asking

Two follow-ups in one channel, written well, is enough. If both were cheap to answer and neither got answered, the channel has failed, not necessarily the relationship. An email thread that died can come back to life as a thirty-second chat message. A chat thread that died can become a phone call. The switch itself carries information: it says this is real enough that I picked up the phone. Escalating within the same channel, message after message into the same void, only proves you have nowhere else to go.

Sometimes the honest read is that the silence is the answer. A soft no, delivered by omission. When I suspect that, I do not send another bump. I send a closing message: "I'll assume this isn't a priority right now and close it out on my end. If that changes, ping me and I'll pick it back up." That message gets more replies than any follow-up I have ever written, because it takes the guilt out of the thread. People who could not face the pile can face an ending. Do not send it as a trick, though. Send it when you mean it, and close the thing out, because a fake ending that gets reopened by you is just "no rush!" with extra steps.

The strange part is what all this did to my first messages. Write enough follow-ups this way and you notice that a good follow-up is just what the original message should have been: context in one line, a single ask, a date, a default. If your follow-ups keep outperforming your openers, stop writing openers. Write the follow-up first, and send that.