Reading time: 8 min · Last verified: August 2026 · SMTPedia editorial team
Every guide to the no response email reminder starts in the same place: the wording. Be polite, be short, add a deadline. That advice is fine, and it assumes something nobody checks: that the original message reached a human being. Much of the silence senders read as rejection is not rejection at all. It is a message sitting in a spam folder, filed under a tab nobody opens, or still queued on your own server.
This page runs that check first, then gives you the timing rules and five reminders you can copy. The copywriting comes second on purpose: a beautifully worded reminder sent into the same spam folder is just a second message in the spam folder.
Confirm delivery, wait two to three business days, then send one short reminder in the original thread. Keep it under six lines, restate the ask in the first sentence, give one clear next step, and set a stop rule before you start. Two reminders on a live thread is normal. Five on a cold one is a complaint waiting to be filed.
First Question: Did the Original Email Actually Arrive?
Silence has at least four causes and only one of them is a decision. Before you spend an hour on the perfect follow up, spend two minutes ruling out the other three.
It reached the mailbox, not the inbox
Accepted at the door, then routed to spam. Nothing bounces, so it looks identical to being ignored.
It landed in a tab nobody reads
Delivered, then sorted away from the main view. Common for anything that reads as templated.
It never left the queue
A temporary failure at the far end. Your server retries and no error reaches you.
They saw it and have not replied
The only case where wording matters, and the one everyone assumes it is.
Filtered: accepted, then buried
A server that accepts a message and then files it in spam sends you no signal: no bounce, no error code, nothing. If several people on the same domain have gone quiet in the same week, that pattern is worth more than any single non-reply, and the cause is usually on your side. Our breakdown of the reasons legitimate mail gets filtered as spam covers the checks worth running before you send anything else to that domain.
Filed: delivered to a view they do not check
Consumer mailboxes sort incoming mail before the recipient sees it, and a message that reads as a campaign rather than a personal note gets sorted accordingly. If your reminder is going to a personal address, it is worth knowing how Gmail decides which tab a message belongs in before you conclude that nobody wants to talk to you.
Stuck: still in the queue, days later
Temporary failures are the quietest case. When a receiving server answers with a 421 service temporarily unavailable response, your message is not rejected and not delivered: it goes back into the queue and gets retried on a schedule your provider controls. A full recipient mailbox behaves the same way, and the 452 4.2.2 out of storage response is one you will only ever see if you look at your sending logs. Neither produces the bounce notification most senders wait for.
The practical version: open your sending logs before you open your drafts folder. Only once the log shows the message was accepted are you looking at cause four, which is the only one a reminder can fix.
Timing: How Long to Wait Before the Reminder
No rule is written down anywhere, but the pages ranking for this query converge on one window: two to three business days for a normal professional thread. That is a convention, not a standard, and context moves it a long way.
| Situation | Wait before reminder 1 | Stop after |
|---|---|---|
| Active client thread | 2 to 3 business days | 3 reminders |
| Approval or sign off you are blocked on | 1 business day | Escalate, do not resend |
| Job application, no acknowledgement | 1 to 2 weeks | 1 reminder |
| After an interview | The stated decision date, plus 2 days | 2 reminders |
| Survey invitation | 3 to 5 days | 2 reminders |
| Cold outreach | 3 to 4 business days | See the cadence rules |
Cold outreach is the one row that does not belong with the others: reminding someone who asked to hear from you and reminding a stranger who did not carry different risks and need different stop rules. Our guide to follow up cadence and stop rules for cold email treats that case on its own terms.
How to Write the Reminder: Five Parts, Six Lines
A reminder is not a new pitch. It is a second attempt at one ask, and the shorter it is the more obvious that ask becomes. Five parts, in this order.
Reply inside the original thread so the first message is one scroll away.
Restate what you need in sentence one. Not the context, the request.
One line on what is blocked without it. Consequence, not guilt.
Offer a one word reply option. Yes, no, or a date is easier than prose.
Sign off and stop. No apology for writing, no second paragraph.
Two habits do more damage than any wording choice. Apologising for following up frames your own request as an imposition and invites the reader to agree. Starting a fresh thread strips the recipient of the context that would let them answer in ten seconds, and if you do start fresh the subject line carries the whole burden: what makes a business subject line work or fail is worth reading before you write one.
Five Reminders You Can Copy
Each is written to be sent as a reply inside the existing thread. Replace the bracketed parts and delete nothing else: the length is the point.
Subject: stays as it is, reply in thread
Hi [Name],
Following up on the [document] I sent on [date]: are you able to confirm [the one thing] this week?
Once I have that I can start [next step]; without it the [milestone] slips.
A one line yes or a new date both work.
Thanks,
[You]
Hi [Name],
[Item] is waiting on your approval since [date] and it is the last thing between us and [outcome].
If you are happy with it, reply “approved” and I will proceed today.
If someone else should sign this off, point me at them and I will take it from here.
[You]
Hi [Name],
I applied for the [role] position on [date] and wanted to check the search is still open.
I am still very interested, and happy to send anything else that would help.
If the role is filled, a quick note saying so would be appreciated and I will stop chasing.
Best,
[You]
Hi [Name],
Thanks again for the conversation on [date]. You mentioned a decision by [date], so I wanted to check where things stand.
No rush if the timeline has moved: knowing the new date is enough.
Best,
[You]
Subject: [Survey name]: 3 minutes, closes [day]
Hi [Name],
The [survey name] is still open and closes on [date]. It takes about [n] minutes.
[Link]
If you already completed it, thank you, and please ignore this.
[You]
Unsubscribe link and postal address follow in the footer.
Why survey reminder email examples need their own rules
Most survey reminder email examples are written for one recipient. A survey reminder is almost never that: it goes to a list, which moves it into bulk mail and a different set of obligations. It needs a working unsubscribe path and a valid physical postal address in the footer, and the “if you already responded, ignore this” line is not politeness but the cheapest way to avoid a complaint from someone who did.
The other rule is suppression. Anyone who already answered should be removed from the send. A reminder survey email sample that reaches people who already gave you twenty minutes of their time is the fastest way to teach a list that your mail is not worth opening.
Automated Reminders and Email Notification Examples
Once a reminder is generated by a system rather than typed by a person, it changes category. A renewal notice, a cart reminder, an unsigned document nudge: most useful email notification examples are exactly this, and the classification decides how they are filtered and what they must contain. Our reference on what counts as a transactional email and what does not sets out where the line falls.
The mistake worth avoiding: labelling a marketing reminder as transactional to skip the unsubscribe requirement. The classification follows the content, not the field you set in your platform. A promotional nudge dressed as a receipt is still promotional, and still subject to the rules on opt out and postal address.
A useful sample email notification also says who sent it and why the recipient is getting it. That one line stops a legitimate reminder being reported by someone who forgot they signed up, and confused complaints count against you exactly like annoyed ones.
Stop Rules: When a Reminder Becomes a Complaint
At volume, the line between persistent and unwelcome stops being a matter of taste. Google asks bulk senders to keep their reported spam rate below 0.30 percent, and reminder sequences are one of the fastest ways to cross it: each extra send to a non responder raises the chance of a complaint without raising the chance of a reply.
On the legal side, the Federal Trade Commission requires a valid physical postal address in commercial mail and gives you ten business days to honour an opt out. That is the floor; mailbox providers ask for faster. Wire the suppression list in before the schedule.
Three hard stops. Stop when they reply, even to say no. Stop when the address bounces. Stop at your stated maximum, decided before the first send rather than in the moment. A reminder sent past a stop rule is not persistence: it is a message the recipient has already answered by not answering.
One last note. Mail programs thread and collapse replies differently, so a reminder that reads as one tidy line in your client can arrive as a wall of quoted text in someone else’s. For a mixed audience, the directory of desktop, web and mobile email clients is a quick way to see what your recipients are actually reading your message in.
Frequently Asked Questions
How do you send a reminder email if there is no response?
Reply inside the original thread, restate the specific ask in the first sentence, add one line on what is blocked without it, and offer a reply that takes one word. Confirm the first message was delivered before you send anything.
How long should you wait before sending a no response email reminder?
Two to three business days for an ordinary professional thread, one business day when you are blocked on an approval, one to two weeks for a job application. No standard sets these figures: they are convention.
How do you professionally email someone who has not responded?
Keep it under six lines, do not apologise for writing, and do not imply the silence was rude. Assume a full inbox rather than a decision, and make the reply cheap: a yes, a no or a date beats a paragraph.
How many times can you follow up before it is too many?
On a live thread with someone who knows you, three is a reasonable ceiling. On cold outreach it is lower and the risk higher, because complaints from strangers count against your sending reputation. Decide the maximum before the first send.
What should a survey reminder email say?
The closing date, the time it takes, the link, and a line telling anyone who already responded to ignore the message. Because it goes to a list, it also needs a working unsubscribe link and a valid physical postal address in the footer.
Should I resend the original email or write a new one?
Reply in the thread. Resending the same message with no new text reads as an error, and a fresh thread throws away the context that lets the recipient answer quickly. Keep the original underneath, add four lines above it.
Why do my reminder emails get no response at all?
Check delivery before wording. If several recipients on one domain go quiet at once, the messages are probably filtered rather than ignored. Your sending logs show whether the mail was accepted, deferred, or never left the queue.
About the Author

Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.

