The thing that determines whether your email gets read is the subject line and the first sentence—in that order. A subject line that fails costs you the open. A first sentence that fails costs you the read. Learning How to Write a Proper Email means surviving those two critical moments, as most communication problems trace back to these initial failure points.
A proper email is clear about what it wants, respectful of the reader’s time, and actionable. It does not make the reader search for the point, guess what response is expected, or wade through context they do not need. Those principles apply whether you are writing a cold outreach, a follow-up, a complaint, or a meeting request.
The Anatomy of a Good Email
| Element | What to Do | What to Avoid | Example |
|---|---|---|---|
| Subject line | Specific, relevant, creates reason to open | Vague (‘Following up’), clickbait, all caps | ‘Feedback on the proposal you sent Thursday’ |
| Greeting | Match formality to relationship and context | Generic ‘To Whom It May Concern’; overly casual with strangers | ‘Hi James,’ / ‘Dear Ms. Chen,’ / ‘Hello team,’ |
| Opening sentence | State the purpose or reference shared context immediately | Starting with ‘I hope this email finds you well’ – everyone knows it’s filler | ‘I’m writing about the contract renewal due next Friday.’ |
| Body | One clear purpose per email; short paragraphs; use bullet points for lists | Wall of text; multiple unrelated topics; passive voice throughout | 3-5 short paragraphs or bulleted items |
| Call to action | State exactly what you need and by when | Vague endings (‘Let me know your thoughts’) with no specific ask | ‘Could you confirm by Wednesday whether the budget is approved?’ |
| Sign-off | Match the tone: formal or professional | Over-formal (‘Yours faithfully’) in casual contexts; no sign-off at all | ‘Best regards,’ / ‘Thanks,’ / ‘Kind regards,’ |
Subject Line Formulas That Consistently Work
The specific reference: ‘Re: your question about invoicing from Tuesday’ – shows you are responding to something specific, not blasting a template.
The direct request: ‘Quick question about your availability next week’ – sets expectations for what the email contains and what the reader needs to do.
The time anchor: ‘Action needed before Friday: project approval’ – urgency with a reason works; urgency without a reason feels manipulative.
The benefit lead: ‘Three ways to reduce your reporting time (based on our conversation)’ – works for outreach when you can reference a genuine shared context.
The short subject: Research by Boomerang found that subject lines of 3-4 words received higher open rates than longer ones in professional contexts. Sometimes the simplest approach is most effective: ‘Quick question,’ ‘Intro: [Name],’ ‘Proposal attached.’
Tone and Length: Matching the Context
The fundamental error most people make is using the same register for all emails. An email to your manager asking for annual leave and an email to a new client requiring a contract signature are completely different communication events. Getting the register wrong signals lack of situational awareness, which has professional consequences.
| Context | Appropriate Tone | Appropriate Length | Example Opener |
|---|---|---|---|
| Internal team communication | Casual to professional | 2-5 sentences | ‘Hey all – quick update on the launch schedule:’ |
| External professional (known) | Professional, warm | 3-8 sentences | ‘Hi Sarah, hope the conference went well.’ |
| External professional (unknown) | Professional, precise | 4-7 sentences – no longer | ‘My name is [X], and I’m writing about [specific thing].’ |
| Formal / legal / complaint | Formal, documented | As long as needed; structured | ‘I am writing to formally raise a concern regarding…’ |
| Cold outreach | Professional, direct, brief | 5 sentences maximum | ‘I noticed you recently expanded your team – I work with companies at this stage on…’ |
| Follow-up email | Professional, not apologetic | 3-4 sentences | ‘Following up on my email from Tuesday regarding…’ |
Email Templates for Common Scenarios
Cold Outreach
Subject: Idea for [Company Name]’s onboarding process
Hi [Name],
I came across your job post for a Customer Success Manager and noticed you’re scaling quickly. I work with SaaS companies at this stage on reducing time-to-value for new users – typically cutting the first 30 days drop-off by 20-35%.
Would a 15-minute call this week or next make sense? Happy to send over a couple of case studies first if that’s more useful.
Professional Follow-Up
Subject: Following up – proposal from 14 May
Hi [Name],
I wanted to follow up on the proposal I sent on 14 May. Happy to answer any questions or adjust anything before you make a decision.
If the timing has shifted, just let me know – I can hold the pricing until end of month.
Meeting Request
Subject: 30-min call to discuss Q3 roadmap?
Hi [Name],
I’d like to get 30 minutes with you before the end of the month to align on the Q3 roadmap before the team planning session.
I’m free Tuesday 2-5pm or Thursday morning – does either work? If not, feel free to share a time that suits.
Common Email Mistakes to Eliminate
- Hitting Reply All when only one person needs the response. This is the email equivalent of calling a meeting when an update would do.
- CC-ing people as a passive way of covering yourself rather than because they need the information. It trains people to filter your emails.
- Writing a wall of text with no formatting. If a paragraph exceeds five lines, look for a way to break it up or bullet it.
- Using vague openers (‘I hope you’re well,’ ‘Just circling back,’ ‘As per my last email’). These signal either politeness theatre or passive aggression – neither is useful.
- Sending emails when a 2-minute conversation would resolve the issue. Email is not always the right tool for the job.
- Forgetting to attach the attachment you mentioned. Write ‘attached’ only after you have confirmed the file is attached.
Email Etiquette Quick Reference
| Situation | Best Practice |
|---|---|
| Response time expectation | Same business day for urgent; within 24-48 hours for standard professional email |
| Reading receipts | Do not request them unless contractually necessary – it signals distrust |
| Emojis in professional email | Use sparingly in internal communications with established colleagues; avoid in formal external communications |
| BCC usage | Legitimate for: protecting recipient addresses in group sends; keeping someone in the loop without revealing it. Not for: quietly monitoring conversations |
| Long email chains | After 5+ replies, consider a call or meeting. Long chains mean the issue needs real-time resolution |
| Sending after hours | Schedule send for business hours unless genuinely urgent – late-night emails create pressure that impinges on others’ personal time |
