# How to Write a Formal Email Introduction (Without Sounding Stiff) Canonical URL: https://headwayskills.com/knowledge/communication/formal-email-introduction/ Markdown URL: https://headwayskills.com/knowledge/communication/formal-email-introduction.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer A formal email introduction has five parts and stays under 150 words. What goes in each one, which greeting to use, and how much to say about yourself. ## Key facts - Title: How to Write a Formal Email Introduction (Without Sounding Stiff) - Category: Communication - Primary skill: Communication - Related skills: Professional Behaviors, Networking - Primary keyword: formal email introduction - Source page: https://headwayskills.com/knowledge/communication/formal-email-introduction/ ## What this page covers - A formal email introduction has five parts and stays under 150 words. What goes in each one, which greeting to use, and how much to say about yourself. - Practical guidance for formal email introduction - How this topic connects to Communication ## Detailed explanation The cursor sits in an empty message to someone who has never heard of you, and every version you try sounds either stiff or too casual. A formal email introduction has five parts: a specific subject line, a greeting matched to the recipient, one line on who you are, one or two on why you are writing, and a single clear next step. Keep the whole thing under about 150 words. The parts are easy. What makes people stall is everything the templates leave out — how formal is formal enough, how much of your background belongs in there, and what to do when nobody answers. ## What makes a formal email introduction "formal" — and is anyone still writing that way? Formal here means predictable, not ceremonial. Look across the guides that rank for this topic — Indeed, Grammarly, Adobe, Woodpecker, Harvard's career services — and they describe the same five-part anatomy without much variation. That agreement is the useful part: this is settled convention rather than one publisher's house style, so once you know the five parts you can build the email yourself instead of hunting for a template that matches your situation. The mistake people make when they hear "formal" is to reach for older, heavier language. Several of those same sources warn against exactly that, telling writers to keep a natural, human tone. Formality is carried by the structure and the register, not by ornate vocabulary. ## What should I put in the subject line? Say what the email is. SmartReach's formal email guide puts the working range at roughly 40 characters, or six to nine words, and the format most sources land on simply names the transaction: your name plus the context, such as "Introduction: Maria Ortiz — new account manager." The reason to be plain rather than clever is that your recipient is triaging a message from a name they don't recognize. A subject line that states the transaction lets them decide in a second that the email is legitimate and worth opening. A subject built on curiosity reads like sales, which is the one impression a genuine introduction cannot afford. ## Should I open with "Dear" or "Hi"? Grammarly's guidance is that "Dear [Name]" is appropriate for every formal email, with the caveat that it now sounds slightly old-fashioned, and that a title with a surname — "Dear Ms. Okafor" — belongs in traditionally formal industries such as finance and law. That is the closest thing to a usable rule anywhere in this topic, and notice what it rests on: [the recipient's industry and seniority](/knowledge/influence/know-your-audience/), not your own preference. So the question isn't which greeting you like. It's which one your reader will find unremarkable. When you genuinely can't tell, "Dear" with a first name is the safe middle, and no recipient has ever thought worse of anyone for it. ## How long should a formal email introduction be? Under about 150 words, or one to three short paragraphs. Woodpecker's 2026 roundup of introduction emails puts it plainly: past that length you're making the reader work too hard. Worth being honest about where that number comes from. It is repeated across nearly every guide on this topic, but none of them ties it to a study — it's a [professional convention](/knowledge/communication/examples-of-email-etiquette/), not a measured finding. The reasoning behind it holds up anyway. Your email arrives from someone the recipient has no particular reason to read, so every extra sentence is a cost you are asking a stranger to absorb. Short isn't curt here. Short is considerate. ## How much should I say about myself? Less than instinct tells you. The most useful single point in any of the guides comes from Woodpecker: the biggest mistake in an introduction email is leading with yourself instead of leading with the recipient. Open with something that shows you understand their situation, and the rest of the email has somewhere to land. That reframes the task. You think you're being asked to present yourself well, when the form actually rewards showing why you're relevant to the person reading. In practice that means your role, and the one fact that explains why this email is arriving in their inbox — not a career summary. It also explains why the template hunt disappoints. A template supplies words; the judgment about what to include is yours, and it's the part that carries over to [every email you write](/knowledge/communication/business-writing-skills/) after this one. If that judgment is something you'd like a clearer read on, you can check [where your written communication stands](https://assessment.headwayskills.com/) alongside the other skills the work asks of you. ## Is "I hope this email finds you well" okay to use? The sources openly disagree, which is why you keep finding contradictory advice. Template collections print it as a model opening line. Newer guidance, including Woodpecker's, names it an instant deletion trigger. Both are right in their own context, and nobody says so out loud. Inside your own organization, writing to people who are going to read your email regardless, it's unremarkable filler and costs you nothing. In cold outreach, where the recipient decides within one line whether to keep reading, spending that line on a pleasantry is expensive. So the test is not whether the phrase is good. It's whether your reader has already decided to read you. ## How do I end it — and do I have to ask for something? "Sincerely" sits at the formal end, and "Best regards" is the safe default for most professional situations. Neither is read closely, so it isn't a decision worth much anxiety. The ask matters more. Harvard's career services guidance is to state your purpose early because recipients are busy, and to frame the email around something specific and answerable rather than an open invitation to connect. "Would you have 20 minutes in the next two weeks?" gives the reader a decision they can make. "I'd love to connect sometime" gives them homework, and homework gets postponed indefinitely. ## How do I introduce myself to a whole new team? One message to the group, not twenty separate emails. This is the easier case, because your colleagues already have a reason to read: they've been told you're starting. That lets you relax the register a notch. Give your role, what you'll be working on first, and how people should reach you. Skip the achievements — the team will form its view from your work, and a list of credentials in a first message reads as anxious rather than impressive. Coverage of this specific scenario is thinner than for cold outreach, but the guidance that exists points the same way: brief, warm, and low on self-promotion. ## How do I email someone who has no idea who I am? Have a concrete reason, and lead with it. Not "I'd like to build my network" — a specific reason you are writing to this person rather than anyone else. A shared university, a piece of their work you actually read, a role you're trying to understand. Then the order matters more than usual: the shared context first, who you are second, the ask third and small. It feels backwards, because your instinct is to establish your credentials before you presume to ask for anything. But the recipient is deciding whether this email is relevant to them, and only you can answer that question for them. ## What do I do if they don't reply? Send [one follow-up](/knowledge/networking/networking-follow-up-email/), a few days later, short, replying to your original message so the context travels with it. Then stop. There is very little hard data on this topic — the sources are style guides and career-services pages, not studies, and reply rates for personal introductions aren't something anyone has measured well. What can be said with some confidence is that silence is usually about inbox volume and timing, not about your email. A second message accounts for the first one having landed on a bad day. A third starts creating the impression you were trying to avoid. ## The skills underneath a good introduction email Read back over those ten answers and the formatting questions turn out to be the small ones. Almost every real decision came down to reading the person on the other end — how much they already expect from you, what they'll find unremarkable, what counts as a reasonable thing to ask a stranger. That is not knowledge about email. It's a set of habits that show up in every professional message you send. **Communication** is the most visible of them. The rules that govern an introduction email are the ordinary rules of professional writing under maximum pressure: state the main point first, be brief, and adapt to the person receiving it. They matter more here than anywhere because your reader has no prior context to fill in your gaps. Nothing about the message is doing work except the words on the screen. **Professional Behaviors** cover what "formal" actually means in practice. Matching the register your reader's industry expects, staying polite without stiffening, writing about other people as if they were reading over your shoulder — introduction emails get forwarded, routinely. It's also the reason a message full of your own achievements reads badly while one that shows genuine interest in the other person reads well. **Networking** governs the cold version. The rule that turns a vague "I'd love to connect" into an email that gets answered is a simple one: reach out to a stranger only with a concrete reason. What makes those emails work isn't polish, it's having something real to offer or a genuinely specific question to ask, and then following up promptly and personally rather than letting the thread die. Those three sit inside a wider set of twelve work skills, all of them learnable rather than fixed, and it's rarely obvious from the inside which one is currently costing you the most. Seven minutes with the **free Work Skills Test** will tell you [which one to build first](https://assessment.headwayskills.com/). If some of that felt familiar, it's probably because you already do parts of it without naming them — you noticed that this email was worth getting right and stopped to check the conventions instead of firing something off. That instinct is the part most people skip. The rest is learnable, and none of it requires becoming a different kind of person at the keyboard. The plain, considerate version of you is the one these conventions were built for. What's worth knowing is which of these habits are already solid and which are quietly costing you — because as your responsibilities grow, more of your working relationships start on a screen rather than in a room, and the first impression you make in writing does more of the work. The useful next step is a clear read on where you actually stand. ## Find out where your work skills stand You know the format now. The open question is the one underneath it — how your written communication and the habits around it compare across the skills your work will keep asking for. The Work Skills Test is a **free** self-assessment of your work skills. It gives you a read on all twelve, and shows you which ones will make the biggest difference to you right now rather than leaving you to guess. **[Take the skills test](https://assessment.headwayskills.com/)** *Free, and about seven minutes from start to finish.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? A formal email introduction has five parts and stays under 150 words. What goes in each one, which greeting to use, and how much to say about yourself. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Professional Behaviors, Networking. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/professional-behaviors.md - https://headwayskills.com/knowledge/networking.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/formal-email-introduction/ Preferred summary: "A formal email introduction has five parts and stays under 150 words. What goes in each one, which greeting to use, and how much to say about yourself." ## Change log - 2026-07-07: Content collection version published.