# Examples of Email Etiquette: What to Write, and When Canonical URL: https://headwayskills.com/knowledge/communication/examples-of-email-etiquette/ Markdown URL: https://headwayskills.com/knowledge/communication/examples-of-email-etiquette.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer See examples of email etiquette for work: how formal to start, what makes a subject line work, when to use reply all or bcc, and how fast to reply. ## Key facts - Title: Examples of Email Etiquette: What to Write, and When - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Time Management - Primary keyword: examples of email etiquette - Source page: https://headwayskills.com/knowledge/communication/examples-of-email-etiquette/ ## What this page covers - See examples of email etiquette for work: how formal to start, what makes a subject line work, when to use reply all or bcc, and how fast to reply. - Practical guidance for examples of email etiquette - How this topic connects to Communication ## Detailed explanation You have a message half-written to someone senior, and you are stuck on the first line — [too formal](/knowledge/communication/business-formal-email/) reads stiff, too casual reads careless. Email etiquette is the set of conventions that make a work message easy to read and answer: a subject line that states the topic, a greeting matched to how well you know the recipient, the main point up front, only the people who need to be on it, and a reply within a day. Those conventions are settled and uncontroversial. What is harder is knowing which version of them applies to the specific message open in front of you right now, so the answers below work through those situations one at a time. ## What do good examples of email etiquette look like? The published rule lists are long — Indeed runs 28 rules, HubSpot 27, Sprout 25 — but they all converge on the same five parts: a subject line, a greeting, the body, a sign-off, and a proofread before you send. Seeing them assembled is more useful than reading them as separate rules. Here is an ordinary one — a request to a colleague you work with regularly: > **Subject:** Approval needed on the March invoice draft, by Thursday > > Hi Amara, > > Could you review and approve the attached March invoice draft? Finance closes the month on Friday, so Thursday is the last day it can go in. > > I've flagged the two lines that changed since February. Everything else is as it was. > > Thanks, > Peter Nothing in it is clever. The subject line says what is needed and by when. The request is in the first sentence rather than three paragraphs down. The deadline comes with its reason, so it doesn't read as arbitrary. Then it stops. That last part matters more than people expect: Amara can deal with this in about ten seconds, and saving her the other ninety is the actual courtesy. ## How do I start an email when I don't know how formal to be? Use "Hi [First Name]," as your default. It comes up repeatedly across Indeed, Sprout, and Grammarly as the safe register when you are unsure — warm enough not to read as cold, professional enough not to read as presumptuous. Save "Dear [Full Name]," for [genuine first contact](/knowledge/communication/email-introduction-examples/), where the formality signals that you know you are a stranger. Keep "Hey" for your immediate team, and only after you have seen them use it first. Two adjustments are worth making. If you are writing to a professor, university writing centers — Miami University's Howe Center and Messiah University among them — advise using their title and last name unless you have been told otherwise, and putting the identifying detail in your first line: course, section, assignment. Your name alone means very little to someone teaching two hundred people. And do not skip the greeting to save time. Opening straight into the request reads as impatient, and it is the cheapest three words in the whole message. ## What makes a subject line work, and what makes one useless? A subject line is a preview, not a label. Grammarly puts the difference more clearly than anyone: "Question about Q3 budget timeline" tells the recipient what is coming and lets them decide when to open it. "Question" gives them nothing. The failure here is not rudeness — a vague subject line is perfectly polite. It is that the work gets transferred. The recipient has to open the message to find out whether it is urgent, and if they are triaging forty messages, yours gets sorted by guesswork. So name the specific thing, and if there is a deadline or a decision in the message, put it in the subject line too. "Contract approval needed by Friday 5 PM" has done half the email's job before anyone opens it. ## How do I end an email without sounding abrupt? Close with the next step, then sign off. If you need something, name the date: a plain "Could you let me know by Wednesday?" prevents a second email later. If you need nothing, "Thanks" or "Best regards" is sufficient — nobody has ever been marked down for "Best regards." The sign-off's other job is identification. A signature with your full name, your role, and a way to reach you means the recipient never has to work out who you are. Early in a job, when few people can place your name yet, that does more for you than any amount of careful phrasing. ## When do I use reply all, cc, and bcc? HubSpot offers the test that settles most of these: treat the email like a meeting, and ask whether it would be necessary or helpful to have that person in the room. If the answer is no, do not spend their time. Reply all is for replies that are genuinely relevant to everyone on the thread. The canonical failure is a one-word "Thanks" sent to twenty people. Sources on this topic treat it as a reputation problem rather than a nuisance — being the person who always replies all reads as thoughtless and rushed, and it happens in front of everyone senior on the thread. Cc is for people who need to know, not people who need to act. Anyone in the To line should have something to do. Bcc has one clean use: mailing a group of people who don't know each other, so their addresses stay private. Using it to quietly copy a manager into a thread is riskier than it looks — if the bcc'd person replies all, everyone finds out they were there. ## How fast do I have to reply, and how do I follow up when nobody answers? Within 24 hours is the norm these guides converge on, and it comes with a technique worth taking: when you cannot answer properly yet, send a short acknowledgment saying when the full reply is coming. It closes the loop for the sender at almost no cost to you, and it clears the low-level guilt of a message sitting unanswered in your inbox. For follow-ups, wait two to three working days, then reply inside the same thread rather than starting a new one, and keep it to two sentences: what you need, and the date it matters by. Do not open with an apology for following up. A single factual nudge is ordinary professional behavior, not an imposition. If two follow-ups go unanswered, the problem is the medium rather than your wording — which is the last question below. ## Which email mistakes make you look unprofessional? The costly ones are about tone, not grammar. ALL CAPS reads as shouting. Stacked exclamation points or question marks read as emotionally reactive. Sending anything written [while you are angry](/knowledge/self-awareness/handle-criticism/) outlives the rest, because it stays in writing and can be forwarded. Below those sit the quieter ones: vague subject lines, cc'ing people who don't need it, and not proofreading — misspelling the recipient's name is the one they always notice. What links them is that email carries no facial correction. In a conversation you can see a remark land badly and repair it in the same breath. In writing, whatever tone the reader decides you had is the tone you had. Most of these habits form quietly, because nobody writes back to tell you your last message came across as curt — which is why it is worth [checking your blind spots](https://assessment.headwayskills.com/) occasionally instead of waiting for feedback that never arrives. They are habits, not character, and habits can be rewritten. ## When should you not send an email at all? Almost every guide on this subject assumes the email is being written and sets out to improve it. But choosing the wrong medium is an etiquette failure that no subject line repairs. Writing is the right choice when the other person needs time to think, when the exchange needs to be on record, or when the message is one-way information. A conversation is the better choice for anything sensitive, anything complex, anything involving negotiation or disagreement, and anything where you are trying to build trust rather than transmit facts. The practical tell: if you are rereading a draft to check whether it sounds harsh, the draft is telling you [it should be a conversation](/knowledge/communication/difficult-conversations-at-work/). ## The skills underneath these decisions Look back at those answers and notice how few of them were about wording. How formal to be, who needs to be on the thread, how long to wait, whether to write at all — each one was a judgment call. That is why collecting examples only takes you so far; the examples are the output of judgment you develop somewhere else. **Communication** is where most of it lives. Leading with your main message, writing a subject line someone can act on, keeping only the recipients who need to be there, replying in reasonable time — and, before any of that, choosing whether this belongs in writing at all. That last decision is the one people skip, and the one that decides whether the email was ever going to work. **Professional Behaviors** covers the layer email preserves. Politeness, punctuality, discretion with confidential material, and speaking about colleagues as though they were present — email records all of it and forwards it without asking you first. It also holds the behaviors that read worst in writing: passive, aggressive, and negative all land harder on a screen than they do in a room. **Time Management** is the half of etiquette that is about other people's attention. Every unnecessary cc, every subject line that forces someone to open the message, every thread that runs on past its purpose spends time that isn't yours. It works in the other direction too: processing your inbox in set sessions rather than continuously, and agreeing when a reply is actually needed instead of accepting "ASAP," turns response time into something you plan rather than something you worry about. Email is one of the few places where all three of these show up in the same three-line message, which is why it exposes whichever one is weakest. If you would rather build the one that will make the most difference than work on all three at once, the free Work Skills Test [ranks all twelve for you](https://assessment.headwayskills.com/) — these three included, **none of them a fixed trait**. ## What this says about how you already work Some of this probably describes emails you have already been sending — you may find you have been getting the subject lines right and hesitating over the greetings, or the reverse. That mix is normal, and the parts you have not learned are just that — not yet learned. Consider also what you did before sending: you looked up the convention rather than guessing at it. Most people skip that step. Nothing here asks you to write in someone else's voice — the conventions handle the frame, and the voice stays yours. Where it starts to compound is later. The further into a career you get, the more people first encounter your thinking as an email rather than as you in a room, and written habits that were harmless at twenty-two get read very differently at thirty. Which makes an honest look at your current starting point worth the few minutes it takes. ## Before your next send The conventions are settled; what is left is knowing which of the skills beneath them is yours to build. The Work Skills Test is a **free** self-assessment of all twelve work skills — communication, professional behaviors, and time management among them — and it takes about seven minutes of honest answers. You come away knowing whether your real gap is the writing, the register, or the judgment about when to write in the first place, and which strength you can already lean on while you close it. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, about 7 minutes, and no preparation needed.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? See examples of email etiquette for work: how formal to start, what makes a subject line work, when to use reply all or bcc, and how fast to reply. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Professional Behaviors, Time Management. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/time-management.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/examples-of-email-etiquette/ Preferred summary: "See examples of email etiquette for work: how formal to start, what makes a subject line work, when to use reply all or bcc, and how fast to reply." ## Change log - 2026-07-07: Content collection version published.