The proper email format has five parts in order: a specific subject line, a greeting matched to the relationship, an opening line that states the purpose, a body with only the details the reader needs, and a closing with a sign-off and signature. A valid email address follows a separate format defined by RFC 5321: local-part@domain, with the local part capped at 64 characters and the full address capped at 254 characters in practice.
Two different questions hide behind the same search term. Someone asking "email format" might want the structure of a professional email: what goes where, how long it should be, how to open and close it. Someone else is trying to guess how a company builds its addresses, because they have a name and a domain but no way to reach the person. Most guides answer one and ignore the other.
This guide answers both. Use the proper format section to structure any professional email, the valid address format section for the technical rules behind local-part@domain, and the company address formats and how to find one sections if you are trying to reach someone at a specific company.
What Is the Proper Format for a Professional Email?
The proper format for a professional email has five parts, always in the same order: a subject line, a greeting, an opening line that states the purpose, a body with supporting details, and a closing with a sign-off and signature. Drop one of the five and the reader has to work to figure out what you want. Keep all five short and the email reads in seconds instead of minutes.
Here is the structure, part by part:
- Subject line. 4 to 8 words that name the action or topic. "Confirm Q3 pricing by Friday" gets opened; "Quick question" gets skimmed and archived.
- Greeting. "Hi [Name]," works for most professional email. Match the formality to the relationship and the reader's own last message if you have one.
- Opening line. One sentence, first thing in the body, that states why you are writing. "I'm reaching out to confirm next week's onboarding call."
- Body. 2 to 5 lines with only the facts the reader needs to respond: one line of context, the essential details, and options if a decision is required.
- Closing. One line that names the next step, a sign-off phrase ("Best," "Thanks," "Best regards,"), and a signature with your name, role, and one way to reach you.
Assembled into a real email, the five parts look like this:
Subject: Confirm Q3 pricing by Friday
Hi Elena,
I'm reaching out to confirm the updated Q3 pricing before we send the contract to Legal.
The only change is Section 4: seat price drops to $79/user for 50+ seats, matching what we discussed on the call. Everything else in the March proposal stays the same.
Can you confirm you're good with the new number by Friday so we can get the contract out Monday?
Best,
Marc Dubois
Head of Sales, Sortlist
marc@sortlist.com
Notice the ask sits in the first line of the body, not buried at the bottom. That habit, more than any wording choice, is the difference between an email that gets a same-day reply and one that sits unread for a week.
What Is a Valid Email Address Format?
A valid email address follows the format local-part@domain, as defined by RFC 5321, the internet standard that governs how mail servers transmit email. The local part identifies the mailbox, for example "jane.doe"; the "@" symbol separates it from the domain; and the domain identifies the mail server responsible for delivery, for example "company.com".
The technical rules that make an address valid:
- Exactly one "@" symbol. "jane@doe@company.com" is not valid; there can only be one separator between the local part and the domain.
- Local part capped at 64 characters. RFC 5321 limits the section before the "@" to 64 octets.
- Domain capped at 255 characters. The domain, including any subdomains, has its own 255-octet ceiling.
- Restricted characters in the local part. Letters, digits, and a limited set of symbols (dot, underscore, percent, plus, hyphen) are safe unquoted. A dot cannot open, close, or repeat consecutively.
- The domain must resolve. A syntactically valid address can still bounce if the domain has no mail exchange (MX) record, which is why passing a format check does not guarantee deliverability.
A few examples make the rules concrete:
| Address | Valid? | Why |
|---|---|---|
| jane.doe@company.com | Valid | Standard local part, resolvable domain |
| j.doe+sales@company.com | Valid | The "+" tag is allowed and commonly used for filtering |
| jane..doe@company.com | Invalid | Consecutive dots are not permitted in the local part |
| jane@company | Invalid for mail delivery | Missing top-level domain; most mail servers will reject it |
| jane@@company.com | Invalid | Two "@" symbols; only one separator is allowed |
Check an email format
Syntax valid does not mean the inbox exists. Overloop's email finder verifies deliverability against 450M contacts.
What Are the Most Common Company Email Address Formats?
Most companies pick one address pattern for the whole domain and build every employee's address from their name using that pattern. Learn the pattern once, and you can build almost anyone's address at that company from a name and a domain alone.
| Format | Example (Jane Doe at acme.com) | Where it's common |
|---|---|---|
| first.last@ | jane.doe@acme.com | Large companies and enterprises |
| flast@ | jdoe@acme.com | Mid-size companies, roughly 50 to 500 employees |
| first@ | jane@acme.com | Startups and small teams under 10 people |
| firstlast@ | janedoe@acme.com | Alternative to first.last, no separator |
| first_last@ | jane_doe@acme.com | Underscore variant, less common |
| lastf@ | doej@acme.com | Occasional, some large enterprises |
The pattern that dominates changes predictably with company size:
| Company size | Dominant pattern | Share |
|---|---|---|
| 1 to 10 employees | first@ | 71.5% |
| 11 to 50 employees | first@ | 41.9% |
| 51 to 200 employees | flast@ | 41.8% |
| 201 to 500 employees | flast@ | 44.8% |
| 1,001 to 5,000 employees | first.last@ | 48.1% |
| 10,001+ employees | first.last@ | 56.3% |
The practical takeaway: if you only know one confirmed address at a company, you can usually infer the pattern for the whole domain, unless the company is large enough to run a first.last convention with occasional exceptions for name collisions (two "Jane Doe" entries, for instance, which often get a middle initial or number appended).
How Do You Find a Company's Email Address Format?
Once you know the pattern, you can build most addresses at that company without ever seeing them published. Four ways to confirm it before you rely on a guess:
- Check a published address. The "Contact," "About," or "Press" page often shows one real address ("press@acme.com" or "jane.doe@acme.com"), which reveals the pattern instantly.
- Read the source of an email you already have. A signature, a forwarded thread, or a quote in a press release frequently contains a real, working address.
- Search LinkedIn and company bios. Some profiles list a direct email; job postings and conference bios occasionally include one too.
- Use pattern-matching plus verification. Given one confirmed address at a domain, apply the same pattern to any other name at that company, then verify each guess against the mail server before you send.
That last step is what an email finder automates: it checks known patterns and public records for a domain, builds the likely address, and verifies it is live before it ever reaches your list. Overloop's contact database covers 450M B2B profiles with formats already mapped, so instead of manually testing four permutations per contact, you search by name and company and get a verified address back.
If you build addresses manually, verify before you send at any volume. A syntactically valid, correctly patterned guess can still hit a closed mailbox, and sending a batch of unverified guesses damages your domain's sending reputation. Running a list through an email verification API before a campaign catches invalid and high-risk addresses before they turn into bounces.
Stop guessing company email formats
Overloop's B2B contact database covers 450M verified profiles with email formats already mapped, so you search by name and company instead of testing permutations one by one.
Try Overloop free →See featuresFormal vs Casual Email Format: Which Should You Use?
Once the five-part structure is right, tone is the only variable left. Get it wrong and you either sound stiff to a friendly contact or sloppy to someone who expects polish. Here is the quick chooser.
- Formal: "Dear [Title] [Last name]," and "Sincerely," or "Best regards," for first contact with executives, legal or financial matters, and job applications.
- Professional (the default): "Hi [First name]," and "Best," or "Thanks," for most day-to-day work email.
- Casual: "Hi [Name]," or just "[Name]," and "Cheers," or "Talk soon," for people you know well.
- Cold outreach: "Hi [First name]," followed by a question-based call to action instead of a generic sign-off.
For the openers and greetings that fit each context, see our guide to how to start an email. For the full list of sign-offs grouped by formality, see 45+ email sign-offs by context. The format stays the same across all four; only the greeting, sign-off, and word choice shift.
Email Format Examples by Situation
Here is the five-part format applied across common situations. Copy the structure, replace the specifics.
Formal request to a senior stakeholder
Subject: Approval needed: updated MSA by Thursday
Hello Ms. Patel,
I'm writing to request your approval on the updated Master Service Agreement before our legal team can countersign.
Section 4 (payment terms) now matches the terms from our last call: net 30 instead of net 45. Everything else is unchanged from the version you reviewed in March.
Could you confirm approval by Thursday so we can keep the July 15 onboarding date?
Best regards,
Jordan Lee
Head of Partnerships, Acme Co
jordan@acme.co
Cold outreach to a new prospect
Subject: Question about outbound at Nordvale
Hi Alex,
Saw Nordvale is hiring two SDRs this quarter, which usually means outbound volume is about to jump.
We help B2B teams personalize cold email and LinkedIn outreach at scale without losing the "a human wrote this" feel.
Worth a quick 15-minute call next week to compare notes?
Appreciate your time either way,
Priya Nair
Sales Lead, Overloop
Internal quick update
Subject: Update: contract redlines resolved
Hi team,
Legal signed off on the redlines this morning. No changes to pricing or scope.
Next step: I'll send the final PDF for countersignature by end of day.
Thanks,
Sam
Meeting or scheduling request
Subject: 15 min on SOC 2 timeline?
Hi Marcus,
I'd like to align on the SOC 2 audit timeline before we brief the board next month.
Are you free Tuesday or Wednesday afternoon, 30 minutes, your call on the time?
Thanks,
Dana
Following up on a quiet proposal
Subject: Re: Q3 proposal (bumping this)
Hi Elena,
Circling back on the proposal from last week in case it got buried.
Two options if it's still relevant: (A) start with the pilot scope, or (B) go straight to the full rollout.
Should I follow up next month instead, or is this still a priority?
Best,
Marc
Job application email
Subject: Application: Senior RevOps Manager (Jane Doe)
Dear Hiring Team,
I'm applying for the Senior RevOps Manager role posted this week. I've attached my resume and a short case study relevant to your onboarding funnel.
I'm available for a call any afternoon this week if that's useful.
Sincerely,
Jane Doe
jane.doe@email.com
Common Email Format Mistakes to Avoid
Most format mistakes cost you a reply before the reader even considers the content. Here is what to drop and what to do instead.
| Don't | Do instead |
|---|---|
| Bury the ask in the last paragraph | Put the ask in the first line of the body |
| Write a vague subject like "Quick question" or "Hey" | Lead the subject with the action or topic: "Approve Q3 pricing by Fri" |
| Guess a company's email format and send without checking | Verify the address against the mail server before sending, especially at volume |
| Write one dense paragraph with no bullets | Break dates, options, and requirements into short bullets for mobile scanning |
| Attach a giant signature with disclaimers and banners | Keep the signature to name, role, company, and one contact method |
| Guess a name variant ("Rob" instead of "Robert") without checking | Use the name format you can confirm from a public source; default to the safer full form |
For the subject lines that get these opened in the first place, see our guide to the best subject lines for sales emails, and for length benchmarks, what's the best email length for sales outreach.
