Setting up a dedicated email subdomain

By default, Katalyz sends notifications from "Katalyz" no-reply@mail.katalyz.co. A dedicated sending domain lets those emails come from your own domain instead — e.g. rooms.yourcompany.com — which improves deliverability and trust. Setup is self-serve from Settings → Workspace → Email delivery.

⚠️ Requires org role Admin and access to your company's DNS records (or support from IT). Included in the Core plan.

Why set this up

Without a dedicated domain:

• Emails come from @mail.katalyz.co (a third-party vendor to your buyers)
• Corporate email gateways (Proofpoint, Mimecast, etc.) flag third-party senders more aggressively
• Your open rates and click-through rates suffer

With a dedicated domain:

• Emails come from yourcompany.com — inheriting your brand's sending reputation
• Buyers recognize the sender and trust it
• Delivery rates improve, often significantly

How it works

Katalyz sends through Amazon SES. You choose a subdomain, add a handful of DNS records that authorize Katalyz to send on its behalf, and Katalyz verifies them. From then on every notification — invitations, magic links, comment alerts, signature requests — goes out from your subdomain.

Before you start

• A subdomain name. Use a subdomain, never your root domain (that's reserved for your primary mail). Good examples: rooms.yourcompany.com, notifications.yourcompany.com, hello.yourcompany.com.
• Access to your DNS provider — GoDaddy, Cloudflare, Route 53, etc.

Setup

Open Settings → Workspace → Email delivery. The page walks you through three steps.

Step 1. Choose domain

1. Sending domain — the subdomain buyers will see (placeholder project.katalyz.co).
2. MAIL FROM domain (optional) — the domain used for bounce handling. Leave it empty to use m. + your sending domain (placeholder m.project.katalyz.co).
3. Click Save settings. Saving a new domain resets verification.

Step 2. Set up DNS records

The page generates the records for the domain you saved, each with a Type, a Host / Name and an Expected value / Target, and a Copy button next to every value:

Add them at your DNS provider — or copy them into a ticket for IT.

Step 3. Verify

Click Check status. DNS propagation can take from 15 minutes to a few hours, so the overall Status may stay In progress for a while — click Check status again later. The panel shows Last checked and Verification requested timestamps, plus a Provider checks list with one line each for Domain verification, DKIM and MAIL FROM; each turns SUCCESS as it passes.

If you've changed records and want a clean run, click Restart verification.

Activation

At the top of the page, the Activation toggle (Enabled / Disabled) controls whether Katalyz actually sends from your domain. "When disabled, Katalyz uses the default sender address ("Katalyz" no-reply@mail.katalyz.co)." Keep it disabled until the status is Verified, then enable it.

Test it

Send yourself a room invitation to a personal mailbox outside your company. Check that:

• It arrives (not in spam)
• The "From" address is your subdomain
• SPF, DKIM and DMARC pass (visible in the message headers of most email clients)

Ongoing maintenance

• DNS provider change — re-add the records if you migrate DNS, then Restart verification.
• DMARC policy tightening — start with p=none, move to p=quarantine then p=reject over time.
• Changing the domain — edit Step 1 and save; you'll need to add the new records and verify again.

Troubleshooting

• Verification stuck In progress — DNS propagation takes time. Wait a few hours and click Check status again. Double-check the Host / Name values: some providers want the host relative to the zone (e.g. katalyz._domainkey.rooms instead of the full name).
• Records verified but email still goes to spam — some receiving domains have other rules. See Email is landing in spam.

Related articles

• Notification sender email
• Email is landing in spam
• Connecting Google Workspace
• Connecting Microsoft 365

Updated on: 02/10/2026