Urgent Follow Up Email: Templates and Limits

What makes a follow-up email urgent?

A follow-up is urgent when something changes for the recipient at a fixed point in time. A quote expires, a slot at an event closes, a contract renewal date passes, or a project can't move until they sign off. If you can't name that date and what happens after it, the email isn't urgent. It's just impatient, and readers can tell the difference.

That gives you a quick test before you write anything. Can you finish the sentence "If I don't hear back by [date], [specific consequence]"? If you can, the urgency is real and belongs in the first line. If you can't, send a normal follow-up instead. How long to wait between touches and how many to send are separate questions from urgency.

If your question is broader, like how do you write a follow up email that isn't urgent at all and when it should go out, start with the guide to timing, threading and when to stop.

How do I make an email urgent?

Urgency goes in three places, and the recipient should see it before they open the message:

1. 1 Subject line: name the deadline and the topic, for example "Sign-off needed by [date]: [project]". A date tells the reader more than the word "urgent" does.
2. 2 First sentence: say the decision you need and by when. Put background after the ask, not before it.
3. 3 Fallback: name who else can decide, or ask the recipient to forward it. That way, an absent recipient doesn't leave the deadline hanging.

Some mail clients also let you flag a message as high importance. Outlook does this, and it writes header fields such as Importance or X-Priority into the message. The receiving client decides whether and how to show that flag. Gmail's compose window has no importance setting of its own. The flag tells the reader nothing about why the email matters, and Google's published sender guidelines say nothing about it. Those guidelines are about authentication and complaint rates. Use the flag with colleagues and clients who expect it, not with prospects.

Here's what doesn't work. An all-caps "URGENT" in the subject line of a first or second cold email, a typed "Re:" on a message that was never a reply, or a deadline you invented. The FTC's CAN-SPAM compliance guide for business says subject lines must not mislead people about what the message contains.

Sales follow up email template for a real deadline

This template assumes there was an earlier conversation or a sent proposal, and a date that actually matters. Send it as a reply in the existing thread so the earlier message sits right underneath it.

Subject: [Original subject] (decision needed by [date]) Hi [First name], I need your go/no-go on [proposal/quote] by [date and time]. After that, [specific consequence: the pricing lapses / the slot goes to the next team / delivery moves to (later date)]. What's needed: - [Decision 1] - [Decision 2, if any] If someone else owns this now, who should I ask? A one-line reply is enough. [Your name]

Swap in whichever consequence is true and delete the others. If none of them are true, don't use this template. For situations without a deadline, like after a demo, after a proposal or after silence, the sales follow up email template examples cover each case.

Follow up sales email: what goes in it

Any follow up sales email, urgent or not, needs the same four parts in this order. First, the ask. Second, a reminder of what came before, in one line. Third, what the recipient gets or avoids by answering. Fourth, an easy way out, such as a forward or a one-word reply. Leave out "just checking in" and "bumping this to the top of your inbox". Neither phrase gives the reader anything to act on, so it reads as a demand on their time.

How do I politely remind someone of an email?

A polite reminder is a short reply to your own earlier message. It assumes the email got buried and doesn't assume the person ignored it. In practice, that means hitting Reply in your sent folder, not writing a new message. A real reply carries the In-Reply-To and References header fields that the internet message format standard defines for replies. Clients use these to show your reminder in the same conversation as the original. A new message with "Re:" typed into the subject doesn't carry them, so the context can end up in a separate thread.

Wording that holds up: "Resurfacing this in case it got lost. The only open question is [X]. Happy to send it to someone else if that's easier." You don't apologise and you don't add guilt, and the recipient can answer in one line. If you've had no response at all, check for bounces before sending a reminder, since a reminder to a dead address does nothing. The templates for a follow up email after no response go through that order.

Email prospecting: where urgency doesn't belong

