Email communication

Emails are a vital part of user interaction, whether they involve notifications, updates, confirmations, or reminders. A clear, professional, and engaging email can significantly enhance user experience and drive action. This guide covers the generic principles for writing this kind of email; for organization-specific branding, signature, and template details, see your platform-specific email template reference.

A note on tone: several conventions in this guide — exclamation points in subject lines, more overtly action-driving CTA copy, a warmer promotional register in welcome or upgrade emails — would be flagged as marketing language in the Common Voice and Tone Mistakes and Words to Avoid guides used for knowledge base articles. Email is a genuinely different genre with different, legitimate conventions: some warmth, urgency, and directness toward action is expected and functional in a notification email in a way it isn't in a help article. Use this guide's conventions for email specifically, and the knowledge base voice guides for articles — the difference is intentional, not a contradiction.

General Principles for Email Communication

Purpose-driven content

• Clearly state the purpose of the email in the subject line and the opening paragraph.
• Focus on the primary message without overwhelming the reader.

Clarity and simplicity

• Use concise sentences and avoid complex language.
• Format the email for readability with proper spacing and bullet points where needed.

Professional yet friendly tone

• Maintain a tone that is professional but approachable. Avoid overly formal or casual language.

Action-oriented

• Include clear calls-to-action (CTAs) that guide users on the next steps.

Consistency

• Align the email tone, design, and formatting with your organization's branding guidelines.

Accessibility

• Use a legible font size and proper color contrast to ensure readability for all users.
• See Accessibility for Email Clients below for considerations specific to how email renders differently from web content.

Email Components

1. Subject line

• Keep it short and descriptive (50 characters or less; closer to 30–40 characters if you expect a significant share of readers to open on mobile, where subject lines truncate more aggressively).
• Clearly convey the purpose of the email.
• Avoid clickbait or ambiguous phrasing.

Examples:

• "Welcome — get started today"
• "Your password has been reset successfully"
• "Action required: verify your email address"

2. Preheader text

• Provide a brief summary (40–60 characters) of the email's content.
• Encourage users to open the email.

Examples:

• "Learn how to make the most of your new knowledge base."
• "Verify your account to complete the setup process."

3. Greeting

• Personalize the greeting whenever possible using the user's name.
• For generic communications, use a friendly opening.
• When writing example or placeholder greetings for internal templates or documentation about email, use a clearly generic name ("Alex," "Jordan") rather than a real or recognizable (including fictional/trademarked) name — see the Names and Personal Examples section of the Cultural Considerations in Global Documentation guide.

Examples:

• "Hi Alex,"
• "Hello,"

4. Email body

• Start with the most important information or action required.
• Break down the content into clear, scannable sections using bullet points, numbered lists, or subheadings.
• Be concise — stick to 3–4 short paragraphs.

Examples:

• "We noticed you haven't logged in recently. Here are some tips to get started again:"
• "Your subscription is about to expire on [date]. Renew now to continue enjoying uninterrupted service."

5. Call-to-action (CTA)

• Use a button or hyperlink for the primary action.
• Keep the CTA clear, direct, and action-oriented.
• Include only one primary CTA per email; multiple competing CTAs reduce the likelihood any one of them is taken.

Examples:

• "Verify my email address"
• "Learn more"
• "Renew my subscription"

6. Closing

• End with a polite and professional closing.
• Provide contact information or links to support resources.

Examples:

• "If you have any questions, feel free to reach out to our support team."
• "Thank you for choosing us."

7. Signature

Include the sender's name, title, and organization. Phone numbers in a signature should follow the international format specified in the Numbers, Dates, and Time guide (+1 (555) 123-4567), with the correct country code for the sender's actual location, rather than an inconsistent or locally-formatted variant.

Example:

Best regards,
The Support Team

8. Footer

Include links to:

• Unsubscribe options
• Privacy policy and terms of use
• Social media handles (if applicable)
• The organization's contact information

Legal and Compliance Requirements

A working, one-click unsubscribe mechanism, a physical mailing address, and honoring opt-outs promptly are not just good practice — they are legal requirements in many jurisdictions (for example, under CAN-SPAM in the United States, GDPR in the EU, and CASL in Canada) for marketing and, in some cases, transactional email. Treat the footer's unsubscribe link and contact information as a compliance requirement, not an optional nicety, and confirm your specific legal obligations with whoever owns compliance for your organization — this guide is not a substitute for that review.

Accessibility for Email Clients

Email renders differently from a web page in ways that affect accessibility specifically:

• Many email clients block images by default until the reader explicitly allows them. Alt text matters even more here than on the web, since a reader may see only the alt text for a meaningful stretch of the email — write alt text that conveys the same information the image would, not just a generic label.
• Several email clients apply a forced dark mode that can invert or alter brand colors unpredictably. Test emails in both light and dark rendering where possible, and avoid relying on a specific background color for contrast or legibility.

Types of Emails

Welcome emails

Greet new users and guide them through the onboarding process.

Example: "Welcome! Explore your dashboard and start building your knowledge base today."

Transactional emails

Confirm specific user actions, such as sign-ups, password resets, or subscription renewals.

Example: "Your subscription has been successfully renewed. Thank you for your continued support."

Notification emails

Inform users about updates, reminders, or upcoming actions.

Example: "Your free trial is ending soon. Upgrade now to continue enjoying full access."

Error/failure emails

Notify users about failed actions and guide them on how to resolve the issue.

Example: "We couldn't process your payment. Please update your billing details to continue using our services."

Feedback/survey emails

Encourage users to provide feedback or participate in surveys.

Example: "We'd love to hear your thoughts. Take our 2-minute survey."

Do's and Don'ts for Email Communication

Self-Audit Checklist

Before sending, check the email against these questions:

• Is the subject line clear, under the length guideline, and legible on mobile?
• Does the email body focus on a single primary message?
• Is there exactly one primary CTA, clearly stated and easy to find?
• Is the email formatted for readability, with short paragraphs and scannable structure?
• Does the signature's phone number follow the standard international format?
• Are all example or placeholder names generic, not real or trademarked names?
• Does the footer include a working unsubscribe link and required contact/compliance information?
• Does every image have meaningful alt text, in case images are blocked?
• Has the email been tested in both light and dark mode rendering?
• Has the email been proofread and tested for layout before sending?