Write

How to Write a Follow-Up Email That Gets a Reply

A follow-up email works when it makes the next action easier, not when it announces that you are still waiting. A good one restates the decision you need in a form the reader can answer in a word, or adds one new reason to reply. This page gives you templates for chasing an overdue decision and for keeping a sales thread alive, plus before/after examples you can copy and adapt.

Guide

Key points

Most weak follow-ups do the same thing: they express that the sender is waiting. "Just checking in," "circling back," "per my last email." None of these help the reader act. A follow-up that gets a reply either lowers the effort of answering the original ask, or brings a genuinely new reason to write. If it does neither, it is noise, and it trains the reader to ignore your thread.

  • Make the next action easier, not louder. Restate the ask in a form the reader can answer in one word, or add one new useful thing: a sharper angle, a proof point, a resource, a clearer deadline.
  • Give the deadline structure. Write the date, time, timezone, and reason, and say what happens if you do not hear back. "Please reply by Thursday 16:00 CET; we need the decision before sending the client quote."
  • Drop the irritation. Passive-aggressive phrasing loses replies even when your frustration is fair. Replace the jab with the request, the dependency, and the next step.

Two follow-ups are not the same email twice

A reply-chasing follow-up and a sales-sequence follow-up have different jobs. When you are waiting on a decision from someone who already knows the context, the follow-up should re-surface the exact ask and make the reply trivial: "approved" or "hold." You do not need a new angle; you need to remove the friction of finding the original thread. When you are following up on outreach that has gone quiet, repeating the pitch does nothing. Each touch has to earn its place with something new the reader did not have before.

Sequence the pressure, do not perform it

When a decision is genuinely blocking work, escalate across follow-ups without turning up the emotion. The first follow-up is a low-friction reminder. The second shares the business impact of the delay and states what happens if the deadline passes. The final note records that the deadline passed, states the action you are taking, and closes the loop: "We are moving this to next week's submission. No action needed unless you want us to reopen it." The strength comes from facts, impact, and consequences, not from adjectives or a wounded tone.

Only use "I'll proceed unless I hear otherwise" when it is legitimate

A default-action close is useful when the default is genuinely fair: "I'll book the Tuesday slot unless I hear otherwise by Friday." It is not a tool for forcing explicit approval through silence. If the reader's sign-off actually matters, ask for it directly and keep asking; do not manufacture consent by declaring that no reply means yes.

Stop when there is no new reason to write

On the sales side, a follow-up is not "just bumping this" with a fresh timestamp. Add one reason at a time: a tighter read on the same problem, a comparable proof point, a practical resource, a clarification of fit, a referral path, or a respectful close. When you run out of new reasons, stop. In practice, three to five thoughtful touches is the working ceiling for most cold sequences; past that, you are spending goodwill you cannot get back.

Check

Check your writing

We never store your text or use it to train AI.

125/800

Templates

Templates

First follow-up on a pending decision (low friction)

When to use: the reader already has the context and you just need the decision surfaced again. Next action: quote or link the original ask directly above this so they do not have to search for it, and fill in a real {dependency} so the deadline has a reason.

Hi {name},

Following up on the approval request below. Could you reply with "approved" or "hold" by {day} {time} {timezone}?

We need the decision before {dependency}. If a full review is not possible this week, your call on the {section} alone is enough to unblock us.

Thanks,
{your name}

Second follow-up: share the impact of the delay

When to use: the first reminder went unanswered and the delay now affects a downstream step. Next action: name the concrete consequence ({downstream step}) instead of implying urgency, and keep the reply format to one word.

Hi {name},

We still need a decision on {item} to move forward this week.

If we do not have your go-ahead by {day} {time} {timezone}, I'll hold {deliverable} until next week rather than send it without sign-off. That keeps us safe but pushes the {downstream step} back by a week.

A one-line "go" or "hold" is all I need.

{your name}

Final note: close the loop without a threat

When to use: the deadline has passed and you are recording the default action, not chasing. Next action: keep the tone administrative, not resentful. State what you did and leave a clean path back in.

Hi {name},

Closing the loop on {item}. Since we did not have a decision by the deadline, we are moving it to {next window} rather than proceeding without sign-off.

No action needed unless you want us to reopen it, in which case just reply here and I'll bring it back into this week.

Thanks,
{your name}

Sales follow-up that adds a new angle

When to use: an outreach thread has gone quiet and you have a genuinely new reason to write. Next action: make {new trigger} something real and specific to the account. If you have no new reason, do not send this; stop the sequence instead.

Hi {name},

Following up on my note about {problem}. Since I wrote, {new trigger} came up, which usually makes {specific issue} harder to manage.

One team in a similar setup handled it by {mechanism in one line}. I would not assume the same fit without comparing your workflow, but the pattern may be relevant.

Worth a 20-minute call to compare notes, or should I send a short example first?

{your name}

Examples

Before / After

Before

Per my last email, I am still waiting for your response.

After

Following up on the approval request below. Could you reply with "approved" or "hold" by Thursday 16:00 CET? We need the decision before sending the client quote.

What changed: the irritation was replaced with the exact ask, a one-word reply format, and a reason for the deadline. Why it is better: the reader can act in seconds instead of decoding your mood.

Before

Just floating this back to the top of your inbox. Any update?

After

We still need a decision on the Acme discount to issue the quote this week. If we do not have approval by Thursday 16:00 CET, I'll hold the quote until next week rather than send it without sign-off.

What changed: a content-free bump became the business impact plus what happens if the deadline slips. Why it is better: it gives the reader a real reason to prioritize the reply.

Before

Just bumping this in case you missed it. Let me know if you are interested!

After

Since I wrote, your enterprise plan launch went live, which usually puts more pressure on onboarding handoffs. One team in a similar setup cut that friction by combining onboarding milestones and support signals in one view.

What changed: a repeated pitch became a new, account-specific reason to reply. Why it is better: it earns the follow-up with something the reader did not have before.

FAQ

How long should I wait before following up?

Match the wait to the ask and the deadline you already set. For a decision with a Thursday deadline, a follow-up on Wednesday is reasonable. For cold outreach with no prior reply, a few business days between touches is typical. The gap matters less than whether the follow-up adds something; a fast bump with no new value still gets ignored.

How many times can I follow up before it becomes annoying?

For a decision you are owed, follow up until you have an answer or a stated default action, then stop. For cold outreach, three to five thoughtful touches is the practical ceiling, and only if each one brings a new angle, proof, or resource. Once you have nothing new to say, stopping is the stronger move.

Is it fine to write "I'll proceed unless I hear otherwise"?

Only when the default is genuinely fair and the reader would expect it. It works for low-stakes logistics like booking a time slot. It is not a way to force approval through silence; if explicit sign-off actually matters, keep asking for it directly instead.

What should I never write in a follow-up?

Avoid phrasing that vents instead of helping: "per my last email," "as previously stated," "gentle reminder," "I am still waiting for your response," and fake urgency like "please revert urgently." They cost you replies even when your frustration is justified. Lead with the request, the dependency, and the next step.

Keep writing in Inki

Start from a template, then edit until it sounds like you.

Start writing in Inki

Links

Related links

English
Made by n, Inc.