Password-reset mail going to spam
A user can’t reset their password = a churned account. Worst part is you’ll never see it in your funnel because they bounce out silently.
// for saas product teams
Product email that lands. Password resets, onboarding, alerts, invoices.
When your transactional mail goes to spam, churn goes up. Unspam continuously tests every product email you send: password resets, magic links, onboarding, billing. You know it’s reaching users before they open a support ticket.
The deliverability problems we hear most.
Scaling sends after a launch spike
Going from 10K → 1M emails/month in three weeks is the most common way to wreck a fresh sending domain. Most teams don’t monitor until it’s too late.
Multi-product authentication drift
Marketing, transactional, billing, support: all four often send from the same root domain via different ESPs, each with slightly different SPF/DKIM. One bad include record breaks the rest.
Why teams like yours pick Unspam.
// flow health
Every product email, on its own threshold.
Password resets, magic links, billing receipts: each tracked against its own placement threshold. Cross the line, the on-call gets paged.
TRANSACTIONAL · 4 FLOWS · LIVE
ALERT · 1 FLOW
Password reset
98%
Magic link
89%
Billing receipt
97%
Onboarding · day 1
96%
avg placement · alert threshold 95%
96.5%
// scoring
A score that maps to real placement.
Calibrated against actual delivery outcomes, not a generic spam-filter rule list that has nothing to do with real-world inbox placement.
UNSPAM SCORE · scan #4189 excellent
90 / 100
high deliverability · likely inbox
industry avg · 78 ↑ +12 vs avg
SPF · DKIM · DMARC aligned
+3
12 / 12 links healthy
+1
Missing List-Unsubscribe-Post
−10
HTML / text ratio 1.8
+1
How it works.
01
Test a production send
Trigger a real password reset, magic link, or billing email to the Unspam address. Same path your users hit.
02
Get auth + score + placement
SPF/DKIM/DMARC verdict, spam score with actionable diff, inbox placement per provider.
03
Schedule it across every flow
Autopilot runs daily for each transactional flow so you know the morning a placement issue starts.
04
Wire alerts to your on-call
Alerts go to email or Slack on the same threshold you’d page for an outage. Email-delivery slip = real outage.
A few common workflows.
Product email is infrastructure. When it breaks it’s a silent outage, no PagerDuty page, just users who can’t log in. These are the patterns SaaS teams set up first.
-
Pre-launch deliverability baseline
Three weeks before launch: warm up the domain, verify SPF/DKIM/DMARC across all the sub-domains your stack uses, and lock in a placement number you can compare against post-launch.
-
Continuous transactional monitoring
Daily Autopilot test on each transactional flow: reset, billing, alerts, magic link. Alert page on regression so an on-call engineer sees it before a user complains.
-
Multi-ESP audit
Run a single test against each ESP your product uses (Postmark for transactional, SendGrid for marketing, etc.) and confirm SPF/DKIM/DMARC alignment across the stack.
-
Magic-link reliability check
Test magic-link emails across consumer Gmail and corporate Google Workspace. A 60% inbox rate is a silent login failure for 40% of your users.
-
Recovery from a deliverability incident
After a spike in complaint rates, run daily placement tests to confirm your billing flow is back in primary before the next renewal batch goes out.
-
ESP migration regression testing
Switching from Postmark to Resend? Run before-and-after tests on every flow so reputation regressions don’t ship to production silently.
// FAQ
Frequently Asked Questions
Do you support custom transactional ESPs?
+
Yes: Postmark, SendGrid, Mailgun, SES, Mandrill, Mailjet, Resend, your own SMTP. Unspam tests whatever actually arrives at our seed list; the originating ESP is irrelevant.
How does Unspam help with SPF/DKIM/DMARC alignment?
+
Each test breaks down which mechanism passed/failed/aligned. For multi-ESP setups you’ll see per-message exactly which sender record was used, so you can confirm every ESP is correctly aligned without grep-ing through DNS records. The inbox-placement test tells you whether that alignment actually moves placement on the receiving end.
Can I integrate Unspam into our CI?
+
API access is part of the White Label tier. Talk to us about getting an integration set up. Programmatic test runs let you wire a deliverability check into the same pipeline that ships your transactional templates.
What threshold should I alert on for transactional mail?
+
For password reset / billing / security, anything below 95% inbox placement at the major providers is worth paging on. Promotions/marketing tolerates more. Set the threshold per flow inside Unspam.
Does this replace my ESP’s deliverability dashboard?
+
Different layer. Your ESP shows what it accepted, bounced, complained on. Unspam shows where the accepted mail actually went at the receiving end, inbox vs spam vs promotions. They’re complementary.
// ready when you are
Product email is an outage when it doesn’t land.
Free placement test on a real production send. Wire up Autopilot in five minutes.