People who search for litmus email templates usually want one thing: an email that looks right in every inbox before it goes to the whole list. A broken layout in a client's work inbox costs you more than a weak subject line, because it tells a buyer your firm is careless. This article covers the job behind the search, which is pre-send testing and rendering checks, what to look for in any testing tool, and how to run test sends and checks inside the levelpartner.ai platform before you press send.
What pre-send testing actually protects
Every email client renders HTML differently. Desktop mail apps, webmail in a browser and phone apps each strip, rewrite or ignore parts of your code. A template that looks clean in the builder can arrive with stacked columns, missing images or a button that has turned into plain text.
For a 60-person firm sending a monthly update to a few thousand contacts, one broken send is not a disaster. Ten broken sends a year, each seen by your best clients, slowly erode trust. Testing is cheap insurance against that.
There are four things worth checking on every template:
- Layout: columns, spacing and images hold together on a narrow phone screen.
- Links: every link goes where it should and carries the right tracking.
- Personalisation: merge fields fill in, and fall back cleanly when a field is empty.
- Dark mode: logos and text stay readable when the client inverts colours.
Before you start
You need a finished draft in the platform's email builder under Marketing. You need two or three real inboxes you control, ideally on different providers, plus at least one phone. Add a test contact record for yourself with every merge field filled in, and a second record with the first name and company left blank. That second record is the one that catches embarrassing fallbacks.
How to set it up
- Go to Marketing, Emails, and open your draft template.
- Switch to the Design Editor tab.
- Click Preview and check the Desktop, Tablet and Mobile views.
- Fix anything that stacks badly, such as long side-by-side columns.
- Open the three dots beside Preview and choose Test Email.
- Fill in the sender, receiver, Preview Text and Email Subject.
- Click Send Test Email for each of your inboxes.
- Open each test on desktop, webmail and phone, then in dark mode.
- Click every link and button in at least one copy.
- Click Save Template only when every inbox shows the same email.
Keep a short written checklist pinned in your marketing folder. The person sending on a Friday afternoon will skip steps they have to remember.
What to check when choosing a testing tool
Some teams add a dedicated rendering service on top of manual test sends. If you are weighing one up, judge it on the job, not on its feature list. Ask whether it shows the specific clients your buyers use. A firm selling to corporate finance teams needs accurate desktop mail previews far more than it needs dozens of obscure apps.
Check how it fits your workflow. A tool that requires exporting HTML, pasting it elsewhere and re-importing fixes adds friction, and friction means people stop using it. Check whether it tests links, accessibility and load weight as well as appearance. Finally, ask who on your team will own it. A tool with no owner becomes a cost line nobody can justify at renewal.
For many firms of 10 to 250 people, disciplined test sends to three real inboxes catch the large majority of real problems. A paid rendering service earns its place when you send to many client types, run heavy custom HTML, or have had a visible failure before.
What this replaces and the time it takes
Pre-send testing replaces the habit of sending to the list and waiting for a colleague to reply that something looks odd. Done properly, it takes about ten to fifteen minutes per new template. Once a template has passed, later campaigns that reuse it need only a quick phone check and a link test.
Suppose the marketing lead builds one new template a quarter and reuses it. If testing a new template takes 15 minutes and each campaign after that needs a 5-minute phone check, a year works out at four template tests (one hour) plus 24 phone checks (two hours). That is roughly 3 hours of testing to protect 24 sends to a list of, say, 4,000 contacts. The timings are estimates.
The usual mistake is testing only in the builder preview. The preview shows what the platform intends, not what Outlook on a locked-down corporate laptop will actually display. Always test in a real inbox.
When not to bother
Plain-text style emails from a named person, the kind used in a sales follow up email, rarely break. A quick send to yourself is enough. Heavy testing pays off on designed newsletters and campaigns, such as the layouts in our newsletter template guide. If you want to reduce breakage at the source, start with simpler layouts using the principles in email design principles.
Troubleshooting
Images do not show in the test
Many work inboxes block images by default. Make sure every image has alt text that still makes sense, and never put your main message or call to action inside an image.
The layout collapses on phones
Two or three side-by-side columns with long copy will stack in an unpredictable order. Move to a single column for anything important, and keep columns for short items like logos.
Merge fields show raw code or blank greetings
The contact record is missing data. Set a fallback value for each merge field in the builder, such as "there" for a missing first name, and re-test with your blank record.
Links go to the wrong page
Usually a copied template kept the old links. Click every link in a real test copy, not in the builder, before each send.
Frequently asked questions
Do I need a paid rendering tool to test emails?
Not always. Test sends to three real inboxes on different providers, plus a phone and dark mode, catch most problems. A paid service becomes worth it when you send heavily designed HTML to a wide range of client types.
How many test sends should I do per campaign?
One round per new template across all your test inboxes, and one quick check per later campaign. If you change the layout, treat it as a new template and run the full round again.
Can I reuse templates I built in another tool?
Yes, but rebuild them in the platform's builder rather than pasting raw HTML. Imported code often carries styles that break in some inboxes. Our guide to reusable email templates covers how to structure them.
Who on my team should own testing?
The person who presses send. Testing that depends on a second reviewer tends to get skipped when that reviewer is busy, so make it part of the sender's checklist.