Notifications & Messaging

Make every message feel intentional — not noisy

Azotte helps you design, trigger, localize, and deliver customer communications across the subscription lifecycle. From “payment failed” to “price change notice” to “trial ending” — every message is consistent, compliant, and tied to the exact lifecycle event that caused it.


What you can send

  • Lifecycle messages: welcome, activation, renewal, cancellation, pause/resume, grace period, expiration
  • Billing messages: invoice created, receipt, refund, chargeback/dispute updates
  • Dunning messages: payment failed, retry scheduled, last attempt warning, access at risk, recovered
  • Price change consent & notices: pre-announcement, consent request, reminder, confirmation, post-change receipt
  • Campaign messages: promo confirmation, redeemed code, reward earned, referral milestones
  • Security & trust messages: suspicious activity, new device/session, policy changes (optional)

Where you can deliver it

  • Email
  • SMS
  • Push notifications
  • In-app inbox / message center (optional pattern)
  • Webhook to your own messaging stack (if you already have one)

Azotte doesn’t force a single provider — you can plug in your preferred messaging vendors per region/storefront.


Event-driven, not “manual send”

Azotte messaging is triggered by real subscription events, not by human workflows:

  • Payment attempt changes state → notify customer and support flows
  • Trial approaches end date → remind at the right time window
  • Subscription renewal scheduled → confirm and reduce surprise
  • Price change planned → run a compliant notice sequence automatically
  • Customer cancels → confirm immediately + optionally start a save flow

Templates that scale across regions and products

  • Template library: reusable layouts for common events
  • Localization-ready: language-specific content per storefront/region
  • Dynamic placeholders: customer name, bundle, price, currency, renewal date, next retry date, consent deadline, etc.
  • Per-storefront branding: sender identity, tone, footer/legal text, unsubscribe rules

Personalization without complexity

  • Segmentation-aware messages (e.g., region, customer type, channel, risk tier)
  • Context-aware content (e.g., “your in-app subscription” vs “your card payment”)
  • Timing windows (e.g., “3 days before renewal”, “24h before last retry”)

Compliance and customer trust built in

  • Consent-aware flows for sensitive cases (like price changes)
  • Audit trail: what was sent, when, to whom, and why (which event triggered it)
  • Frequency guardrails: avoid accidental spamming from rapid event loops
  • Fallback logic: if a channel fails (or is unavailable), switch to another channel

Connect messaging to recovery and retention

Notifications aren’t just “status updates” — they’re levers:

  • Pair dunning notices with retry schedules and “update payment method” CTAs
  • Use cancellation confirmations to trigger save offers (Campaign & Offer Engine)
  • Use renewal reminders to reduce involuntary churn and support tickets
  • Use price change sequences to increase acceptance and reduce charge disputes