{"id":51944,"date":"2026-07-03T04:29:57","date_gmt":"2026-07-03T03:29:57","guid":{"rendered":"https:\/\/woodpecker.co\/blog\/?p=51944"},"modified":"2026-09-03T04:36:31","modified_gmt":"2026-09-03T03:36:31","slug":"parts-of-an-email","status":"publish","type":"post","link":"https:\/\/woodpecker.co\/blog\/parts-of-an-email\/","title":{"rendered":"Parts of an Email: Structure, Format & Examples"},"content":{"rendered":"

A well-written email is easy to understand before the recipient has finished reading it. The subject sets the expectation, the opening establishes context, the body carries the information and the ending makes the next step clear.<\/span><\/p>\n

Those parts remain broadly the same across everyday business emails, formal messages, follow-ups and cold outreach. What changes is the tone, length and amount of context the reader already has.<\/span><\/p>\n

This guide breaks down the main parts of an email, explains how email structure differs from email formatting and shows how the same structure changes across common business situations.<\/span><\/p>\n

What are the main parts of an email?<\/b><\/h2>\n

A professional email has five core message parts: a subject line, greeting, body, closing and signature. Before those come the addressing fields, such as From, To and CC, which tell the email system and recipient who is involved in the conversation.<\/span><\/p>\n\n\n\n\n\n\n\n\n
Part<\/b><\/td>\nIts job<\/b><\/td>\nExample<\/b><\/td>\n<\/tr>\n
Subject line<\/span><\/td>\nExplains what the email concerns<\/span><\/td>\nUpdated proposal for review<\/span><\/td>\n<\/tr>\n
Greeting<\/span><\/td>\nAddresses the recipient and sets the tone<\/span><\/td>\nHi James,<\/span><\/td>\n<\/tr>\n
Body<\/span><\/td>\nProvides the context and information the recipient needs<\/span><\/td>\nI\u2019ve updated the proposal based on Tuesday\u2019s discussion.<\/span><\/td>\n<\/tr>\n
Closing<\/span><\/td>\nStates the next step and ends the message<\/span><\/td>\nCould you confirm the timeline by Friday? Kind regards,<\/span><\/td>\n<\/tr>\n
Signature<\/span><\/td>\nIdentifies the sender<\/span><\/td>\nMaria Lopez, Account Manager<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A useful way to judge the complete email is to ask whether the recipient can answer three questions without reconstructing the message: Who is writing? Why are they writing? What, if anything, should I do next?<\/span><\/p>\n\"Email\n

Email structure and email format are not the same thing<\/b><\/h2>\n

Email structure describes the order and purpose of the message. Email format describes how that information appears on the screen. Paragraph length, spacing, bullets, fonts, links and attachments are formatting choices; the subject, greeting, body and closing belong to the structure.<\/span><\/p>\n

An email can have all the correct structural parts and still be difficult to read because the body appears as one dense paragraph. The reverse is also possible: a beautifully formatted message may still leave the reader unsure what the sender wants.<\/span><\/p>\n

For a deeper look at presentation and conventions, Woodpecker has a separate guide to <\/span>proper professional email format<\/span><\/a>. Here, the focus is on how the parts work together.<\/span><\/p>\n

Start with the sender and recipient details<\/b><\/h2>\n

The content begins with the subject line, but an email starts with the From and To fields. In business communication, the sender should be easy to identify and the recipient should be the person who is expected to read or act on the message.<\/span><\/p>\n

A named address such as anna@company.com<\/b> gives an external recipient more context than an unrelated username or a generic mailbox when the conversation is meant to be one-to-one. Woodpecker’s guide to <\/span>professional email address formats<\/span><\/a> covers the common options and when role-based addresses still make sense.<\/span><\/p>\n

What are the parts of an email address?<\/b><\/h3>\n

An email address and an email message have different structures. In an address such as anna@company.com<\/b>, \u201canna\u201d is the local part and \u201ccompany.com\u201d is the domain. The @ symbol separates them.<\/span><\/p>\n\n\n\n\n\n\n
Address element<\/b><\/td>\nExample<\/b><\/td>\nWhat it represents<\/b><\/td>\n<\/tr>\n
Local part<\/span><\/td>\nanna<\/span><\/td>\nThe mailbox identifier before @<\/span><\/td>\n<\/tr>\n
@ symbol<\/span><\/td>\n@<\/span><\/td>\nSeparates the local part from the domain<\/span><\/td>\n<\/tr>\n
Domain<\/span><\/td>\ncompany.com<\/span><\/td>\nThe domain responsible for receiving mail for the address<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

You may also see CC and BCC fields. CC is useful when somebody needs visibility but is not the main recipient. BCC hides the listed recipients from one another and should be used deliberately, particularly when privacy matters.<\/span><\/p>\n

The visible From, To, CC and Subject area should not be confused with the complete technical email header. Behind the message, email systems add routing and delivery information used to move and authenticate the email.<\/span><\/p>\n

Write a subject line that sets the right expectation<\/b><\/h2>\n

The subject line should tell the recipient enough to understand what kind of message is waiting for them. In an existing business relationship, clarity usually matters more than curiosity: \u201cUpdated onboarding schedule\u201d or \u201cFeedback needed on Q3 campaign\u201d is easier to process than \u201cQuick question\u201d or \u201cImportant.\u201d<\/span><\/p>\n\n\n\n\n\n\n\n
Vague<\/b><\/td>\nClearer<\/b><\/td>\n<\/tr>\n
Quick question<\/span><\/td>\nQuestion about the Q3 campaign budget<\/span><\/td>\n<\/tr>\n
Update<\/span><\/td>\nUpdated onboarding schedule<\/span><\/td>\n<\/tr>\n
Meeting<\/span><\/td>\nAgenda for Monday\u2019s project meeting<\/span><\/td>\n<\/tr>\n
Important<\/span><\/td>\nContract approval needed by Friday<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Cold email is slightly different because the recipient does not already know the context. The subject still needs to be accurate, though. It should signal relevance without relying on false urgency, fake reply prefixes or a promise the email body does not fulfill.<\/span><\/p>\n

If you are testing subject lines across a large enough campaign, use one meaningful change at a time. Woodpecker’s <\/span>cold email A\/B test calculator<\/span><\/a> can help determine whether the difference between two variants is large enough to treat as meaningful rather than random noise.<\/span><\/p>\n

Choose a greeting that fits the relationship<\/b><\/h2>\n

A greeting sets the register for the rest of the message. \u201cHi Maya\u201d works well in most everyday business situations, while \u201cDear Dr. Patel\u201d may suit a more formal first contact. Colleagues who communicate regularly can often use something even lighter.<\/span><\/p>\n

There is no need to make the greeting more elaborate than the relationship requires. In fact, a formal salutation followed by very casual copy can feel more awkward than a simple greeting used consistently throughout the email.<\/span><\/p>\n\n\n\n\n\n\n\n
Situation<\/b><\/td>\nPossible greeting<\/b><\/td>\n<\/tr>\n
Everyday business email<\/span><\/td>\nHi Maya,<\/span><\/td>\n<\/tr>\n
Formal first contact<\/span><\/td>\nDear Ms. Patel,<\/span><\/td>\n<\/tr>\n
Existing client relationship<\/span><\/td>\nHello David,<\/span><\/td>\n<\/tr>\n
Internal email<\/span><\/td>\nHi Alex,<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Woodpecker’s <\/span>email greetings guide<\/span><\/a> has more examples for formal, professional, casual and cold-outreach contexts.<\/span><\/p>\n

Build the email body around one main purpose<\/b><\/h2>\n

The body should give the recipient enough information to understand the message and respond without asking them to sort through unrelated background. In most professional emails, a useful order is context, essential information and next step.<\/span><\/p>\n

For example:<\/span><\/p>\n

Hi Olivia,<\/b><\/span><\/p>\n

I\u2019ve updated the onboarding timeline based on our call yesterday. The first setup session can now take place on Tuesday or Thursday next week.<\/span><\/p>\n

Which day works better for your team?<\/span><\/p>\n

Best,
\nDaniel<\/b><\/span><\/p>\n

Nothing in that message is particularly clever. It works because the reader knows what changed and can answer without searching for the request.<\/span><\/p>\n

Put information in the right layer<\/b><\/h3>\n

A common formatting problem is trying to fit an entire project into the email itself. If the recipient needs a report, proposal or technical specification, summarize what matters for the decision in the message and place the supporting detail in the document.<\/span><\/p>\n\"Information\n

For an attachment, tell the reader what the file is and why it matters. \u201cI\u2019ve attached the revised proposal with the updated launch date and budget\u201d gives more context than simply announcing that a document is attached. The guide to <\/span>alternatives to \u201cplease find attached\u201d<\/span><\/a> covers this in more detail.<\/span><\/p>\n

Use bullets when the reader needs to scan several items<\/b><\/h3>\n

Bullets help when an email contains several dates, requirements or decisions. They are less useful when a normal sentence would communicate the point more naturally.<\/span><\/p>\n

For example:<\/span><\/p>\n

Please review these changes before Thursday:<\/span><\/p>\n