A bad email makes the reader do the work the writer should have done: figure out what it is about, why it matters, what to do next, and who owns the next move. A good email answers those four questions before the reader has to ask them.
The fastest way to see the difference is to put the bad version next to the good version. Below are 12 bad email examples, 8 from everyday work and 4 from sales outreach, each paired with the good version that earns a reply and a one-line note on why the fix works.
What Counts as a Bad Email?
A bad email fails at one job: getting its point across without making the reader work for it. Almost every bad email pushes at least one of four questions onto the reader:
- What is this about? A vague subject or opening makes them guess.
- Why does it matter? No context makes them work out the relevance for you.
- What do I need to do? No clear ask makes them invent the next step.
- Who owns the next move? Too many recipients makes them work out whose job it is.
The 12 mistakes below are all versions of that one failure, in work emails and in sales emails. A good email answers these four questions before the reader has to.
The cost is rarely dramatic. It is a slow tax: a reply that takes three days instead of three hours, a message back asking what you actually meant, or a quiet drop in how seriously they take the next thing you send. Some older data lines up with this: in Boomerang’s 2016 analysis of email response rates (a broad sample, so treat it as historical context rather than a rule), emails of 50 to 125 words drew the best response rates, and messages that closed with a thank-you did better than formal sign-offs. The examples below make the case on their own.
Each example has three parts: the bad version, a line on why it fails, and the good version to send instead. The bracketed text is a placeholder to swap for your own details.
The 8 Most Common Bad Emails (Good vs Bad)
1. The Vague Subject Line
The subject line tells the reader what the email deserves their attention for. A vague one tells them nothing, so they cannot judge it without opening it, and it sinks.
Subject line: Quick question
Hi Priya, when you get a chance, can you look at the thing we discussed and let me know? Thanks.
Why it fails: nothing in the subject or the first line says what “the thing” is or what you need, so it waits.
Subject line: Need your sign-off on the Q3 budget by Thu
Hi Priya, could you review the Q3 budget (one tab, five lines changed) and reply with a yes or your edits by Thursday? Happy to walk through it on a quick call if easier.
Why it works: the subject carries the ask and the deadline, so they can act without opening a thread to find out what you want.
A few more, side by side:
| Bad subject line | Good subject line |
|---|---|
| “Hello” | “Intro: [Your Name] from [Company], re: [their project]” |
| “Follow-up” | “Following up: proposal feedback by Friday?” |
| “Update” | “Launch moved to Oct 14: what changes for you” |
| “Important” | “Action needed: confirm your slot for Tuesday” |
2. The Aggressive or Passive-Aggressive Tone
Tone travels further in writing than people expect, because the person reading supplies the voice. Pressure and blame read louder on a screen than they would out loud.
Subject line: Report???
Why isn’t the report done yet? The deadline is tomorrow and you are holding up the whole team. Please get it done ASAP.
Why it fails: the subject is hostile, the body blames before it asks, and the recipient opens defensive instead of helpful.
Subject line: Q3 report: still on for tomorrow?
Hi Sam, the Q3 report is due to the client tomorrow and I want to make sure we are on track. Is it still doable on your end, or is something blocking it I can help clear?
Why it works: it states the fact, assumes good faith, and offers help, which gets you the status you actually wanted.
3. The Too-Casual Email
The trap is rarely obvious slang. It is being a notch too familiar for the relationship, so a first-time client or a senior stakeholder reads you as breezy about their time. The same email that is fine for a teammate can land wrong with someone you just met.
Subject line: re: our call
Hey Priya! Thanks a mil for hopping on earlier 🙂 Really enjoyed it. Will shoot over that deck super soon, promise. Anything else on your end just lmk!
Why it fails: to someone you met once, the exclamation marks, “shoot over” and “lmk” read as casual about their time, and “super soon” commits to nothing.
Subject line: Recap and next step from our call
Hi Priya, thanks for your time earlier. I will send the proposal deck by Thursday, with the two pricing options we discussed. If anything else would help in the meantime, just let me know.
Why it works: it is still warm, but it fits a new professional relationship and gives a real date instead of “super soon”.
4. The Wall of Text
A single dense paragraph hides the point and the action inside it. People have to mine for what matters, and busy ones do not mine.
Subject line: Updates on everything
Hi team, here is the update from last week: we need to finish the design, write the copy, get approval from management, send the draft to the client, check the data, fix the report, confirm the budget, plan the event, book the venue, and finalize catering, plus reply to John and fix the grammar issues from last time. Let me know what you think. Thanks.
Why it fails: ten tasks in one block, no owners, no dates, so nobody knows what is theirs.
Subject line: This week’s 4 priorities (owners inside)
Hi team, four things to land this week:
- Design draft: Maya, share by Wed
- Client report updated with new numbers: Raj, by Thu
- Budget confirmed: me, by Fri
- Venue booked for the launch: Lena, by Fri
Everything else can wait until next week. Shout if your item is blocked.
Why it works: scannable, one owner and date per line, so each person sees their part in two seconds.
5. The Email With No Clear Ask
An email that ends on “let me know” or “thoughts?” leaves them to guess what you want, so the easy choice is to do nothing.
Subject line: Proposal
Hi Dana, attaching the proposal. Let me know.
Why it fails: no question, no deadline, no next step, so it looks optional.
Subject line: Proposal attached: can you approve the scope by Fri?
Hi Dana, the proposal is attached. The one decision I need from you is whether the scope on page 2 works, or whether to cut the add-on. Could you reply by Friday so we can start Monday?
Why it works: one decision, clearly framed, with a date, so replying is faster than ignoring.
6. Grammar and Spelling Mistakes
The errors that cost you are not cartoon typos. They are the small, plausible mistakes a competent person makes in a hurry: the wrong name, a misplaced decimal, a date that does not match itself, a typo in a link. Each one forces the reader to stop and check.
Subject line: Invoice for March
Hi Jon, thanks for the call. Attached is the invoice for $45.00, due on the 15th. Please confirm by Thursday the 17th. Payment link: alore.io/pay-invioce. Best, Maya
Why it fails: the name is wrong (Jon, not John), $45.00 should read $4,500, the 15th and Thursday the 17th do not line up, and the link is misspelled, so the reader has to query every line.
Subject line: Invoice for March: $4,500, due Mar 17
Hi John, thanks for the call. The March invoice is attached: $4,500, due Thursday, March 17. You can pay here: alore.io/pay-invoice. Tell me if anything looks off. Best, Maya
Why it works: every number, name and date is consistent and checkable, so the reader can act instead of writing back to confirm what you meant.
7. The Wrong or Too Many Recipients
Who is on the email is part of the message. Reply-all to forty people, or CC the whole floor, and you blur who actually needs to act.
Subject line: Can someone handle this?
A question meant for one teammate goes to a 25-person list with “Can someone handle this?” Nobody is named, so everyone assumes someone else will, and no one does.
Why it fails: with no named owner, the message belongs to everyone and therefore to no one.
Subject line: Priya, can you take this?
Email the one person who owns it in the To line, with “Priya, can you take this?”, and CC only the people who genuinely need to see it. If it truly needs the group, name the owner inside the body.
Why it works: a clear recipient is a clear owner, and a clear owner is what gets a reply.
8. The Over-Apologetic Email
Piling on apologies and softeners buries the request, so the reader cannot tell whether you need anything or by when.
Subject line: so sorry to bother you
Hi Nina, so sorry to bother you, I know you are slammed, but I was wondering if you might possibly have a second to glance at this at some point? No rush at all.
Why it fails: five softeners hide the ask, and “no rush” says it can wait forever, so it does.
Subject line: Your pick on the vendor shortlist by Wed?
Hi Nina, could you look at the vendor shortlist (three names, one page) and reply with your pick by Wednesday? If you are slammed, a one-line reply is plenty.
Why it works: one clear ask with a deadline and an easy out, so she knows exactly what you need and when.
Bad Sales and Cold Email Examples (Good vs Bad)
Sales emails fail the same way everyday emails do, with three extra traps. I read cold emails all day, and the ones that get deleted almost always make the same move: they talk about the sender before they give the reader a reason to care. The pairs below are illustrative patterns rather than specific campaigns.
9. The All-About-Us Opener
A cold email that opens with your company, your funding or your feature list asks a stranger to care about you before you have given them anything.
Subject line: Introducing [Company], the leading platform
Hi there, we are the leading all-in-one platform trusted by thousands of businesses to streamline their workflows with AI-powered automation. We’d love to show you a demo.
Why it fails: every sentence is about the sender, and “Hi there” proves it went to a list.
Subject line: a thought on [their team]’s reporting
Hi Maria, I saw [Company] doubled the sales team this year. When teams grow that fast, manual reporting is often the first thing to pile up. If that is happening on your side, it is the problem we help with. Worth a quick look, or is it not a fit right now?
Why it works: it opens on their situation, names one plausible problem without inventing a statistic, and makes the ask easy to decline.
10. The Spray-and-Pray Pitch
If the same email could go to a thousand companies without changing a word, people can tell, and generic gets ignored.
Subject line: Partnership opportunity
Hi, I think there could be great synergy between our companies. We offer best-in-class solutions for businesses like yours. Can we jump on a call this week?
Why it fails: no reason for this company specifically, no proposal, no upside stated.
Subject line: idea for [their product]’s onboarding
Hi Tom, your onboarding emails stop after day three, and that is usually where trials go cold. One fix other teams use is a short nudge sequence across the first week. Happy to share the structure we have seen work, if it is useful.
Why it works: one specific observation about them, one concrete idea, and something offered before anything is asked.
11. The Pushy “Just Bumping This” Follow-Up
A follow-up that adds nothing but pressure feels like nagging. Each one should carry a new reason to reply.
Subject line: Re: Re: following up
Hi, just bumping this to the top of your inbox. Did you get a chance to look? Circling back again since I haven’t heard anything.
Why it fails: it repeats the first email and makes them feel chased rather than helped.
Subject line: Re: idea for [their product]’s onboarding
Hi Tom, one more thought since I wrote: I put the onboarding sequence I mentioned on one page here [link], so you can use it whether or not we talk. If fixing onboarding is a priority this quarter, worth 15 minutes to walk through it?
Why it works: it brings something new, gives value with no strings, and lands on one clear ask with the opt-out left implicit.
12. The Vague Ask That Kills the Deal
Even a well-written sales email dies on a soft close. “Let me know if you’re interested” puts the work on them, so nothing happens.
Subject line: following up on my last note
Hi Dana, just checking in to see if you had any interest in what I sent. Let me know your thoughts whenever.
Why it fails: no specific ask and no next step, so there is nothing easy to say yes to.
Subject line: 15 min on [their goal] next week?
Hi Dana, would a 15-minute call next week work to see if this is a fit? If the timing is off, tell me and I will follow up next quarter.
Why it works: one small, specific ask, with an easy way to say no, so replying takes five seconds.
Good vs Bad Email: The One-Screen Checklist
Run any email past this before you hit send. If the bad column describes yours, fix it first.
| Part of the email | Bad | Good |
|---|---|---|
| Subject line | Vague (“Hello”, “Update”) | States the topic and the ask |
| Opening | About you, or no context | About the reader or the shared context |
| Tone | Demanding, blaming, or too casual | Direct, warm, and specific |
| Body | One dense block | Short paragraphs or bullets, one idea each |
| The ask | “Let me know” | One clear action, with timing when it is real |
| Sign-off | Missing, or abrupt | A sign-off that fits the relationship, with clear sender identity |
| Recipients | Reply-all, everyone CC’d | The one owner in To, only who needs to see it in CC |
| Before sending | Sent on the first draft | Read once for typos, tone and the ask |

