DPDP deadline: May 2027 · 220 days left Get your business ready in 15 days, done for you Learn more →
Home / Managed Ops / Messaging for SaaS INDUSTRY FILE · MSG-02
MSG-02 / INDUSTRY: B2B SAAS & PRODUCT

Messaging that keeps magic links, dunning and product alerts in the inbox

Magic-link auth emails that land in Gmail primary. Usage alerts that reach the admin before a bill spike. Invoice reminders that recover 40-60% of failed annual renewals. In-app push that respects OS-level throttling. Incident status pages that fan out to email + push + SMS + Slack. Built by a team running 6+ SaaS products of its own.

Chat with Deci Send Requirements →
99%+Inbox placement rate
40-60%Failed renewal recovery
6+Own SaaS products live
DualEmail vendor failover
FILE 01 / WHERE SAAS MESSAGING BREAKS

Magic links go to spam. Dunning fails silently. Product notifications train users to mute the app.

Every SaaS ships email in a hurry. First it is SendGrid free tier for signup emails. Then Postmark for transactional. Then a marketing team lands and pipes broadcast through the same domain. Six months later the sender reputation is trashed, magic-link emails land in Gmail promotions, and a support engineer is spending Friday evenings resending confirmation codes from an admin panel.

Dunning is the second silent tax. Every annual card renewal has a 12-18 percent first-attempt failure rate. Most SaaS wire a Stripe smart-retry and stop. The recoverable percentage sits at 15-25 without a proper email + in-app + CS handoff sequence. A tuned dunning flow gets that to 45-65 percent recovery. On $2M ARR that is $80-120k of net-new revenue that was already earned and is being left on the table.

Then product notifications. Slack-style mention emails, someone-shared-a-doc emails, weekly digests. Teams ship each one as a one-off. There is no central preferences layer. Users get 8 emails an hour and eventually filter the entire domain to trash. Later, when a real security alert or billing failure needs their attention, the email lands in the same muted folder. Fixing this requires an event router, not another feature.

PROOF OF WORK

We run 6+ SaaS products with the same stack

Dcomply (compliance OS), Fluxeta (creator OS), VakeelSaathi (legal OS), RealZent (brokerage OS), SignupDesk (event registration), Dpublish (digital publishing). Every one ships magic-link auth, usage alerts, invoice recovery, product notifications and incident status through the same messaging layer. We eat what we cook.

See our products
FILE 02 / WHAT WE BUILD

Six messaging flows every B2B SaaS needs wired correctly

FLOW-01 · 99%+ inbox rate

Magic-Link + OTP Auth

Domain auth done properly (SPF + DKIM + DMARC + BIMI). Dedicated warmed IP for auth stream. Fallback to SMS OTP for users whose email is muted. Under 5-second median delivery to Gmail, Outlook, Zoho, ProtonMail.

FLOW-02 · Zero bill-shock tickets

Usage + Threshold Alerts

Watch metering events. Fire alerts at 70 / 90 / 100 percent of plan limits, with a link to upgrade or cap. Prevents bill-shock support tickets and captures upgrade intent. Per-workspace admin-only routing.

FLOW-03 · 40-60% recovery

Dunning + Invoice Recovery

14 days pre-renewal (soft reminder + card check), 3 days (retry warning), day-of (attempt), day-of + 3h (retry), day-of + 24h (email + banner + CS handoff). Wired into Stripe, Chargebee, Razorpay.

FLOW-04 · One preferences layer

Product Notifications Router

Event bus + user preferences + channel deduplication. Mentioned in a comment, shared a doc, assigned a task all flow through one router. Push for urgent, email digest for batch, in-app inbox for history.

FLOW-05 · Sub-minute fan-out

Incident Status + Alerts

StatusPage-style feed with subscriber management. Email + web push + SMS + Slack + Teams + webhook fan-out. Automated incident detection from your Prometheus / Datadog. Post-mortem draft template.

FLOW-06 · Push acknowledgement tracked

Web + Mobile Push

