Oops email subject lines: 30 examples by mistake
30 subject lines for correction and oops emails, grouped by mistake: date, price, code, link, name, wrong list. Plus three rules for getting opened.
By Hassan Ali, Okaytosend team · Updated
An oops email is the short follow-up you send when a campaign went out with a mistake in it. A good correction email subject line does the whole job on its own: it says this is a correction, and it gives the right fact. Someone who never opens it should still turn up on the right day with the right code. Below are 30 subject lines grouped by the kind of mistake, each with preview text, and the rules behind them.
Three rules for an oops subject line
- Put the right fact in the subject line. "Correction: the deadline is 7 March" works unopened. "Oops, we made a mistake" doesn't.
- Lead with the word that matters. Phones cut subject lines short, so "Correction" or "Updated" and then the fact, before anything else.
- Match the tone of the mistake. A playful "Oops" suits a retail brand and a typo. A wrong renewal date for members, or anything about money, deserves a plain "Correction".
Wrong date or time
| Subject line | Preview text |
|---|---|
| Correction: the early-bird deadline is 7 March | Not 14 March, sorry for the mix-up |
| Updated date: doors open Thursday 11 March | Yesterday's email had the wrong day |
| Correction: the webinar starts at 4pm GMT | That's 12pm EDT on Thursday 25 March |
| Right date this time: Friday 12 March | One quick fix to yesterday's invitation |
| The renewal deadline is 31 January, not 31 March | Please renew by then to keep your member rate |
Wrong price
| Subject line | Preview text |
|---|---|
| Correction: the Team pass is $1,450 | Booked at $1,250 already? That price stands |
| Price correction for this weekend's sale | The right prices, and what happens if you've ordered |
| Updated: member rates for 2027 | One rate in yesterday's email was wrong |
| We got a price wrong (and we'll honour it) | If you booked before 5pm, you pay what you saw |
| Correction: delivery is free over £40 | Not £50, as yesterday's banner said |
Discount code that doesn't work
| Subject line | Preview text |
|---|---|
| Correction: your code is SPRING25 | Sorry if you tried the old one |
| Oops, here's the code that works: SPRING25 | 25% off everything until 31 March |
| The right code (and an extra day to use it) | SPRING25 now works until Thursday 25 March |
| Your discount code, fixed | Use SPRING25 at checkout |
| That code didn't work. This one does. | SPRING25, 25% off any pass |
Wrong or broken link
| Subject line | Preview text |
|---|---|
| Correction: the right link to register | Yesterday's button went to last year's page |
| Here's the link that works | Everything else in yesterday's email was right |
| Fixed: the recording link | Sorry, the first link pointed to the wrong session |
| Oops, wrong link. Try this one. | The 2027 programme, as promised |
| Updated link: download the report | The first link has expired |
Wrong name, speaker or venue
| Subject line | Preview text |
|---|---|
| Correction: the keynote is in Hall C | Not Hall B, as yesterday's email said |
| A correction about our closing speaker | We had her job title wrong yesterday |
| Updated: the right venue for Thursday 11 March | Same time, different building |
| We spelt a sponsor's name wrong | Here's the corrected programme |
| Correction to yesterday's speaker list | One title was out of date |
Sent to the wrong list, or sent twice
| Subject line | Preview text |
|---|---|
| Please ignore our last email | It reached you by mistake. Nothing to do. |
| Sorry, that one wasn't meant for you | You're still on the list you signed up for |
| You got that twice. Sorry. | One email, sent once more than we meant to |
| Your renewal is already done | Please ignore this morning's reminder |
| Oops, a test email escaped | No need to do anything |
Bad news: cancelled, postponed or sold out
Not every hard subject line follows a mistake. When the news itself is bad, the same rules apply: say what changed, and what the reader should do next.
- Thursday's workshop is postponed (your place is safe)
- Change of plan: the summit moves online
- Early-bird passes have sold out. Here's what's left.
- We're cancelling the 11 March session, and refunding everyone
What to put in the email itself
Keep it shorter than the original: the right fact first, what was wrong in one sentence, a single apology, and the one action that matters. There are full templates for each kind of mistake in how to write a correction email, and a quick test for whether a typo needs one at all in typo in a marketing email.
Better still: no oops email
Every subject line on this page exists because a fact was wrong in a test send and nobody noticed. Okaytosend checks the test send against your own website and files before it goes out: every date, price, code, name and link, text in images included, with both quotes side by side when something disagrees. If you want to check one kind of fact by hand, try the time zone converter or the date and weekday checker.
Questions and answers
What is an oops email?
An email sent after a campaign went out with a mistake: a wrong date, price, code or link, or a send to the wrong list. It's usually short, says what was wrong and gives the right fact. "Oops" in the subject line keeps the tone light; "Correction" is plainer and suits more serious mistakes.
What's a good correction email subject line?
One that gives the right fact, not only the fact that there was a mistake. "Correction: the early-bird deadline is 7 March" works even for people who never open it. "Oops, we made a mistake" makes them open it to find out what changed.
Should I use "oops" or "correction"?
"Oops" suits a friendly brand and a small, fixable mistake like a broken link or a code typo. Use "Correction" or "Update" when the mistake is about money, a deadline or anything people may already have acted on, and for formal senders like associations and universities.
Do oops emails get more opens?
You'll often read that correction emails get opened more than usual, but there's little reliable data behind it, and it's no reason to send one. Every correction costs a little trust and an extra email in the inbox. Send one only when the mistake changes what people will do.