Bad Email Etiquette: The Mistakes That Matter (and the Ones That Don't)

This guide sorts the two. It covers what counts as poor email etiquette, the habits that cost you and how to fix each one, the folklore you can stop worrying about, how the right call changes with who you are writing to, and what the research says the real cost is. The fixes come from writing and tracking business email at volume, where the only test that matters is whether the other person replies.

What Counts as Bad Email Etiquette

Bad email etiquette is any habit that makes your message harder to read, act on, or trust than it needed to be. In practice it shows up as unclear requests, messy threads, the wrong recipients, sloppy formatting, or a tone that lands colder or pushier than you meant.

It is worth separating two kinds. The first kind changes outcomes: the reader cannot tell what you want, replies slowly or not at all, or comes away slightly annoyed. The second kind is cosmetic: choices a strict colleague might frown at that have little bearing on whether your email works. Most advice treats both as equally serious. They are not, and knowing which is which saves you a lot of second-guessing before you hit send.

The Habits That Cost You

These are the ones worth fixing first, because each makes the reader work harder or trust you a little less. For each, here is the mistake and how to fix it, with a before and after where a rewrite makes the point.

A Subject Line That Says Nothing

A subject line like “Quick question” or “Update” gives the reader nothing to triage on, so your email sinks in a busy inbox. Name the topic, the request, and the deadline in a few words. Keep it short enough to survive a phone’s preview, which often cuts off after the first few words.

What changed: the reader can see the topic, the scope, and the deadline before opening, and knows what “this” means.

No Clear Ask

An email that reads like a status update but secretly wants action leaves the recipient unsure what to do, so they do nothing. Put the request in the first two lines, and if there is more than one, number them. The same one-ask discipline is what makes a good meeting request email land.

What changed: the ask moved to the top, the choice is limited, and the deadline is visible, so the email is answerable in one reply.

A Passive-Aggressive Reply

“As I already said twice, this was due yesterday” feels satisfying to send and expensive to clean up. State the fact, drop the blame, and give the person a face-saving way out.

What changed: the blame is gone, there is a clear next step and a deadline, and the question surfaces a blocker instead of picking a fight.

Reply-All That Adds Nothing

A “Thanks!” sent to forty people teaches all forty to ignore the next group thread. Reply to the one person who needs it, or do not reply at all. Reserve reply-all for when every recipient genuinely needs your message.

A New Thread With No Context

Starting a fresh email that says only “Any update?” forces the reader to reconstruct which request you mean. Stay in the original thread so the history travels with the question, and add a one-line recap if you must start fresh.

What changed: the old context stays attached, and the question is specific and dated.

CC as a Pressure Tactic

Copying someone’s manager to force a faster answer reads as political even when your request is fair, and it spends goodwill you may want later. Write to the owner first with a reason and a deadline. Keep escalation in reserve rather than opening with it.

A Wall of Text

An update with four decisions buried in one unbroken paragraph makes the recipient hunt for the sentence that matters. Break it into the decisions needed, what is already done, and the deadline, so it can be skimmed on a phone.

What changed: the action items come first, the context second, and the reader sees what they own at a glance.

Chasing Too Soon

Three nudges in one morning create urgency for you while giving the recipient nothing new to act on, and they make your real deadlines harder to believe. Wait a sensible interval, then send one clean follow-up with a new reason or an easy next step. If something is genuinely urgent, change channels instead of stacking emails.

The Folklore You Can Mostly Ignore

These are the habits etiquette lists love to police, though in practice they rarely decide whether you get a reply. None of them is a hard rule. Each is a judgment call that depends on who you are writing to, and is seldom what makes or breaks your email.

• Emojis. Fine with people you know and in a relaxed culture; riskier in a first email to a formal recipient. A 2017 study of first-contact work emails (Glikson and colleagues, in Social Psychological and Personality Science) found that smileys did not raise perceived warmth and slightly lowered perceived competence, so they suit a warm relationship better than a cold open. The emoji is rarely the real problem; an unclear message with an emoji is.
• Exclamation marks. One warm exclamation mark reads as friendly. Five read as frantic. The count matters more than the character.
• Numbers in your address or a slightly informal handle. A clean name-based work address helps, but someone deciding whether to reply is reacting to your message rather than studying your email string.
• A one-word “Thanks” to close. In a fast internal thread this reads as efficient rather than rude. On a first contact it can feel thin, so add a line and a proper sign-off there.
• A formal greeting every single time. First contact and high-stakes messages earn “Hi [Name],” a quick back-and-forth inside a live thread does not need a fresh salutation each round.

The test for anything on this list is simple: would changing it make the message clearer or easier to act on? If not, it is taste, and you can spend your attention on the section above instead.

Etiquette Changes With Who You're Writing To

The same habit lands differently depending on the relationship, so match the fix to the reader. Treat the table below as a starting point you adapt.

A cold outreach email and a note to a colleague you speak to daily are held to different standards. Writing as if every email were a formal letter wastes effort; writing to a client as if they were your desk neighbor costs trust. The skill is reading the relationship and matching it.

What Poor Etiquette Costs You

The honest answer is that most of the cost is friction rather than catastrophe. A single clumsy email rarely ends a deal. The cost is cumulative: slower replies, more back-and-forth, and a slow erosion of how easy you are to work with.

Two findings put numbers on the backdrop. A 2024 study in Frontiers in Psychology found that higher email load predicted a later increase in strain, even after accounting for time pressure and interruptions, and that the main driver of that load was the volume of communication emails people received. Your email lands in that pile. A large 2015 study of more than two million users and sixteen billion emails found that the more email people receive, the smaller the share they answer, and the shorter their replies get. In other words, attention is the scarce resource, and an email that is hard to read or act on is the first to be skipped.

Those are the real stakes of etiquette: not adding to the pile of work the reader is already behind on.

Etiquette When You're Sending at Scale

Everything above assumes you are writing to one person. The moment you send to a list, the etiquette changes, and the mistakes get more expensive because they repeat across hundreds of inboxes.

A few rules hold at scale. Send to people who have a plausible reason to hear from you, rather than every address you could find. Make the unsubscribe or opt-out obvious, because hiding it earns spam complaints that damage your ability to reach anyone. Personalize beyond a first name, since “Hi [First Name]” on a generic blast fools no one. Resist the urge to over-follow-up: a sequence that adds a fresh reason each time is persistence, while the same nudge sent five times is noise.

On follow-up timing specifically, our own approach across outbound campaigns is a spaced cadence of three to five touches over roughly a month, with every message carrying something new instead of repeating the ask. The point is the same as with a single email: respect the reader’s attention, and stop when you no longer have a fresh reason to write. When you are running this across a whole list, the hard part is the coordination, which is what an outbound engine like Alore is built to handle. For the mechanics of a graceful final message, see our guide on what to send when you haven’t heard back.

The 10-Second Pre-Send Check

Before you hit send, run these five checks. They catch most of the mistakes in the first section in the time it takes to reread the top of your email.

1. Subject: does it name the topic and the ask, so the reader can triage without opening?
2. The ask: is the one thing you want in the first two lines, and is it a single, clear request?
3. The recipient: is this the right person, and does everyone on CC need to see it?
4. The scan: can the reader find what matters in one pass, or is it a wall of text?
5. The tone: if you are annoyed, has the blame come out of the reply?

If all five pass, send it. If you are stuck on the wording of a tricky one, our side-by-side good and bad email examples show the fixes in full.

Frequently Asked Questions

What are examples of bad email etiquette?

The ones that cost you are a vague subject line, no clear ask, a passive-aggressive reply, needless reply-all, starting a new thread with no context, copying people to apply pressure, a wall of text, and chasing too soon. Each makes the reader work harder than they should have to.

What is the 5 email rule?

It usually refers to the five-sentence rule: keep an email to about five sentences or fewer, treating it like a text message so the reader can act fast. The idea was popularized by Mike Davidson’s “five sentences” convention. Some people use “the 5-minute rule” instead: if a message would take more than five minutes to write or read, have a call.

What are the basic rules of email etiquette?

Three carry most of the weight: write a clear subject, make one clear ask near the top, and match your tone to the reader. Add to those a correct recipient list, a scannable layout, and a reply speed that fits the context, and you have covered what affects whether your email works.

How quickly should I respond to emails?

Match the reply to the sender and the stakes; there is no fixed clock that fits every message. Routine internal email can wait hours; a client or a time-sensitive thread deserves a same-day reply, even if it is only a line to say when a full answer will come. The faster signal is an acknowledgment, sent even before the full answer.

Are emojis or exclamation marks unprofessional?

Not by themselves. Both are fine with people you know and in a relaxed culture, and risky in a formal first contact. One exclamation mark reads as warm; several read as frantic. Judge it by the relationship rather than a blanket ban.

The One Rule Behind All of Them

Every habit in this guide reduces to a single question: have you made the recipient’s job easier or harder? Good email etiquette is the habit of doing the small work (a clear subject, one ask, the right recipients, a steady tone) so the person on the other side does not have to.

If you are sending at any volume, the discipline is the same email after email, which is where it gets hard to hold. That coordination, who is due for a follow-up, what you said last, and when to stop, is what an outbound engine like Alore is built to carry, so the judgment you apply to one email holds up across a whole list.