Email-sending domain

By default, every email the portal sends to your clients goes out from the platform's configured default sender. Clients see the platform domain, not yours. Configuring your own sending domain replaces that with you@yourdomain.com for every outgoing email, quote notifications, invoice receipts, contract reminders, the lot.

Why bother

• Branding. Every email shows your own domain in the From address instead of the platform's. Your business name shows either way; the domain completes the picture.
• Trust. Clients open emails from a domain they recognize, especially clients behind strict corporate mail gateways.
• Replies work the same either way. When a client replies to email you composed, the reply lands in the Inbox at /admin/email and a copy is forwarded to your own mailbox, with or without a domain. A domain only changes the From address the client sees.

Setting it up

Go to Settings → Email Domain.

Add the domain

Type the domain you want to send from (e.g., acmeplumbing.com, or a subdomain like mail.acmeplumbing.com). The form accepts common variations and sanitizes them:

• https://acmeplumbing.com becomes acmeplumbing.com
• acmeplumbing.com/ becomes acmeplumbing.com
• acmeplumbing.com:443 becomes acmeplumbing.com

The portal trims protocols, trailing slashes, paths, ports, and stray leading or trailing dots before saving. Whatever you paste, you'll get the bare domain back.

If you've previously registered this domain in Resend under a different account (common when an old setup got abandoned), the portal will detect that and adopt the existing Resend record instead of creating a duplicate. You'll see a green confirmation that says the domain was reattached.

Add the DNS records

Once you've saved the domain, the portal generates the 4-5 DNS records you need to add at your registrar:

1. DKIM TXT at resend._domainkey.<your-domain> — proves outbound messages are signed by you.
2. SPF MX at send.<your-domain> — points at feedback-smtp.us-east-1.amazonses.com with priority 10.
3. SPF TXT at send.<your-domain> with value v=spf1 include:amazonses.com ~all — authorizes the sending service.
4. DMARC TXT at _dmarc.<your-domain> (optional but recommended).

Open your DNS host's control panel (Cloudflare, Namecheap, Route 53, GoDaddy, etc.) and add each record exactly as the page shows. Keep TTL at "Auto" if your provider supports it; otherwise 3600 seconds is fine.

Verify

Click Verify in the portal. The portal calls Resend's verification API which checks all the records you added.

DNS propagation can take a few minutes to a few hours depending on your registrar. If verify fails on first try, wait 5-10 minutes and try again. If it still fails after an hour, double-check the record values exactly match what the portal showed.

Once verified, the page shows a green "Verified" badge and saves the verification timestamp.

What the From address looks like

The full From header is "<your-brand-name>" <fromuser@yourdomain.com>. The brand name is always your business name (set on Settings), even when the email is going out under the platform's shared sender. That way the client sees your business in their inbox preview pane, not a generic platform name.

You control two parts:

• fromName — what's in quotes in the From header. Defaults to your business name. Override on the email-domain settings page if you want a different display name (e.g., "Acme Plumbing Support" instead of just "Acme Plumbing").
• fromUser — the local part of the email address (the bit before the @). Defaults to portal. Change it to hello, support, billing, or whatever fits your brand.

Composing email to a client

The main place to write clients is the email hub at /admin/email. Click Compose, pick who it goes to in the To field, and add CC recipients if you like; both fields offer the client's own address plus their saved contacts. Your email signature is added to the bottom automatically (the signature editor is on the same page). The message goes out with your business branding and sender domain. When the client replies, the reply lands in the hub's Inbox and a copy is forwarded to your own mailbox.

You can also write a client directly from their page: open the client, then the Email tab. It works the same way, with the same sending and the same replies to the Inbox. A blank line starts a new paragraph, and lines starting with - or 1. become lists.

Below the composer is a history of every email the portal has sent that client: composed messages, invoices, and notifications alike.

When something goes wrong

The email-domain page surfaces errors as banners at the top, not as dropped form data. When something fails, you'll see an error from the mail service passed straight through, such as:

• A message that the domain is already in use by another account. Resend allows one domain across all accounts. If you used the domain previously in a different Resend account, the portal will offer to adopt it for you (single click). If the domain belongs to someone else entirely, you'll need to free it on the other account first.
• A message that the DNS records don't match. Your record values don't match what the mail service expects. Double-check spelling, especially the DKIM record (it's a long string and one character off invalidates the whole thing).
• A message that verification is still in progress. The mail service is still checking. Wait 5-10 minutes and refresh.

The exact wording comes from the mail service, so it may vary. The DNS records the page shows you to add are likewise generated by the mail provider and can differ from one domain to the next.

When you re-submit the form after an error, the field stays filled in with whatever you typed — you don't lose your work to the banner.

Without a verified domain

You can use the portal without configuring a sending domain at all. Everything delivers with no setup: email goes out from the shared portal address with your business name shown, and client replies still land in your /admin/email Inbox with a copy forwarded to your mailbox. A domain is a branding upgrade, nothing more. It changes the address clients see, and it can't break your email: if your domain ever has a problem, sending falls back to the shared address automatically.

The Email Domain settings page shows how your email works right now, and if you don't own a domain yet, it helps you buy one (typically $10-15 a year). Setup is a one-time job that takes about 20 minutes including the DNS propagation wait.