Skip to Content
Email MarketingOverview

Email Marketing

Send branded email — marketing campaigns, transactional sends, password resets, order confirmations — from your own domain. Recipients see dkim=pass against your brand instead of ours.

What you can do

  • Authenticate your sender domain — publish 3 DNS records once; we sign every send with your domain
  • Build templates with the visual editor — drag-in blocks (heading, image, button, footer), live preview, save once and reuse forever
  • Send campaigns — pick a template, pick an audience (segments + contacts), schedule or send now, watch open + click rates roll in live
  • Transactional APIPOST /public/email/send from your backend for one-to-one sends (OTP, receipts, password resets)
  • Built-in compliance — RFC 8058 one-click unsubscribe header on every send, suppression list enforced at send-time, hard-bounce auto-remove

Pricing

  • First 100 emails per UTC day are free — counter shared across marketing + transactional + public API
  • Beyond that:
    • Marketing emails: ₹0.10 / email + reseller markup (if any)
    • Transactional emails: ₹0.05 / email + reseller markup (if any)
  • Charges show in Settings → Track Expenses  as email_marketing and email_transactional line items, alongside your WhatsApp / RCS deductions

Plan-gated

Email Marketing requires a plan with the Email Marketing feature enabled.

  • Trial users get full access during the trial window
  • Paid users need their plan’s Email Marketing flag enabled (admin sets this on the plan)

If you see “Email Marketing requires an active plan” when opening /email, ask the platform admin to enable the flag on your plan.

How to start

  1. Connect your sender domain — publish 3 DNS records on the domain you want to send from. Takes 5 min to publish, < 15 min to verify.
  2. Build a template — open the visual editor, add blocks, save.
  3. Send a campaign — pick template + audience, click Send.

Or if you want to send transactional email from your backend, jump to the Send Email API  reference.

Architecture

Every email goes through the same pipeline regardless of source:

Your action (campaign / API / template send) We pre-render the template HTML (react-email cross-client output) We sign with your domain's DKIM key We deliver direct to recipient's MX server (STARTTLS, no third-party SMTP relay) Recipient sees: From <you@your-domain.com>, dkim=pass, spf=pass

The sender side is fully self-hosted — we don’t relay through Resend / SES / Mailgun. Your domain reputation is yours.

Compliance built in

  • One-click unsubscribe — every email carries List-Unsubscribe + List-Unsubscribe-Post: One-Click headers (RFC 8058). Gmail and Outlook show their native Unsubscribe button automatically.
  • Suppression list checked at send-time — once a recipient unsubscribes, they’re suppressed for your account. New campaigns can’t re-mail them.
  • Hard bounces auto-suppress — invalid mailboxes added to your suppression list immediately so you don’t keep hitting them and damaging reputation.
  • Footer is required — every template’s Footer block auto-injects company name, mailing address, and unsubscribe link. Required by CAN-SPAM (US) / GDPR (EU) / DPDP (India).

See also