Email prospecting means contacting people who haven't dealt with you yet, to find out whether they're a fit. At that stage, there's almost never a deadline that matters to the prospect. Your quarter end matters to you, not to them. Adding urgency to cold prospecting turns a polite introduction into pressure from a stranger. That's the moment when people reach for the spam button instead of the delete key.

There's also a legal point for EU recipients. Germany's Unfair Competition Act (UWG) generally requires prior consent for advertising by email, including to business recipients. US CAN-SPAM, by contrast, works on an opt-out basis. A fake deadline doesn't change which rule applies to your list. Check consent before you think about tone. When a prospecting sequence has run out without a reply, end it with a closing message rather than an escalation. The breakup email templates show how to do that without inventing pressure.

Cold email deliverability: what an urgent follow-up can break

Cold email deliverability is decided by the receiving server, not the sender. That server checks whether SPF and DKIM pass and line up with your From domain under DMARC, and it weighs your domain's reputation, bounces and complaints. An urgent follow-up affects that decision in two ways. First, every follow-up adds to the volume your mailbox and domain send. Second, a pushy message to a stranger is likelier to be reported as spam, and Google's sender guidelines treat the user-reported spam rate as a signal for bulk senders.

Common failure modes in practice: sending a burst of urgent follow-ups in one batch on top of normal volume, following up with addresses that already hard-bounced, and sending from a domain whose DKIM signature isn't aligned with the From address. All three show up in the authentication headers or in bounce logs, so you can check for them. The breakdown of what decides cold email deliverability walks through each check.

What is a good email deliverability rate?

Deliverability rate usually means the share of sent messages the receiving servers accepted: accepted divided by sent. Accepted isn't the same as inboxed. A receiving server can accept a message and still file it as spam, and the delivery rate won't show that. So judge two things separately: bounces after list verification, which you can read in your bounce logs, and where seed-test copies were filed, which a placement test reports per mailbox provider. There's no single standard figure. How the two numbers differ is covered in email deliverability rate: delivery vs inbox.

How EmailFlow OS sends a follow-up from your own domain

This section describes a EmailFlow OS product on its own, not against other tools. EmailFlow OS sends personalised AI video email for B2B cold outreach. You record one video and upload it to EmailFlow OS, connect your Brevo account and your sending domain, and import your prospect list into EmailFlow OS. EmailFlow OS then creates a personalised version of that one recording for each recipient, not each company. Two people at the same firm get two different versions.

Each version goes out from your own inbox, through your own Brevo account and your own sending domain, never through a shared platform sender. For anything urgent, that means the complaints and bounces described above are recorded against your domain and nobody else's. Your SPF, DKIM and DMARC records are what receiving servers check, and the rules on real deadlines, threading and consent apply exactly as they do to a plain-text email.

Questions people ask

? Is it okay to write URGENT in the subject line?

With colleagues or an existing client who's waiting on a decision, yes, though a date says more: "Approval needed by Friday" tells the reader what to do, while "URGENT" only tells them how you feel. With cold prospects, no. You have no shared deadline with them, and the FTC's CAN-SPAM guidance treats a misleading subject line as a violation.

? Does marking an email as high importance help it reach the inbox?

No. The importance flag is a header field such as Importance or X-Priority that some clients show as an icon. Google's sender guidelines list SPF, DKIM, DMARC, unsubscribe handling and spam complaint rates as what senders need to manage, not importance flags. Placement is decided by the receiving server based on authentication and reputation, not on how the sender labels the message.

? What is a polite follow-up email?

A polite follow-up is a reply in the original thread that restates your one open question, assumes the first email got buried, and gives the recipient an easy way out, like a one-word answer or forwarding it to a colleague. Compared with a new message that starts over, it keeps the earlier context visible through the In-Reply-To header.

? How is an urgent follow-up different from a breakup email?

An urgent follow-up asks for a decision before a specific date and expects a reply. A breakup email closes a sequence that got no response and says you'll stop writing. One adds a deadline and the other removes pressure. Don't combine them: a breakup email with a fake deadline is still a fake deadline.