What I’ve Learned Reading Bad Emails
I framed this guide around one idea because fifteen years of reading cold emails and sales replies taught it to me the slow way: a bad email asks the reader to do the work the writer should have done. The twelve mistakes above are each one version of that, whether the reader is guessing the topic, hunting for the ask, or working out who owns the next move.
The useful part is what it does to the fix. When an email is not landing, the instinct is to add: more context, more detail, another paragraph of justification. The emails that actually got replies almost always went the other way:
- Cut words until one idea is left.
- Cut asks until one action is left.
- Cut recipients until one owner is left.
The best test I know is to read your email as the busy person receiving it and ask one question: what do they have to figure out that I could have figured out for them? Whatever that is, is the fix.
When Email Is the Wrong Channel
Some messages are bad emails because they should not be emails at all. If the topic is likely to spark ten rounds of back-and-forth, a short live conversation usually settles it faster and with less room to be misread. Before you draft, ask whether a call would cut the ambiguity faster than another email. If so, switch channels deliberately, then confirm the important decisions back in writing. For genuinely sensitive material, pick the channel that keeps it secure, which is not always a call. Email is a strong default for most business communication, but it is not the only tool, and the advantages of email come with limits worth knowing.
Frequently Asked Questions
What is an example of a negative message email?
A negative message is one that sounds blaming or dismissive, like “You failed to finish the task, which is unacceptable.” It puts the reader on the defensive. The same point lands better as “The task is not done yet: what is blocking it, and how can I help?” You can be direct and still be kind.
Which words should I avoid in emails?
Do not blacklist words; no word is bad on its own. “Unfortunately”, “mistake” and “you did not” are all fine when they are accurate and not aimed at the person. What actually hurts an email is blame, vagueness and unnecessary emotional charge. Swap “you failed to send it” for “the file has not come through yet”: same fact, no finger-pointing.
What are common grammar mistakes in business emails?
The grammar ones are mixing tenses, subject-verb disagreement and wrong homophones (their, there, they’re). Separate from grammar, the habits that make an email look rushed are writing in all caps, runaway or missing commas, and sending with no subject line. None changes your meaning much on its own, but together they read as careless. Reading the email once out loud catches most of both.
How do I make sure I’m emailing the right person?
Check the name and the email domain before you send, and make sure the right owner is in the To line rather than buried in CC. For a cold or new contact, confirm you have the person who owns the decision rather than a shared inbox no one checks.
Can an unprofessional email address hurt my reply rate?
Yes, on a first business contact it can cost you trust. An address like partyanimal99@email.com reads as unserious before the message is even opened. Use your name at your company domain, such as jane.smith@company.com, so the sender looks credible from the first glance.
The Bottom Line
Writing a good email is mostly editing a bad one. Use the pairs above as patterns, run the one-screen checklist before you send, and when a message is not landing, cut before you add: fewer words, one ask, the right owner.
For outbound specifically, the writing is only half the job: a clear cold email still has to reach the inbox and get tracked to a reply. That is what Alore is built for, running your outreach sequences, warming up your sending so messages land in the inbox instead of spam, and tracking replies, so a well-written email turns into a conversation.



