Emails and reusable assets

The Emails area is the reusable message library for broadcasts and automations. An email can be drafted and tested independently, then published for delivery workflows.

Create an email

1. Open Emails and choose New Email.
2. Start with Draft with Loop, a blank canvas, imported HTML, or an available template.
3. Add an internal label that identifies the purpose.
4. Set the subject, preview text, sender name, and reply-to address.
5. Build and review the message.
6. Send a test.
7. Publish it when ready for a broadcast or automation.

Publishing an email does not send it. It creates a usable release for another delivery surface.

Content checklist

• the subject and preview text work together
• the opening matches the audience’s context
• claims are supported by the approved source
• merge fields have safe fallbacks
• one primary call to action is easy to find
• required address, preference, and unsubscribe content is present
• the text still makes sense when images are blocked

Image and asset checklist

• appropriate dimensions and file size
• useful alt text
• current brand imagery
• no internal-only or temporary source file
• legible mobile layout
• no screenshot of stale pricing, terms, or product UI

Link review

For each link, confirm:

• link text matches the destination
• the final URL is production, not local or staging
• query or tracking parameters are intended
• the destination works without your authenticated session
• time-sensitive pages will still be valid at send time

Publish and change safely

Before publishing, send a test and inspect desktop and mobile rendering. If a published email is already used by a broadcast or automation, understand whether your change creates a new release or changes a future delivery. The product’s usage indicators show where an email is referenced.

Use clear labels and archive unused emails instead of keeping many ambiguous near-duplicates.

Continue with Plan your first broadcast or Automations.