Skip to content
Operations7 min read

A Better Way to Test Email Before It Reaches Customers

Test in the right order: automated output checks first, then a controlled inbox look - never the customer list.

By The Memo Team

Last updated

Quick answer

Test email in two layers: automated preflight on compiled output, then a controlled internal test send to a real inbox - prefixed, rate-limited, and never pointed at your audience.

There are two kinds of email testing. Automated checks of the artifact. A human look in a real inbox. You need both, in that order.

Check the output first

Before any send, preflight should confirm variables, links, images, accessibility, and weight. Eyeballing an email with a broken unsubscribe link wastes everyone’s time.

Then look at it in a real inbox

A controlled test send puts one QA copy in front of a real client render - internal only, clearly marked, rate-limited.

Keep testing contained

  • Test sends go to internal recipients, never to an audience segment.
  • Prefix and label so tests are never mistaken for production mail.
  • Limits and idempotency prevent accidental floods.

Test send is not A/B testing

Memo test send is QA confidence, not experimentation infrastructure. Campaign testing still lives in your ESP.

Example (fictional): A reviewer test-sends a [TEST] copy to herself, confirms the hero on mobile, approves - without touching the customer list.

Frequently asked questions

What is a test send?
A controlled delivery of one email to internal allowlisted recipients for QA - not a campaign blast.
Preflight or test send first?
Preflight first. Fix mechanical failures before you spend an inbox check.
Can test send replace Litmus or Email on Acid?
No. Inbox previews and device labs complement test send; they do not replace automated link and variable checks.
Does Memo send to customers?
No bulk send. Test send is internal QA only. Production mail goes through your sending platform.