Email proofing for teams means a read-only preview link for approvals, a Test to an address on your account for inbox checks, and same-canvas Team collab only while people are still editing. When the proof is right, export HTML or MJML or push a Zoho Campaigns draft. The real send stays in your ESP.
In Milo Email Studio, the preview link, the Test and the shared canvas all sit next to the drag-and-drop editor.
The "forward me the test" problem
You finish a draft and a founder, brand lead or client wants a look. So you do what everyone does: send yourself a test and forward it, or paste three screenshots into Slack.
It falls apart quickly.
- Screenshots go stale the moment you change a headline.
- Threads fill with replies to the wrong image.
- A forwarded test lives in someone's inbox as a one-off, not as the live proof.
- People who should never touch the ESP end up asking for a guest login "just to have a click around".
Slack ends up as your proof archive, and it's a terrible one. What works better is one link that doesn't change for the people who only need to approve, and a clear owner on the canvas for the people still editing.
Three proof tools (choose by job)
Preview link: the default for approvals
A preview link is a read-only proof of the email. Anyone with the URL can see it, but they can't edit anything, and it doesn't take up a seat in the studio.
You can create the link, copy it, regenerate it when an old URL should stop working, or revoke it when the proof is done.
Use it for founders, brand, legal, clients, or anyone whose job is to say "does this look right?" Drop the link in Slack with one clear request. There's no need to add every approver to Team just so they can say "looks good".
Test send: prove the draft in an inbox
Send the current draft to an address on your account. The subject starts with Test. It's a copy of the draft, so you can check image blocking, dark mode and how it looks in Gmail or Apple Mail right now.
It's just a proof, for checking the draft in a real inbox before you hand it over to your ESP.
Same-canvas Team collab: for editors, not every approver
On Team, two people can work on the same proof. You'll see who's on the canvas (names and avatars), labelled cursors, the same outline when a block's selected, edits as they save, and team chat beside the canvas.
That's for a designer and a marketer rewriting the headline together, not for everyone who just needs to approve. Approvers get the preview link, and editors get the canvas.
A simple team workflow
Each tool has one job, so nobody waits on the wrong one.
One canvas while the draft is moving. Milo's AI designer or a starter (Welcome, Promo, Newsletter, Event or blank) gets you a first draft, and the brand kit keeps the palette, fonts and buttons consistent. If two people are changing the copy or layout, work on the same canvas on Team. Once the draft settles down, stop adding editors.
One link for sign-off. A read-only preview link in Slack with one request ("can you approve the subject and CTA?") keeps the feedback in one thread, pointing at the live email rather than screenshots.
One inbox check before export. A Test to yourself shows what a browser proof won't: images off, dark mode and phone width. The HTML email checklist has the full list.
A clean handoff. Export HTML or MJML for your ESP, or connect Zoho Campaigns and push a draft. If you're still deciding where the design should live, see design then export vs build in your ESP. For a file handoff to another ESP, see how to design a branded email and export.
A last check where the list lives. Unsubscribe and merge tags live in the ESP, so run one last test there before the real send. That's about compliance and your list, not another round of design.
Preview vs test vs ESP campaign
| Preview link | Studio test send | ESP campaign / list send | |
|---|---|---|---|
| Who sees it | Anyone with the link (read-only) | An address on your account | Your list or segment in the ESP |
| Purpose | Stakeholder approval | Inbox proof of the draft | Real send and compliance in the ESP |
| Subject | N/A (web proof) | Starts with Test | Real campaign subject |
| Campaign send? | No | No | Yes |
Questions
What's wrong with "forward me the test"?
A forwarded test is a snapshot, so it's out of date the moment you change the draft. People end up replying to old copies, and anyone without ESP access can't see your updates unless you forward it again.
What is an email preview link?
It's a read-only link to the email that you can share with anyone. Viewers don't get a studio seat and can't edit anything.
How is a preview link different from a test send?
The preview link is a browser proof for approvals. The test is an inbox proof sent to an address on your account, with a subject that starts with Test. When the stakes are high, use both, then hand over export-ready HTML to your ESP.
Where does the campaign go after export?
Once you've exported the HTML or MJML (or pushed a Zoho Campaigns draft), you send the campaign from your ESP.
Can stakeholders approve without an ESP login?
Yes. Send them the preview link, and keep ESP logins for the people who actually send.
When should I use Team collab instead of a preview link?
When someone needs to rewrite blocks with you. If they just need to approve, send the preview link.
When do I still need an ESP test?
After import and before the list send, because merge tags, unsubscribe links and the platform's own preview all live there.
Prefer a head start on the first draft? Ask Milo's AI designer to draft blocks on the canvas, then share the preview link for sign-off.