What is email etiquette?
Email etiquette is the set of conventions that make work email clear and courteous: a specific subject, a greeting, the request up front, a sensible length, careful use of CC and reply-all, and a sign-off with your name.
Free email writing tool
An email etiquette checker scores a work email against professional email etiquette rules before you send it. Paste your draft to see each rule it breaks, from a vague subject or buried ask to a missing attachment, with a one-line fix for each.
Your email stays in this browser. Nothing is sent or stored.
Etiquette score
17 / 100
Rewrite before sending
11 issues · 3 of 14 checks passed · 49 words
high · Mentioned attachment is attached
The email mentions an attachment, but you haven't marked one as attached.
Fix: Attach the file before you write the email, then tick the box above.
medium · Clear subject line
"QUICK QUESTION!!" doesn't tell the reader what the email is about.
Fix: Name the topic and the action, like "Review: pricing page copy by Thu".
medium · Sign-off
The email ends without a closing.
Fix: End with a sign-off on its own line, like "Thanks," or "Best regards,", then your name.
medium · Ask in the first two sentences
Your request is in sentence 5: "Can you approve it by EOD??".
Fix: Move the ask to the first or second sentence; put background after it.
medium · No shouting in capitals
The subject is in all capitals.
Fix: Use normal case; add emphasis with a clear sentence or bold one key phrase.
medium · Calm punctuation
Repeated marks like "!!" or "?!" read as alarm or anger.
Fix: Keep one exclamation mark at most, and none in the subject.
medium · Reasonable CC and reply-all
4 people are on CC.
Fix: CC only people who need to know; move a big group to BCC or send a separate note.
medium · No passive-aggressive phrases
"Per my last email" can read as irritated.
Fix: Restate the point plainly: "Here's the date again: June 3."
low · Acronyms and shorthand explained
Found chat shorthand: EOD; unexplained acronyms: SOW, KPI.
Fix: Spell out acronyms on first use, like "statement of work (SOW)", and swap EOD or ASAP for a real time.
low · No filler openers
"I hope this email finds you well" delays your point.
Fix: Delete it and start with why you're writing.
low · Sent during working hours
Sending at 23:30 lands outside working hours.
Fix: Use schedule send for about 8 to 10 AM in the recipient's time zone.
Avoid: Hi / Quick question
Better: Approve Q3 budget by Friday?
Avoid: Long background, request in paragraph three
Better: Can you review the draft by Thursday? Context below.
Avoid: Hey there,
Better: Hi Priya,
Avoid: Yo! (to a new client)
Better: Dear Dr. Lee, (first contact) or Hi Sam, (colleague)
Avoid: 400 words to ask for a meeting
Better: Under about 150 words for a request; link a doc for details
Avoid: Need this ASAP / by EOD
Better: Could you send it by 3 PM ET Wednesday?
Avoid: The SOW for the MSA is ready
Better: The statement of work (SOW) is ready
Avoid: This is URGENT
Better: This needs a decision today because the vendor closes at 5 PM.
Avoid: Thanks!!! See you soon!!
Better: Thanks, see you Tuesday.
Avoid: "See attached" with nothing attached
Better: Attach first, then write "The deck is attached."
Avoid: CC the whole department
Better: CC your manager; send a separate summary to the team
Avoid: 60 client addresses in To
Better: Clients in BCC, your own address in To
Avoid: "Thanks!" to 40 people
Better: Reply to the sender only
Avoid: Per my last email...
Better: Here's the date again: June 3.
Avoid: Message ends mid-thought
Better: Thanks, Sam Patel, Product Lead
Subject: Approve the statement of work by Friday? Hi Maria, Could you approve the statement of work (SOW) for the dashboard project by Friday at 3 PM? The draft is attached. We need sign-off to start the build on Monday. The only change since last week is the delivery date, which moved to March 14. Thanks, Sam
Email etiquette is the set of conventions that make work email clear and courteous: a specific subject, a greeting, the request up front, a sensible length, careful use of CC and reply-all, and a sign-off with your name.
Reply within one business day. If you need longer, send a short note saying when you'll have an answer. Urgent internal requests usually deserve a same-day reply.
Use CC for people who should see the email and may need to reply. Use BCC when you're emailing a large group who don't know each other, so their addresses stay private and nobody can reply-all.
No. "Hi [Name]," is the standard greeting for most work email in the US and UK. Use "Dear [Name]," for formal first contact, job applications, or when the other person writes that way. Avoid "Hey" with people you don't know.
No. Every rule runs in your browser with plain text checks. Nothing you paste leaves this page, and there's no AI rewrite.
DripAgent turns product events into onboarding, follow-up and re-engagement emails for AI-built SaaS apps, with clear subjects, one ask per email and sensible send times.
Professional greetings and opening lines by situation and tone.
105 email closings by tone, with a personalized closing block.
Start from a structured template for common work emails.
See exactly who sees whom and who gets reply-all (MailParse).