Emails sent from the system that are not the direct result of user action should be sent from ‘Lumere Support’, with a reply-to address of support@lumere.com.

Emails sent as a direct result of user actions should be sent from ‘First Last (via Lumere)’, with a reply-to address of support@lumere.com.

Subject lines can vary in form, but should be kept short (65 characters is the optimal length). When the email’s subject involves a user action, the user’s name should be included at the beginning of the subject line:

Diana Shipley assigned you the task ‘Financial Analysis.’

The ‘preheader’ is the introductory bit of text displayed below the subject line on mobile devices (and certain desktop clients); commonly around 50 characters are displayed in this area. This text shouldn’t just be a repetition of the subject line—it should provide additional context. For example, an email inviting a user to a meeting could include details about the date/time and location in the preheader.

Body copy should be short (3 paragraphs maximum), to the point, and should only include the most pertinent details. If part of the email is user-generated content (for example, a comment), indent and highlight it for emphasis.

• Any email that is asking the user to complete an action should include a CTA button with a link to the screen most relevant to completing that action. Keep the CTA short (2–3 words) and action-focused.
• CTAs should include a one-time login token unless the destination involves user management or organization configuration changes (for example, SSO configuration).

All emails should contain the universal footer.