Docs / Merchant guide
Email Studio & sending domains
Customizing every outbound email and verifying your own sending domains.
Email Studio (owner-only) lets you customize every email WallaB.AI™ sends on your behalf, with a live preview rendered by the exact same engine production uses.
Templates you can customize
- Sign-in code — the portal one-time passcode email.
- Win-back offer — the one-tap reactivation email.
- Payment notice — the dunning retry email.
- Final payment notice — sent when the retry ladder is exhausted and the subscription goes on hold.
- Card-expiry warning — the pre-dunning heads-up.
- Renewal reminder — the pre-charge heads-up: an advance notice of a pay-as-you-go subscriber's next renewal date and amount, sent shortly before the charge (default on; lead time in Settings → Renewal reminders).
- Personalized payment-notice variants — used only when "Personalized dunning emails" is turned on in Settings; WallaB picks the variant per customer: the first payment retry note, the gentler long-time subscriber note, the second payment notice, the firmer repeat payment failure notice, and the backup card notice (sent when a backup card was charged after the primary failed). With the setting off, the standard payment notice above is always used.
- Weekly digest — your own merchant performance summary.
- Welcome and post-save check-in — sent by automated workflows.
- Surprise gift notice — the "a little something extra is on its way" email sent AFTER WallaB grants a subscriber a genuine, unadvertised $0 Over-Deliver gift (never dangled during the cancel flow).
- Milestone thank-you note — the Over-Deliver "Moment": a warm, unadvertised thank-you email sent at a subscriber tenure milestone when you set that milestone's action to send a note (Settings → Over-Deliver). It carries no offer, no discount, and no buy-now link — pure appreciation.
- Subscription confirmation — the always-on transactional email a shopper gets right after subscribing. It lists what they subscribed to (products, quantity, delivery cadence, and the per-cycle total when available) and carries their portal link. Unlike the Welcome workflow (an opt-in), this one always sends — the portal link placeholder is required, so shoppers can always reach self-serve management.
Shopper-facing templates render in the shopper's language automatically. Saving is guarded: a template that fails to render cleanly against sample data is rejected rather than saved broken. You can send yourself a real test email from the editor at any time.
Sending domains
By default, email sends from WallaB.AI's shared domain. You can send from your own domain instead — a branded From address that improves deliverability and brand trust. Set it up on the Settings → Email → Sending domain card (owner-only). Here is what actually happens:
- Enter a subdomain like
mail.yourshop.comand click Set domain. WallaB registers it with our email provider (Mailgun) on your behalf — you do not need a Mailgun account of your own. - Publish the DNS records WallaB shows you. These are a couple of TXT records (SPF and DKIM authentication) and a CNAME, each with its name, type, and value. Add them at your domain registrar or DNS host; the card has a Copy button on every row.
- Verify. Click Verify DNS and WallaB checks whether the records have propagated. In sandbox mode this completes instantly; with real DNS, propagation can take anywhere from a few minutes to a few hours, so a "not verified yet" result right after publishing is normal — wait and verify again. The card shows the live status: unverified → pending → verified.
- Once verified, all transactional email (sign-in codes, payment notices) and win-back sends go out from your domain with a branded From address. If verification ever lapses, or you replace the domain, WallaB automatically falls back to the shared WallaB.AI domain — a send is never dropped for a missing or unverified domain.
Marketing broadcast domain — an optional, SEPARATE subdomain (e.g. mkt.yourshop.com) that pure-marketing broadcast campaigns send from, so campaign volume can never affect the deliverability of your payment and sign-in email. It uses the same set-DNS-then-verify flow. If unset, broadcasts fall back to the shared WallaB.AI marketing domain, then to your primary domain — win-back and transactional email always use the primary domain, never the marketing one.
Suppression
Marketing email honors your suppression list automatically. Transactional email (payment notices, sign-in codes) is account-lifecycle mail and is always delivered.