FCM for Android + web, APNS for iOS, OneSignal or Novu as fallback. Silent-hours per user, OS-level throttling respected, action buttons for common responses. Deep-links back to the exact in-app location.

Losing renewals to dunning? Or magic links to spam?

15-min call. Send us your current stack (email vendor, dunning provider, push infra). We come back with a delivery audit and a fixed plan to recover the leakage in 48 hours.

Chat with Deci
FILE 03 / TECH STACK WE USE

Vendors and providers we operate every day

Boring, battle-tested pieces that compose into a messaging layer your team can operate six months from now. No lock-in on the routing layer, so you can swap any vendor without a rewrite.

STACK-01

Transactional Email

Postmark · Amazon SES · SendGrid · Resend

STACK-02

Push Notifications

Firebase Cloud Messaging · Apple APNS · OneSignal · Web Push (VAPID)

STACK-03

SMS Fallback

Twilio · MSG91 · AWS SNS · BookMySMS

STACK-04

Routers & Preferences

Novu · Knock · Custom Postgres router · Temporal workflows

STACK-05

Billing & Dunning

Stripe Billing · Chargebee · Razorpay Subscriptions · Paddle

STACK-06

Status & Observability

Atlassian StatusPage · Instatus / BetterStack · Datadog / New Relic · Grafana + Loki

FILE 04 / COMPLIANCE & DELIVERABILITY

Gmail + Yahoo bulk rules, GDPR, DPDP, SOC 2 audit trails

Since February 2024, Gmail and Yahoo enforce hard rules on bulk senders. If you send more than 5,000 emails a day to Gmail addresses you need SPF, DKIM, DMARC alignment, a one-click unsubscribe header on marketing, spam complaint rate under 0.3 percent, and no phishing-like link patterns. Fall out of compliance and Google bounces the whole domain. We set up all six requirements at go-live and monitor complaint rates weekly.

GDPR obligations: legal basis for each message type (contract for transactional, legitimate interest for product updates, consent for marketing), DPAs with vendors, right-to-erasure across message logs. Postmark, SES and SendGrid all have DPAs we know how to sign. DPDP (India): consent capture at signup, purpose limitation, breach notification wiring, opt-out synced across email + push + SMS.

SOC 2 auditors want message audit trails. Every send logged with recipient, template, timestamp, provider, delivery outcome, opens and clicks (where applicable). Retention configurable per message type. We ship the audit query interface so your compliance team stops emailing engineering every quarter for reports.

Deliverability checklist per go-live ● WHAT WE COVER

  • ✓ SPF + DKIM + DMARC + BIMI setup and monitoring
  • ✓ Dedicated IP warming over 2-3 weeks
  • ✓ Separate streams for auth vs product vs marketing
  • ✓ Inbox placement testing on 8+ providers
  • ✓ Complaint + bounce monitoring with alerts
  • ✓ One-click unsubscribe per RFC 8058
  • ✓ SOC 2 audit trail for every send
FILE 05 / PRICING

Setup + monthly ops + specialty modules

ONE-TIME

Setup & Onboarding

Domain auth, dedicated IP warming, magic-link + transactional templates, event-to-channel routing, first go-live.

₹1.75 L
MONTHLY

Managed Deliverability

Bounce + complaint monitoring, IP reputation tracking, template A/B, inbox placement tests, dunning tuning.

From ₹65k/mo
PACKAGE

Incident Status + Push

StatusPage-style feed, subscriber management, multi-channel fan-out, post-mortem automation. Setup + first quarter.

₹1.25 L
SPECIALTY

Dunning + Invoice Recovery

Failed-payment recovery sequence wired into Stripe / Chargebee / Razorpay. Retry logic + in-app banner + CS handoff.

₹85k

Per-message vendor costs (pass-through): Postmark $1.25 per 1000 emails / SES $0.10 per 1000 / SendGrid from $19.95/mo / FCM free / OneSignal from $9/mo / Twilio SMS $0.079 per US SMS, MSG91 India from ₹0.15 / SMS.

