churnhook
Email branding

Email branding

Logo, footer, sending domain, and a receipt line so customers recognize their plan.

One brand for every recovery email

Settings → Messages → Email. Recovery emails are wrapped in the same layout: your logo, your organization name (optional), and a short footer. Set them once — every template inherits them.

The Preview button renders a real recovery email with your current settings, including sample subject and body. Nothing is saved until you click Save.

Plan, price, and due date

Every recovery email adds one muted line automatically after your copy, with the plan, cycle price, and the customer's due date while they're still billed (the due date drops on win-back, since the subscription is already canceled). You don't insert anything yourself — this line comes straight from that customer's Stripe subscription. The same line appears on the offer, pause, keep, and portal pages those emails open. Its language follows Ticket language on Settings → Churnhook, not the dashboard language. Template, brand, and run Preview windows show a sample of that line in the same language.

Sending domain

Recovery emails can leave from your own domain instead of churnhook. Only the owner can set this up.

  1. Type a hostname (for example billing.example.com) and pick a sending region.
  2. Set domain shows the DNS records to add at your DNS provider.
  3. Click Check. While verification is pending, churnhook also re-checks automatically every 30 seconds.

Once every record is verified, your recovery emails send from your domain; until then, they keep leaving from churnhook. Signup confirmation and password-reset emails always stay on churnhook, in churnhook's look — not your logo or sending domain.

If your domain is verified but a later send is rejected by your DNS provider, that step fails instead of silently falling back to churnhook — so customers never see the wrong sender.

Recommended: DMARC

Once the domain is verified, Settings flags DMARC as Recommended. Configure DMARC offers a record that lowers the chance your emails land in spam or show as sent "via" another brand. Sending still works without it, but it's worth setting up.

If a _dmarc record already exists, don't add a second one. Otherwise, stay on the most permissive policy (p=none) until you've reviewed the reports.