Skip to main content

Review & testing

Use the Review tab of the Email Workspace to make sure an email is ready before it goes anywhere. The tab brings together pre-flight checks, test sends, accessibility, and your final ESP sync.

Pre-flight checks​

Every revision runs through your organization's email checks: subject and preheader, content and brand, links and images, accessibility, HTML and size, and AI review of the rendered email. The panel also tracks the workflow essentials — valid module fields, a current revision, resolved comments, and required approvals.

Warnings are advisory; blocking failures hold up export until they're fixed, dismissed, or overridden. See Pre-flight checks for the full walkthrough, including AI findings in the preview and how overrides work.

In-editor preview​

The first layer of QA is the live preview in the Edit tab. Use it to spot:

  • structure and order
  • mobile behavior
  • content length and image crops
  • segmented variants

This is the fastest way to catch obvious issues while you're still building.

Test sends​

When you need to see the rendered email in a real inbox, send a test from the Review tab. Test sends are useful for double-checking subject lines, preview text, and client-specific quirks before the final sync.

Inbox and multi-client preview​

For deeper QA, the Review tab supports inbox-based testing and multi-client preview. Validate how the email behaves across desktop, web, and mobile clients without sending real campaigns.

note

Enterprise-only feature: Inbox and multi-client preview are available on Enterprise plans.

This is especially important for templates that use:

  • advanced layout patterns
  • complex imagery
  • tight typography constraints
  • segmentation variants

Accessibility auditing​

Accessibility is part of pre-flight, not a separate step. Checks cover alt text (both presence and whether it actually describes the image), color contrast, heading structure, minimum font size, descriptive link text, and layout table semantics. Your admin chooses which of these run and how strict they are — see Email checks.

Accessibility review is easiest when it starts at the template level, but it's still valuable at the campaign level.

Sync to your ESP​

Once checks pass, sync directly to your connected ESP from the Review tab — or download the rendered HTML for a custom workflow. See Integrations for ESP-specific details.

Best practices​

  • Use the in-editor preview early and often.
  • Always check mobile before asking the team for feedback.
  • Send a test for critical campaigns.
  • Use multi-client testing for important launches or complex layouts.
  • Treat accessibility as part of QA, not a final afterthought.