How to Write a Follow-Up Email (+ Templates)
To write a follow-up email, reply in the original thread, remind the recipient of the specific context in one sentence, add something new they didn't have before, and close with a single, low-friction question. Keep it under 100 words. The most common mistake is sending a message whose only content is "just checking in" — that asks the reader to do work with no reason to.
The one rule that fixes most follow-ups
Every follow-up should give before it asks. That's it. If your message contains no new information, no new angle, and no new reason to respond, you're essentially sending a nudge, and nudges annoy people who are already behind on their inbox.
"New" doesn't have to be dramatic. A relevant case study, a changed deadline, an answer to an objection they raised, a link to the thing you promised, a note that a competitor just did something relevant — any of these convert a nag into a message worth opening. The bar is low, but there is a bar.
Timing: how long to wait and how many to send
Follow-up cadence depends on what you're following up on. A proposal follows a different rhythm than a job application. This is a reasonable default structure that you can adjust to your industry.
| Scenario | First follow-up | Total follow-ups | Spacing |
|---|---|---|---|
| Sales outreach (cold) | 3 business days | 4–6 | 3, 5, 7, 10, 14 days |
| Proposal or quote sent | 3 business days | 3 | 3, 7, 14 days |
| After a meeting | Same day | 1–2 | Recap, then 5 days |
| Job application | 7–10 days | 2 | 10 days, then 14 |
| After an interview | 24 hours | 2 | Thank-you, then at stated deadline |
| Unpaid invoice | Day after due date | 3–4 | +1, +7, +14, +30 days |
| Networking or intro request | 7 days | 1–2 | 7 days, then let it rest |
Two structural choices matter as much as the timing. First, reply in the original thread so the recipient has the history one scroll away. Second, vary the send time — if your first email landed at 9 a.m. Tuesday and got buried, sending the follow-up at 9 a.m. Tuesday puts it in the same pile.
Anatomy of a follow-up that gets a reply
- Subject line. Reply in-thread and keep the "Re:" subject, or write a fresh one that names the specific thing: "Re: pricing for the Boise install." Never write "Following up" as the whole subject.
- Context line. One sentence: what you sent, when, and why it matters to them. "I sent over the retrofit quote last Thursday."
- The new thing. One or two sentences of value they didn't have before.
- One question. A single, specific, easy-to-answer ask. Multiple questions reliably produce zero answers.
- An exit. Give them a graceful way to say no. Counterintuitively, this raises reply rates because it removes the guilt of a non-answer.
Five templates you can adapt today
1. After sending a proposal
Subject: Re: [Project] proposal
Hi [Name] — sent the proposal for [project] last Thursday. Since then we wrapped a similar [type] job for [company], and the timeline came in about two weeks faster than we'd scoped, so I'd adjust your Phase 2 estimate down accordingly. Is the scope still what you had in mind, or has anything shifted on your end? Happy to revise before you take it to [decision maker].
2. After a meeting or call
Subject: Recap + the two things I owe you
Hi [Name] — good talking Tuesday. Recapping so we're aligned: you're aiming to launch by [date], the blocker is [issue], and you wanted numbers on [item]. I owe you (1) the integration doc and (2) a reference from a customer in your industry. Both attached. Anything I got wrong in that summary?
3. Cold outreach, second touch
Subject: Re: [specific observation about their business]
Hi [Name] — reaching back out on the [specific thing] I mentioned. I put together a short breakdown of how three [industry] companies handled the same problem; it's two pages and I'll send it whether or not we ever talk. Worth a look? If this isn't a priority right now, just say "not now" and I'll close the loop.
4. Unpaid invoice
Subject: Invoice #[number] — past due [X] days
Hi [Name] — invoice #[number] for [amount] was due [date]. Copy attached in case it got lost. If it's already in your payment run, let me know the expected date and I'll stop chasing. If there's a problem with the invoice itself, tell me what to fix and I'll reissue today.
5. The breakup email
Subject: Closing the file on [project]
Hi [Name] — I've reached out a few times about [topic] and haven't heard back, which usually means the timing is wrong or it's not a fit. Either is completely fine. I'm going to stop emailing so I'm not adding to your inbox. If [problem] becomes a priority later, reply to this thread and I'll pick it right back up.
These are starting points, not scripts. Rewrite them in your voice — a follow-up that reads like it came from a template is worse than a clumsy one that reads like a person. If you'd rather start from proven layouts than a blank page, a library of professionally designed email templates gets the formatting out of your way so you can focus on the words.
What kills follow-ups
- "Just checking in" / "bumping this up" / "circling back." These phrases signal that you have nothing to add. Delete them.
- Guilt. "I haven't heard back from you" makes the reader defensive. Their silence is not a moral failing; it's a full inbox.
- Restating the entire first email. They can scroll. Summarize in one line.
- Stacking questions. Three questions equals a task. One question equals a reply.
- Vague CTAs. "Let me know your thoughts" is unanswerable. "Does Thursday at 10 work?" is answerable in two words.
- Sending forever. After your breakup email, stop. Continuing past that point produces spam complaints, and complaints damage the deliverability of every email you send after.
When to automate and when to type it yourself
Automation is right for follow-ups where the trigger is objective and the content doesn't require judgment: abandoned carts, trial expirations, post-purchase check-ins, invoice reminders, webinar no-shows, and onboarding nudges. These are high-volume, predictable, and genuinely better handled by a system than by a person who will forget.
Type it yourself when the relationship is the point — a large proposal, a hiring conversation, a customer who complained, an introduction someone made for you. Readers can tell, and in those situations getting caught automating costs more than the time you saved.
The middle ground works well in practice: build the sequence in an email automation workflow with a rule that pulls anyone who replies out of the sequence immediately, then handle those replies personally. You get the discipline of a system with the responsiveness of a human, and nobody ever receives step three after they already answered step two.
A short pre-send check
- Is there one new piece of information in this email? If no, don't send it yet.
- Is there exactly one question?
- Is it under 100 words?
- Did I remove "just checking in" and every variant?
- Is there a graceful way for them to decline?
- Is this reply in the original thread?
Frequently asked questions
How long should I wait before sending a follow-up email?
Three business days is a solid default for sales and proposals, 24 hours after an interview or meeting, and a week to ten days for job applications. Waiting less than two business days on a cold email tends to read as pressure rather than persistence.
How many follow-up emails is too many?
For cold outreach, four to six spread over two to three weeks is the practical ceiling. For a warm conversation, two or three. Once you've sent a breakup email offering to close the file, stop — continuing past that point generates spam complaints that hurt your sending reputation.
What should I write instead of "just checking in"?
Lead with the new information instead. "The timeline on similar projects came in two weeks faster, so I'd revise your estimate" does the same job while giving the reader a reason to reply.
Should follow-up emails be in the same thread or a new one?
Reply in the same thread in almost all cases. It gives the recipient the full history without searching and it groups your messages instead of scattering multiple unread items across their inbox. Start a new thread only when the topic has genuinely changed.
Do automated follow-up emails work as well as manual ones?
For predictable, trigger-based situations like abandoned carts, trial expirations, and invoice reminders, automated follow-ups perform very well and are far more consistent than a human. For high-stakes relationship emails, write them yourself.
Want your follow-ups to send themselves — and stop automatically the moment someone replies? Build your first sequence with IGSendMail, free for up to 2,500 contacts.