StatusPulse StatusPulse
← All features

Branding · Business

Custom Reply-To for alert emails

Subscribers reply to alert emails. By default those replies bounce off donotreply@. Set a Reply-To and they land in your help desk where someone can actually answer.

Why you need it

Per-status-page CustomAlertReplyTo field attaches a Reply-To header to every alert + incident notification email. The envelope sender stays as our verified ACS box (deliverability holds) — only Reply-To changes.

  • One config field per status page. Settings → Basic. Enter a single email address; leave blank to use the platform default.
  • Header-only change. SPF / DKIM / DMARC alignment on outbound stays on our verified domain — no DNS work needed.
  • Soft-validated. Malformed values (no @, too long) get logged + ignored so the email still ships with the default reply destination instead of bouncing.

Where it pays off

Anywhere subscribers expect to talk back:

  • Customer help desk. support@acme.com routes into Zendesk / Intercom / Freshdesk — replies become tickets.
  • Ops shared inbox. ops@acme.com for internal coordination on customer-facing comms.
  • Personal name during launch. marcelo@acme.com for the first 50 customers — every reply is a relationship-building opportunity.

Not the right tool when: you need full SPF / DKIM domain delegation so alerts send from your domain. That's a separate workstream — Reply-To is the header-only quick win.

Available on Business. Already on StatusPulse? See the full config in Help →

Related

Try Custom Reply-To for alert emails in StatusPulse

5 probes, 1 status page, forever. No credit card. US or EU host — you choose.

Start free See pricing