This page covers SaaS specifics. For the full service — channels, gateway management, AI monitoring and how engagements run — see Messaging & Notification Systems →

REF-A Parent & Related
REF-B Messaging by Industry
REF-C Product & Proof
FILE 06 / FIELD MANUAL — FAQ

Questions SaaS founders ask on the first call

Which email provider should a B2B SaaS use, Postmark, SES or SendGrid?
Depends on volume and mix. Postmark is our default for pure transactional (auth, receipts, invoices) because separate transactional and broadcast streams keep the transactional IP clean. Amazon SES is 8-10x cheaper per email and fine if your team can operate reputation properly. SendGrid works if you need marketing + transactional in one place with dedicated IP. For SaaS above 5M sends per month we usually recommend Postmark for critical transactional plus SES for lower-priority notifications, with a shared template layer we build on top.
Why do magic-link emails land in spam?
Three usual reasons. First, missing or misconfigured DMARC. Gmail and Yahoo now reject unauthenticated bulk email outright. Second, the domain has no reputation, or you are sending from a shared IP with a noisy neighbour. Third, the email content trips filters (single link, no plaintext version, no unsubscribe header even though it is transactional). We fix all three: proper SPF + DKIM + DMARC alignment, dedicated IP warming over 2-3 weeks, hardened templates, and inbox placement testing on the top 8 mailbox providers before go-live.
How do you handle in-app + email + push routing for the same event?
Event-first architecture. Every product event (invoice due, usage threshold hit, mention in comment) flows into a routing layer we build on top of your job queue. Per-user preferences decide which channels fire. Delivery deduplication makes sure the same user is not blasted on email, web push and mobile push simultaneously. Fallback logic: if push is not acknowledged in 30 minutes and the event is high-priority, email fires. All logged for audit and A/B analysis. Works with Firebase Cloud Messaging, OneSignal, Novu, Knock, or a custom Postgres-based router.
Do we need a StatusPage or can we roll our own?
Both work. Off-the-shelf (Atlassian StatusPage, Instatus, BetterStack) covers 80 percent of teams in a weekend and costs $40-$300 a month. Rolling your own makes sense if you have compliance customers who need the status feed inside their VPC, or if you want automated incident detection from your own observability stack. We have built both. The important layer is the subscriber notification pipeline (email + SMS + Slack + Teams + webhook) which is where teams typically underinvest and then get burned during a real incident.
How do you cut dunning failures for annual renewals?
Annual card renewals are the highest-value dunning event. Failure rates run 12 to 18 percent for most SaaS on the first attempt. We wire a sequence 14 days before renewal (soft reminder + card-on-file check), 3 days before (retry warning), day-of (attempt notification), day-of + 3 hours (retry), day-of + 24 hours (email + in-app banner + CS handoff). Combined with Stripe smart retries this recovers 40 to 60 percent of failed annual charges. High-ARR accounts get manual CS outreach instead of automation.
What about GDPR and Indian DPDP for messaging PII?
Both handled. GDPR obligations: legal basis for each message type (contract for transactional, legitimate interest for product updates, consent for marketing), data processing agreements with vendors (Postmark, SES, SendGrid all have DPAs), right-to-erasure across message logs. DPDP obligations (India): consent capture, purpose limitation, breach notification wiring, opt-out honoured across channels. For US SaaS with EU users we also cover CAN-SPAM header requirements and Yahoo / Gmail bulk sender rules effective 2024.
Push or email for real-time product notifications?
Depends on urgency and user context. Web push and mobile push arrive in seconds and are perfect for time-sensitive events (someone mentioned you, ticket assigned, deploy failed). But push has aggressive OS-level throttling and gets muted fast if you spam. Email is slower but gets archived and searchable. Our default: push for user-attributable events with a 24-hour cooldown, email digest for lower-priority events (daily or weekly), in-app inbox for the full history. High-priority always fires both channels.

Stop losing revenue to messaging silence

15-min call. Share your current email vendor, dunning setup, notification stack. We come back with a delivery audit and a fixed plan in 48 hours.

Chat with Deci Send Requirements →