Email etiquette is the set of unwritten rules governing professional email communication, and in 2026 those rules are shifting. The fundamentals still hold: write clear subject lines, keep messages concise, reply within 24 hours. But AI has introduced a new layer. A 2025 Superhuman survey found that 72% of professionals now use AI to draft or edit emails (Superhuman, 2025). Recipients increasingly read AI-generated summaries instead of full messages. And tools that extract action items automatically reward structured writing and punish vague, bloated emails more than ever. This guide covers both the timeless principles and the new norms that define professional email etiquette in the AI era.
In this guide
- Subject lines that get opened and parsed
- How to structure the body of a professional email
- Tone: formal, friendly, or somewhere in between
- CC, BCC, and reply all: when to use each
- Response time expectations by role and context
- The etiquette of AI-generated emails
- Writing for AI readers: how to structure emails for extraction
- The 10 most common email etiquette mistakes
- Frequently asked questions
Subject lines that get opened and parsed
The subject line is the most important line in your email. It determines whether the message gets opened, when it gets opened, and how it gets categorized by both humans and AI tools. A Radicati Group study found that professionals receive an average of 126 business emails per day (Radicati, 2024). When someone is scanning 126 subject lines, yours needs to communicate what you need in under 10 words.
A subject line should contain the topic and the action required. "Q3 Budget: approval needed by Friday" tells the recipient what it is about and what they need to do. "Quick question" does neither.
Specific subject lines have a second benefit in 2026: AI email tools use them to categorize and prioritize incoming messages. An AI email sorter reading "Q3 Budget: approval needed by Friday" will correctly flag this as an action item with a deadline. The same AI reading "Quick question" has no signal to work with and may deprioritize the message. Writing for AI parsability is not about gaming a system. It is about writing clearly, which has always been good etiquette.
Do
"Project Atlas: design review feedback due March 15"
"Invoice #4821 attached: net 30 terms"
"Meeting reschedule: Tuesday 2pm → Thursday 10am"
Don't
"Quick question"
"Following up"
"Hey"
Change the subject line when the topic changes. Long email threads drift. A thread that started as "Q1 Marketing Plan" may eventually discuss budget approvals, vendor contracts, and team assignments. When the conversation shifts, update the subject line to match. This helps everyone find the message later, helps AI tools extract the right action items, and prevents important decisions from being buried in a thread nobody reads past the third reply.
Use prefixes for urgency and type when appropriate. Prefixes like [ACTION], [FYI], [URGENT], or [EOM] (end of message, meaning the entire message is in the subject line) are common in fast-paced teams and particularly useful in enterprise environments. They function as human-readable metadata. An email with the subject "[ACTION] Approve vendor contract by EOD" communicates urgency, type, and deadline before the recipient opens it. Use these when your team or industry expects them. Avoid them in external communication where they can feel abrupt.
How to structure the body of a professional email
The first two sentences of your email are the most important. Research from the Nielsen Norman Group shows that people read emails in an F-pattern: they read the first line fully, scan the second, and skim the rest (Nielsen Norman Group, 2020). If your request is buried in the third paragraph, most recipients will not reach it. AI summarization tools face the same constraint in reverse: they weigh opening sentences more heavily when generating summaries. The daily briefing your recipient reads may be based on your first two sentences.
Lead with the ask or the key information. Context and background come after, not before. If someone stopped reading after two sentences, they should still know what you need from them.
The inverted pyramid structure: Journalism has used this for a century and it works perfectly for email. Start with the conclusion or request. Follow with the essential supporting details. End with background and context that the reader can skip if they already understand. This structure respects the recipient's time and works with how both humans and AI actually process messages.
Keep it short
Boomerang analyzed over 40 million emails and found that messages between 50 and 125 words had the highest response rates, above 50% (Boomerang, 2016). Longer emails saw declining response rates. The Harvard Business Review reported similar findings: emails written at a third-grade reading level received 36% more responses than those written at a college level (HBR, 2016). Simplicity and brevity are not just polite. They are measurably more effective.
A good target for most professional emails is 75 to 150 words. If your email exceeds 300 words, consider whether it should be a document with the email serving as a cover note. "I've attached the full proposal. The key decision points are X, Y, and Z. Can we discuss Thursday?" is almost always better than pasting a 500-word proposal into the email body.
Use formatting to aid scanning
When an email must be longer, structure it so the reader can scan without reading every word:
- Bullet points for lists of items, options, or updates
- Bold text for deadlines, names, or key decisions
- Numbered lists when you need responses to specific questions (recipients can reply with "1. Yes, 2. Friday, 3. Approved")
- Paragraph breaks between distinct topics rather than one wall of text
Formatting is also how you write emails that AI tools can process accurately. An email that says "we need the designs by Friday and the budget by next Wednesday and please confirm the vendor" buries three action items in one sentence. The same information as a numbered list produces three clearly extracted tasks with individual deadlines.
Tone: formal, friendly, or somewhere in between
Email tone has shifted significantly over the past decade. The stiff formality of "Dear Sir/Madam, I am writing to inform you that..." has given way to a more conversational style in most industries. But "conversational" does not mean "casual." The right tone sits between corporate formality and Slack-chat informality, adjusted for context.
Match the relationship. A first email to a new client should be more formal than an email to a colleague you have worked with for three years. When in doubt, start slightly more formal and let the other person set the tone. If they sign off with "Cheers," you can too. If they use "Best regards," match it. This is called tone matching, and it is one of the subtlest but most important aspects of email etiquette.
The greeting. "Hi [Name]" is the safe default for most professional contexts in 2026. "Dear [Name]" signals formality and is appropriate for first contact, executive communication, or industries like law and finance. "Hey [Name]" is fine for colleagues you work with daily. No greeting at all is acceptable in rapid back-and-forth exchanges within an existing thread.
The sign-off. "Best" and "Thanks" are the two most common professional sign-offs and both are safe in nearly every context. "Regards" and "Best regards" lean formal. "Cheers" is warm but may read as too casual for some industries. Avoid "Sent from my iPhone" as your only sign-off; it signals that the email was not worth the effort of a proper close.
Exclamation points. One per email is fine. Two is the maximum. Zero is safest when delivering bad news, making formal requests, or writing to someone you do not know well. A study by Binghamton University found that text messages ending with a period were perceived as less sincere (Binghamton University, 2016), and the same dynamic plays out in email. A well-placed exclamation point communicates warmth. Overuse communicates either insincerity or anxiety.
CC, BCC, and reply all: when to use each
Misuse of CC and reply all is one of the top complaints in every workplace email survey. A McKinsey study found that the average professional spends 28% of their workweek on email (McKinsey, 2023), and a meaningful portion of that time is spent reading CC messages that do not require their input. Every unnecessary CC adds cognitive load to someone's inbox.
CC someone when they need awareness but not action. If you are adding someone to CC, ask: "Would this person be confused or disadvantaged if they did not see this email?" If the answer is no, do not CC them.
BCC has two legitimate uses: sending to a large distribution list where recipients should not see each other's addresses (event invitations, announcements), and removing yourself from a thread by BCCing yourself on a handoff email ("I'm looping in Sarah who will take this from here; moving myself to BCC"). Using BCC to secretly monitor a conversation is poor etiquette and a trust violation if discovered.
Reply all should be the exception, not the default. Before hitting reply all, ask: "Does everyone on this thread need to see my response?" If your reply is a "Thanks!" or "Got it," the entire group does not need that notification. Reply to the sender only. Reserve reply all for responses that contain information or decisions that affect every recipient.
The CC-as-pressure tactic. CCing someone's manager to escalate or apply pressure is one of the most aggressive moves in workplace email. Sometimes it is necessary. Most of the time it damages relationships. If you need to escalate, do it explicitly: "I'm bringing [Manager] into this conversation because we need a decision on [specific issue]." This is transparent and professional. Silently adding a manager to CC and hoping the recipient notices is passive-aggressive and widely recognized as such.
Response time expectations by role and context
Response time is one of the most anxiety-producing aspects of email. How quickly should you reply? The data is clear: a study analyzing over 2 million emails found that the median response time is 2.5 hours, with 90% of replies that will ever come arriving within 48 hours (USC Viterbi, 2015). After 48 hours, the probability of a response drops sharply.
But expectations vary dramatically by role and context:
- Sales and customer-facing: Speed matters. InsideSales.com research showed that responding to a lead within 5 minutes makes you 21x more likely to qualify them (InsideSales, 2014). For client emails, 2 to 4 hours is the benchmark.
- Internal/cross-team: 24 business hours is the standard expectation. Same-day replies are appreciated but not expected for non-urgent matters.
- Executive communication: Executives receive the most email and have the least time. A concise reply within 24 hours is expected. If you send an executive a 500-word email requiring a complex decision, do not expect a fast reply, or any reply. Shorten the email.
- External/vendor: 24 to 48 hours is reasonable. If a vendor or partner has not replied in 48 hours, a polite follow-up is appropriate.
If you cannot provide a full answer within the expected window, send a brief acknowledgment: "Got your email; I'll have a full answer by Thursday." This takes 15 seconds and eliminates the uncertainty that causes follow-up emails, which create more work for both parties.
AI tools are changing this dynamic in an interesting way. When your recipient uses an AI email tool that extracts action items and deadlines, your email gets processed the moment it arrives, even if the human does not read it for hours. The recipient may see "Action item: approve vendor contract (deadline: Friday)" in their daily briefing and act on it without ever opening your full email. This means that clear, structured emails with explicit deadlines are more likely to get timely action, even from slow responders, because the AI does the triage that the human did not.
The etiquette of AI-generated emails
AI-drafted email is no longer novel. It is the norm. A 2025 survey found that 72% of professionals use AI to help write emails (Superhuman, 2025), and the number is higher among younger professionals. The etiquette question is not whether to use AI but how to use it well.
The rules for AI-drafted emails
- Always review before sending. AI drafts are first drafts. They get facts wrong, hallucinate details, and default to verbose, hedging language. Read the draft as if someone else wrote it. Edit for accuracy, tone, and brevity. The social contract of email is that the sender takes responsibility for the content. "My AI wrote that" is not an acceptable excuse for an incorrect statement.
- Remove the filler. AI models are trained on internet text that is full of pleasantries: "I hope this email finds you well," "Just wanted to circle back," "Please don't hesitate to reach out." These phrases add words without adding meaning. Delete them. Your recipient will thank you for respecting their time.
- Preserve your voice. If every email you send sounds like it was written by the same AI, colleagues will notice. Use AI for structure and speed, but inject your own phrasing, especially in high-stakes messages. The emails that build relationships are the ones that sound like they came from a person, not a model.
- Disclose when appropriate. In most contexts, disclosure is not required. You do not announce that you used spell check or Grammarly. But in sensitive situations (legal communications, formal complaints, executive briefings) there is an emerging norm of transparency about AI involvement. If in doubt, err on the side of disclosure.
When AI-generated replies are obvious
Recipients can often tell when a reply is AI-generated. The telltale signs: overly formal language that does not match the sender's usual tone, responses that are longer than the question warranted, generic phrases, and a tendency to repeat the original question back before answering. These are not just style issues; they signal to the recipient that their email was not worth a personal response, which undermines the relationship.
The fix is simple: edit the draft to sound like you. Cut the length in half. Remove the preamble. Add one sentence that only you would write: a reference to a shared project, a specific data point, a direct opinion. The AI saved you 80% of the work. Spend the other 20% making it yours.
Writing for AI readers: how to structure emails for extraction
Here is a shift most people have not considered: your emails are increasingly read by AI before they are read by humans. Recipients who use tools like Unboxd, Shortwave, or Superhuman see AI-generated summaries, extracted action items, and priority labels before they see your actual email. The way you write directly affects how accurately the AI represents your message.
This is not about gaming AI. It is about clear communication. The same practices that help AI extract accurate action items also help humans understand your email faster.
- State deadlines explicitly. "Please review by Friday, April 11" is extracted perfectly by AI. "When you get a chance" is not a deadline and will not be flagged as one.
- One email, one topic. Emails covering three unrelated topics get poorly summarized by AI and poorly processed by humans. If you have three topics, send three emails (or use numbered sections with clear headers).
- Name the action. "Can you approve the Q3 budget?" is an extractable action item. "Thoughts?" is not. Be specific about what you need the recipient to do.
- Use numbers and specifics. "The project is $12,000 over budget" gets extracted and highlighted. "The project is a bit over budget" does not. Specifics are more useful to both AI and humans.
- Put the most important information first. AI summarizers weigh the first paragraph more heavily. If your critical ask is in the fourth paragraph, the summary may not include it.
Writing for AI readers and writing for human readers are the same skill. Both reward clarity, brevity, and structure. The difference is that in 2026, poor email writing has a new consequence: not only might the human miss your point, the AI might misrepresent it.
The 10 most common email etiquette mistakes
These are the mistakes that appear most frequently in professional email, ranked by how much damage they do to communication and relationships.
- Burying the request. If your call to action is in the last paragraph, most people will never see it. Lead with what you need.
- Reply all abuse. "Thanks!" to 30 people is 30 unnecessary notifications. Reply to the sender only unless everyone needs the information.
- Vague subject lines. "Follow up" and "Quick question" tell the recipient nothing. Include the topic and action required.
- Writing too much. Most emails should be under 150 words. If you have written 400 words, edit or convert the content into an attached document.
- Sending angry or emotional emails. The "wait 24 hours" rule exists for a reason. Emails written in frustration are almost always regretted. Draft it if you must, but do not hit send until the emotion has passed.
- Using CC as a weapon. Adding someone's manager to CC without explanation is widely recognized as passive-aggressive. Escalate explicitly or not at all.
- No response when one is expected. Even a one-line acknowledgment ("Got it, will review by Thursday") is better than silence. Silence creates uncertainty and generates follow-up emails that waste everyone's time.
- Sending unedited AI drafts. Recipients can tell, and it communicates that their email was not worth personal attention. Always review and edit AI-generated content.
- Replying to the wrong thread. In fast-moving email conversations, replying to an old message instead of the latest can create confusion. Check that you are responding to the most recent message in the thread.
- Forgetting the attachment. "Please see attached" with no attachment is the most common email mistake and has been for decades. Most email clients now warn you, but double-check before sending. If you do forget, resend immediately with a brief note rather than sending a separate "oops" email.
Putting it all together
Email etiquette is not about rigid rules. It is about communication that respects the recipient's time and attention. In 2026, that means writing emails that work for both human readers and the AI tools that increasingly process them first. The principles are the same as they have always been (clarity, brevity, structure, and courtesy) but the consequences of ignoring them are more visible than ever.
When you write a clear subject line, your email gets categorized correctly by AI and opened faster by humans. When you lead with your request, AI extracts the right action item and the human knows what you need in 10 seconds. When you include an explicit deadline, both the person and their AI track it as a commitment. Good etiquette and good writing have always been the same thing. AI just made it measurable.
For a broader look at how email etiquette fits into a complete productivity system, see the Complete Guide to Email Management. If you are spending more time on email than you should be, the email triage method can help you process your inbox in 15 minutes.
Key Takeaway
- Write subject lines with the topic and action required; AI tools and humans both use them for prioritization
- Lead with your request in the first two sentences; context and background come after
- Keep emails under 150 words when possible: 50-125 words get the highest response rates
- Respond within 24 hours; if you need more time, send a 15-second acknowledgment
- CC means awareness, not action; ask "would they be disadvantaged without this?" before adding someone
- AI-drafted emails are now normal, but always review for accuracy, tone, and brevity before sending
- Write with explicit deadlines, one topic per email, and specific action requests; your emails are now read by AI before humans
- The 10 most common mistakes are all preventable with one principle: respect the recipient's time
Frequently asked questions
What are the basic rules of professional email etiquette?
The core rules are: write a specific, actionable subject line; lead with the request or key information in the first two sentences; use CC only for people who need awareness and BCC for large distribution lists; keep emails under 150 words when possible; respond within 24 hours on business days (even if only to acknowledge receipt); and proofread before sending. These fundamentals have not changed with AI; they have become more important because AI tools parse emails for action items and urgency, rewarding clear, structured writing.
Is it rude to use AI to write emails?
No. A 2025 Superhuman survey found that 72% of professionals already use AI to draft or edit emails. Using AI to write email is now as normal as using spell check. What matters is the result: a clear, accurate message that respects the recipient's time. The etiquette concern is not whether you used AI, but whether you reviewed the output. Sending an obviously generic AI draft without editing, especially one that gets facts wrong or uses filler phrases like "I hope this email finds you well," is the new rudeness.
How quickly should I respond to a professional email?
The general expectation is a response within 24 business hours. For urgent matters or client-facing roles, 4 hours is the benchmark. If you cannot provide a full answer within that window, send a brief acknowledgment: "Got it; I will have a full answer by Thursday." This takes 15 seconds and prevents the sender from wondering whether their email was received. Research shows that 90% of replies that will ever come arrive within 48 hours. After 48 hours with no response, most senders assume the email was missed.
When should I use CC vs BCC in emails?
Use CC when someone needs awareness of a conversation but is not expected to respond, for example, keeping a manager informed of a client decision. Use BCC when sending to a large group where recipients should not see each other's addresses, such as event invitations or company-wide announcements. Never use CC to apply social pressure. The rule of thumb: if you are adding someone to CC to "cover yourself," reconsider whether that is productive communication or office politics.

