Key takeaways
- Same thread, one new reason, one one-word ask, shorter each time.
- Day 3, day 7, day 14, then a polite close; the close gets replies too.
- Never apologise for chasing and never repeat the original; add a date, proof or a smaller ask.
- Make the sequence a schedule so the follow-ups happen without memory.
A good follow-up is not a reminder that you exist. It is a shorter, easier version of the original ask, sent at a better moment, with one new reason to answer. Here is the structure, the timing, four templates that follow it, and the mistakes that get a follow-up deleted.
What makes a follow-up email get a reply?
The data first: in the largest public outreach dataset, one follow-up lifted replies by 65.8% over a single email, and the baseline reply rate was 8.5%. The numbers are in follow-up email statistics. The follow-up works because the first email arrived at a bad moment, not because the reader decided against you. So the follow-up's job is to arrive at a better moment and be easier to answer than the original.
- Reply in the same thread. The context is already there; a new subject line restarts the work for the reader.
- One sentence of why now. A new reason: a date, a result, a piece of information they did not have.
- One ask, phrased for a one-word answer. "Does Thursday work?" beats "Let me know your thoughts."
- Shorter each time. Day 3 is three sentences; day 14 is one.
How long should you wait before following up?
Three days for the first follow-up, a week for the second, two weeks for the third, then a close. Shorter than three days reads as pressure. Longer than two weeks and the thread has scrolled out of the inbox, so the reader has to reconstruct who you are.
| Touch | Day | What it adds | Length |
|---|---|---|---|
| Original | 0 | The context and the ask | Under 100 words |
| Follow-up 1 | 3 | A date or a reason to decide this week | Three sentences |
| Follow-up 2 | 7 | Proof, or a smaller ask | Two sentences |
| Follow-up 3 | 14 | A yes/no question | One sentence |
| Close | 21 | An exit that leaves the door open | Two sentences |
Weekday mornings in the reader's time zone are a safer bet than Friday afternoons, but the day matters less than the gap. Pick the gaps once and keep them; a plan you decided in advance is one you will actually run.
PeakLook does this from your own data. Drafts the reply. Keeps the follow-up going. Join the free beta →
Follow-up email templates: day 3, day 7, day 14 and the close
Day 3
Subject: Re: [original]
Hi Dana, floating this back up in case it got buried. We are holding the pilot slot until the 24th and I would rather give it to you than the waitlist. Would a 20-minute call Thursday or Friday work?
Three sentences. The new reason is the date, and a date works for the same reason a short expiry gets a voucher used: an open-ended ask has no edge, and the behavioural research in the deadline effect says an edge is what moves people. The ask offers two concrete options, so the reply can be one word.
Day 7
Re:
Hi Dana, one more thing that might make this easier: the State University team ran the same pilot in three weeks and wrote up the results here [link]. Happy to send the two-page version if a call is too much right now.
This one adds proof and lowers the ask at the same time. If the call was the obstacle, the two-page document removes it. Never repeat the day-3 email with a different opening line; a follow-up that adds nothing is the one that gets deleted.
Day 14
Re:
Hi Dana, is this still worth a look on your side, or should I close it out? A one-word answer is perfect.
One sentence, one question, both answers acceptable. "Close it out" is not a loss; it is an answer, and an answer lets you stop spending attention on the thread.
The close
Re:
Closing this out so it does not keep landing in your inbox. If the timing changes, reply to this thread and I will pick it straight back up. Thanks for reading.
The close gets replies surprisingly often; it removes the guilt and leaves the door open. It also signals that you keep your word about stopping, which is what makes the next thread with the same person possible.
Follow-up email after a meeting, an interview or a quote
The same structure applies when the follow-up is the first email you send, after a meeting, an interview or a quote. Lead with the one thing that was agreed, add the one thing you promised, and ask the one question that moves it forward.
After a meeting:
Hi Dana, thanks for the time today. You asked for the pricing on the two-team option; it is attached, with the onboarding timeline we discussed. Shall I hold the 24th for the kick-off, or is a later date better?
After an interview:
Hi Dana, thank you for the conversation this morning. The point about scaling the support rota stuck with me, and I have put two ideas on it in the attached page. Is there anything else I can send to help the decision?
After a quote:
Hi Dana, following up on the quote from the 10th. The price holds until the 24th; after that the supplier's rate changes. Would you like me to book the slot, or shall I close it out?
Each one is under seventy words, carries one new thing and ends in a question with a short answer. Then the day 3, 7, 14 plan starts from there.
Follow-up email subject lines
Keep the original subject with "Re:" in front of it. That is the whole rule for a follow-up inside a thread, and it is the rule most people break by starting a new email called "Following up" or "Checking in", which tells the reader nothing and strips the context. If you must start a new thread, because the original was months ago, write the subject as the ask: "Pilot slot until the 24th: still interested?"
Avoid "Quick question", "Touching base" and anything with "just". They read as filler, and filler in a subject line predicts filler in the body.
Mistakes that kill a follow-up
- Apologising for chasing. "Sorry to bother you again" frames the email as an imposition. A new reason frames it as useful.
- Repeating the original. The reader already has it, one message up. Add something or do not send.
- Asking an open question. "Any thoughts?" requires the reader to compose. "Thursday or Friday?" requires one word.
- Following up on the wrong channel. A LinkedIn message about an email thread doubles the reader's work. Stay in the thread.
- Not stopping. Any reply, including "no", ends the sequence. So does a bounce. Keep chasing after either and the relationship is the cost.
Complete three-step and five-step plans built on these rules, with copy for every step, are in email sequence examples that work.
How to follow up without remembering
PeakLook turns exactly this structure into a template: four steps at +3, +7, +14 and +21 days, drafted in your voice from the original thread, sent by the server on the schedule, and stopped automatically the moment Dana replies to any of them. The drafts are shown in gold until you approve them, so nothing goes out that you have not read. If you are choosing a tool for this, the AI email assistant comparison notes which products carry follow-ups on a schedule and which only remind you.
Want this answered from your own data?
That is what PeakLook does. Drafts the reply. Keeps the follow-up going. In private beta — the waitlist is free.
Questions
How do you politely follow up on an email with no response?
Should follow-ups apologise for chasing?
How many times should you follow up?
What if they opened it and did not reply?
What subject line should a follow-up email have?
Can I automate the first email too?
Sources
- Backlinko & Pitchbox (2019). We analyzed 12 million outreach emails. Here's what we learned. https://backlinko.com/email-outreach-study
Builds the UPeak apps and writes up the research behind them.