Email Etiquette: 20 Rules for Professional Emails (With Examples)
Good email etiquette means writing so the reader can act without a follow-up: a specific subject line, the request in the first lines, a polite and neutral tone, the right people on the thread, and a reply within a reasonable time. The 20 rules below cover each point with an example, plus a send-or-wait checklist.
The short answer
Professional email etiquette comes down to respect for the reader's time and attention. Put the point first, address the right people, keep the tone courteous, check before you send, and answer within the time your workplace expects. The 20 rules below are grouped by what you are doing: setting up the message, writing it, handling the thread, and knowing when not to use email at all.
These are widely shared habits, not laws. Employers, industries and countries differ, so when your company has its own email policy or style guide, follow that first.
Part 1: Set up the message
1. Write a subject line that says what the email is about
A subject line is the first thing a busy reader sees. Make it specific, and include a date or action if one applies.
- Vague: "Question"
- Better: "Question about invoice 4821, due 14 November"
- Better: "Action needed by Friday: approve Q1 travel budget"
For more patterns, see our guide to email subject lines.
2. Use a professional sender name and address
Your display name should be your real name, not a nickname or a joke. A work address is better for work, and a plain personal address (name and surname) is fine for job applications. Avoid addresses that read as informal or confusing in a professional setting.
3. Choose To, CC and BCC deliberately
Put people who must act in To. Put people who need to be informed in CC. Use BCC to protect addresses when writing to people who do not know each other. Do not use BCC to secretly copy someone on a sensitive exchange. Full detail is in CC vs BCC.
4. Add recipients last
Write the message first and type addresses at the end. This stops a half-finished draft from going out if you press Send by accident.
5. Use a greeting that fits the relationship
Match the reader and the context. "Dear Dr Alvarez," suits a first message to a senior contact or an academic. "Hi Sam," suits a colleague you know. "Hello team," suits a group. If you are unsure, start more formal; the other person's reply will show you the register. For an unknown contact, our guide on how to start an email shows options, and To Whom It May Concern explains when that phrase is still acceptable.
Part 2: Write the message
6. Put the point in the first two lines
State why you are writing before the background. Compare these two openings.
Before: I hope this finds you well. I was looking at our schedule last week and noticed a few things, and then I spoke to Lena, and so I wanted to ask whether you might possibly have time.
After: Could we move Thursday's review to Friday at 10:00? Lena has a client call on Thursday, and the report will be ready by Thursday evening.
The second version can be answered in one line.
7. Keep it short and use plain language
Most emails need three to five short paragraphs at most. Use ordinary words instead of corporate filler. "Please find attached" is understood, but "I have attached the report" is clearer and warmer.
8. One email, one main topic
If you must raise two unrelated matters, send two emails, so each can be answered, forwarded and filed on its own. If you do combine them, number the questions.
9. Make the request and deadline explicit
Say what you want, by when, and from whom. "Could you send the signed form by Wednesday 5 pm?" works better than "Let me know soon."
10. Format for scanning
Use short paragraphs, a blank line between them, and a list for three or more items. Bold a single key date if it helps, but avoid large blocks of capitals, many colours or lines of exclamation marks.
11. Watch your tone
Text has no facial expression. A line that sounds neutral to you can read as cold or irritated. Compare:
- Sounds sharp: "As I already said, the file was sent on Monday."
- Sounds neutral: "The file went out on Monday; I have attached it again in case it was missed."
Be careful with capitals ("PLEASE READ"), single-word replies ("No."), and sarcasm. If a message sounds sharper than you intended, paste it into the Tone Changer and choose the Formal, Office or Casual mode to see a softer or more formal version. The result is machine-generated, so read it and keep your own meaning.
12. Use humour, emoji and abbreviations sparingly
A single smile in a friendly reply to a colleague is usually fine. In a first message to a client or a senior leader, leave out emoji and slang.
13. Attach files with care
Name the attachment clearly ("Smith_CV_2026-11.pdf", not "Document1"), mention it in the text, and check the attachment is there before sending. Large files can be refused by the recipient's server, so consider sharing a link from your organisation's approved storage and check that the sharing permissions let the reader open it. Do not send sensitive files unless your organisation permits it and the channel is secure.
14. Proofread before sending
Typos and wrong names are the fastest way to look careless. Read the message aloud once, check names and numbers, and run the text through the Grammar Checker and Spell Checker. The Spell Checker works in American or British English; pick the one your reader expects ("organise" or "organize", "colour" or "color").
15. Close clearly and sign off properly
End with the next step ("I will call you on Tuesday") and a short closing such as "Kind regards," "Best regards," or "Thanks,". Then your name, and a short signature with job title, organisation and a phone number if useful. Keep the signature to a few lines, and avoid large images or long legal text in internal mail. See how to end an email for closings by situation.
Part 3: Handle the thread
16. Reply promptly, and say when you will reply fully
Many workplaces treat one working day as a reasonable reply time for ordinary messages, and a few hours as normal for urgent ones. That is a common expectation, not a rule, and your team may set a different norm. If you need longer, send a short holding reply: "Thanks, received. I will have the figures to you by Thursday." If you will be away, set an out-of-office message.
17. Be careful with reply-all
Use reply-all only when everyone on the thread needs your answer. A reply of "Thanks!" to 40 people is noise. Check the To and CC lines before you send, and remove people who no longer need the thread, saying so briefly ("Removing Jo from CC; this is internal").
18. Do not forward without reading
An earlier message in the chain might contain private details, an unflattering comment or a client's information. Read down the whole thread, delete what the new reader should not see, and add a line saying why you are forwarding.
19. Do not use email for what email does badly
Pick up the phone or arrange a call when the matter is urgent, emotional, complicated, or has gone back and forth more than three times without progress. Sensitive news such as bad performance feedback, a conflict, or a resignation is usually better delivered in person or live and then confirmed in writing. Use a chat tool for quick questions if your team uses one.
20. Protect privacy and never write what you would not want read aloud
Emails can be forwarded, archived, and requested in disputes or by regulators. Do not put passwords, payment card numbers or health details in an email unless your organisation's secure process allows it. Be cautious with unexpected requests for money or login details: they may be phishing, so check with the sender by another route before you act.
Cross-cultural notes for teams in different countries
The rules above reflect common English-language business practice. Teams that span countries meet differences in directness, formality and speed. Treat the points below as tendencies, not stereotypes, because every person and company is different.
| Region | Things to watch |
|---|---|
| United States | Often direct and brief; first names are common early on; a clear request and deadline are welcome. |
| United Kingdom | Politeness softeners ("would you mind", "it might be worth") are common; a request may be phrased as a suggestion. Spelling is British. |
| India | Formal titles and "Sir" or "Madam" can be common with seniors; "kindly" and "please revert" are used in many workplaces, and are fine to read as polite, though some readers elsewhere find them stiff. Time zones can mean next-day replies. |
| Southeast Asia | Hierarchy and courtesy matter in many workplaces; titles and a warm greeting are appreciated; urgent matters are often followed up on a messaging app. |
| Continental Europe | Formality at first contact (surname and title) is common in several countries; agreement on when to switch to first names is often explicit. Working hours and holiday periods are strictly respected. |
Practical tips for mixed teams:
- State deadlines with a time zone: "by Friday 17:00 GMT" or "by 9 am Eastern", and write dates in an unambiguous form such as 14 November 2026, because 03/04 means different dates in different places.
- Write plainly. Idioms such as "ballpark" or "touch base" can confuse readers who learned English as a second language.
- Read tone generously. A short or very formal reply may be a matter of style, not displeasure.
- Confirm important decisions in writing, whatever channel was used first.
Examples you can adapt
Request with a deadline:
Subject: Request: comments on draft policy by Thursday 12:00
Hi Priya,
Could you send your comments on the attached draft policy by Thursday at 12:00? I will merge all feedback that afternoon and circulate a final version on Friday.
Thanks, Marco
Holding reply:
Subject: Re: Supplier contract
Hello Ms Okafor, thank you for your message. I have forwarded it to our legal team and will reply with a full answer by Wednesday.
Kind regards, Daniel Reid
More ready-to-adapt messages are in our professional email examples, and the Email & Letter Writer can draft a first version from your notes. It produces generated text, so add the real names, dates and facts yourself.
Send or wait? A checklist
Before you press Send:
- Does the subject line tell the reader what this is and what is needed?
- Is the main request in the first two lines?
- Are the right people in To, CC and BCC, and is anyone included who should not be?
- Is the greeting and closing right for this reader?
- Is the tone one I would be happy to hear read aloud?
- Is the attachment actually attached, and is the file name clear?
- Did I check names, numbers, dates and links?
- Did I run a spelling and grammar check?
- Am I angry or upset? If so, save it as a draft and wait before sending.
- Would a short call be quicker or kinder?
If any answer is "no" or "not sure", wait, fix it, and then send.
Try the tools
Frequently asked questions
What are the most important rules of email etiquette?
Write a specific subject line, put your request in the first lines, keep a courteous and neutral tone, choose To, CC and BCC with care, proofread, and reply within the time your workplace expects. Following these habits helps readers act on a message without asking follow-up questions.
How quickly should I reply to a work email?
Many workplaces expect a reply within one working day for ordinary messages, but norms vary by company, role and country. If you need longer, send a short note saying when you will reply fully. Urgent matters are often better handled by a phone call or chat message.
Is it rude to use reply-all?
Not when everyone on the thread needs your answer, such as a change to a shared schedule. It becomes annoying for short acknowledgements like "Thanks" sent to a large group. Check the recipients first, and reply only to the sender if the group does not need your message.
When should I call instead of sending an email?
Call or meet when the matter is urgent, emotionally sensitive, complex, or has gone back and forth several times without a decision. Difficult feedback, conflicts and bad news are usually better handled live, then confirmed in a short written summary so that everyone has a record.
Related guides
- How to Write a Professional Email: Structure, Tone Ladder and Six Templates — A professional email has six parts: a specific subject line, a greeting, the purpose in the first sentence, only the det…
- CC vs BCC in Email: What They Mean and When to Use Each — To is for the people who must act, CC (carbon copy) is for people who should be kept informed, and BCC (blind carbon cop…
- Email Subject Lines: Rules and 60 Examples by Situation — A good subject line says what the email is about and what you need, in the first few words. Be specific, put the key det…
- How to End an Email: 40+ Sign-Offs, Closing Lines and When to Use Them — End an email with a closing line that states the next step, then a sign-off and your name. "Best regards" and "Kind rega…
- 15 Professional Email Examples You Can Copy and Customise — These fifteen professional email examples cover the situations people search for most: asking for a meeting, chasing an …