How to write emails | Avoid worst email mistakes | Write professional emails

Professional email success often comes down to avoiding small, preventable errors—especially around addressing, formatting, and clarity of intent. The most damaging mistakes tend to be the ones that make recipients work harder (unclear subject lines, generic attachment names, long unreadable bodies) or that signal carelessness (wrong titles, missing signatures, emojis in formal contexts). When those friction points stack up, replies drop—regardless of how qualified the sender is.

The guidance starts with the basics of addressing. Using vague openers like “Dear Sir/Madam” or “To whomsoever it may concern,” or even worse, picking the wrong default salutation, wastes the recipient’s time and undermines credibility. The recommended fix is simple: do basic research to find the correct person. If the name is unknown, use the role—“Dear Hiring Manager” or “Dear Professor”—rather than a generic placeholder.

Even with the right name, formatting can go wrong. The transcript warns against mismatched honorifics such as “Dear Mr Rakesh,” which can violate common email norms. The solution depends on relationship and context: if the sender and recipient use first names, “Dear Rakesh” or “Hello Nandini” is acceptable; if the relationship is professional and the sender doesn’t know the recipient personally, use a full formal form like “Dear Mr Rakesh Malotra” or “Dear Mr Malotra.”

From there, the checklist shifts to presentation and professionalism. A missing or weak email signature is treated as a common red flag; signatures should include the sender’s full name plus designation (job title or student status), along with college or company name, and optionally contact details like mobile number or LinkedIn. Emojis are discouraged in emails to people the sender doesn’t know well, since they can come off as informal or even offensive—especially in cross-cultural or academic contexts.

Clarity continues with the subject line and attachments. Generic subjects like “Resume” or “Resume please” with a PDF attached are criticized as lazy and uninformative. Strong subject lines should state the purpose and role, for example “Digital Marketing Intern Resume Ayush Aurora,” and meeting-related subjects should include the topic and time (“App Development Meeting Reschedule Friday 6pm”). Attachments should also be renamed from vague defaults like “resume final” or “report version 3” to descriptive filenames that include the topic and relevant identifiers (role, name, or date) so recipients can file and track them.

Inside the email body, the advice is to keep messages concise and readable, using bullet points to highlight key messages instead of long paragraphs. Equally important is a clear call to action at the end: rather than passive closings like “I look forward to hearing from you,” the sender should specify what they need and by when (e.g., feedback by tomorrow, or confirmation for a Friday meeting). The transcript also stresses that recipients should respond to emails—at least with a brief acknowledgment—because silence can create miscommunication.

Finally, the transcript adds practical etiquette: reply to the correct people (avoid unnecessary “Reply All” or accidental exclusion of CC recipients) and close with a cheerful greeting before the signature to leave a positive tone. A final “send” checklist—recipient, subject spelling, body, signature, attachments, and grammar—aims to prevent avoidable errors before they reach inboxes.