Onboarding & lifecycle

Walk the whole onboarding journey — one persona per address.

Lifecycle email is a sequence, not a single send: verify, welcome, invite a teammate, get a receipt, reset a password, receive a digest. Testing it with one shared account means every run pollutes the last. Reclario gives you a private catch-all domain for $49/mo per domainnewuser+trial@yourteam.reclar.io exists the moment you send to it, so each persona walks its own journey from step one.

newuser+trial@yourteam.reclar.io verify+expired@yourteam.reclar.io billing+receipt@yourteam.reclar.io reset+password@yourteam.reclar.io
What you can test

Every transactional email you send.

Signup verification

Codes and magic links land in seconds. Read the code, click the link, and check the expired and already-used paths on their own addresses.

Welcome series

Drip sequences are hard to eyeball because they unfold over days. Give the series its own persona and watch every message arrive in one thread.

Team invitations

Invite flows involve two personas and two inboxes. Give both a Reclario address and drive the whole handshake without borrowing a colleague's email.

Receipts and billing

Check totals, tax lines, and PDF attachments in the message a customer actually receives — not in the template preview.

Password resets

Verify the link works, expires when it should, and cannot be replayed. Each scenario gets its own address so state never leaks between runs.

Digests and notifications

Notification batching and digest emails are where rendering breaks first. See the layout, images, and dark-mode behavior as a user would.

How it works

Three steps to a lifecycle you can actually see.

No inbox setup, no DNS, no borrowed accounts. Sign up in your own product with an invented address and follow the mail.

1

Claim a domain

Your team's private catch-all domain — $49/mo per domain, unlimited addresses, nothing public.

yourteam.reclar.io
2

Sign up as a persona

Use a fresh address per journey. Trial user, invited teammate, expired-link case — each one gets a clean inbox.

newuser+trial@yourteam.reclar.io
3

Read what the user reads

Faithful rendering, full headers, attachments, and a raw .eml download for anything you need to inspect closely.

download .eml

See it the way the user sees it.

Transactional templates break in ways a unit test never catches: an image that does not load, a button that collapses, a link that points at staging, a merge field that renders as a literal placeholder. Reclario renders each message in a sandboxed reading pane with headers, cc, and attachments visible — and when you need to go deeper, the raw .eml is one click away, headers and MIME parts intact.

Migrations, incidents, and staging you can't email from.

Three moments make this urgent. Switching email providers, when headers and link wrapping change quietly and the dashboards all look green. After a deliverability incident, when you need proof that mail is landing intact again. And whenever compliance forbids emailing real users from staging — which is most regulated teams, most of the time. In all three, a private domain of disposable personas is the safe way to check. Testing the hiring pipeline instead? See recruiting email testing, or calendar invite testing for scheduling flows.

FAQ

Onboarding and lifecycle email testing, answered.

Can I test verification codes and magic links?
Yes — that is the most common thing people do here. The verification email lands in the inbox seconds after signup, and you can read the code, click the magic link, or pull it out over the API to finish the flow in an automated test. Expired-link and reused-link paths are just two more addresses.
Will emails render like a real client?
Messages render faithfully in a sandboxed reading pane — images, styling, and layout as a user would see them — with headers, cc, and attachments visible. For byte-level checks, download the raw .eml and inspect it yourself.
Can I test after switching ESP?
Yes, and it is a good reason to. Migrating from one email provider to another quietly changes headers, link wrapping, tracking pixels, and sometimes rendering. Send the full lifecycle to a set of Reclario addresses on the old provider, repeat on the new one, and compare the delivered mail rather than the dashboards.
Is it safe for staging data?
Yes. Your domain is private by default — unlisted, unsearchable, readable only by teammates you invite. That matters when compliance forbids emailing real users from staging, and it is the reason public throwaway inboxes are not an option for lifecycle mail carrying names, receipts, or reset links.
Can I automate it?
Yes — API keys and webhooks let CI mint addresses, wait on delivery, and assert on the message, so a broken welcome series fails a build instead of a customer. More on that in email testing for QA.

Test the emails your product sends every day.

Claim a private catch-all domain for $49/mo per domain — or walk your first signup through the free public sandbox at public.reclar.io (work email required, no credit card). Comparing tools? See email testing tools compared.

Start free  See pricing