Connect a portal domain and sending email domain

Serve your client portal and send email from your own domain, verified with a few DNS records you add at your domain provider.

This is available to Agency workspaces.

Before you start

You'll need access to your domain's DNS settings at whichever company you registered it with (for example GoDaddy, Namecheap, Cloudflare, or your IT provider). You're adding records there — The platform never asks for your registrar login.

Two separate connections exist, and you can set up either or both:

• Client portal domain — your clients sign in at your own URL instead of the default one. A subdomain is recommended (for example app.youragency.com); a root/apex domain (for example youragency.com) also works.
• Sending email domain — call summaries and notifications go out from your own email address (for example hello@youragency.com) instead of the default one.

Connect your client portal domain

Click to enlarge

1. In the sidebar, click Agency, then open the Domains & Email tab.
2. On Client portal domain, click Set up portal domain.
3. Under Domain, enter the domain your portal will be served on (for example app.youragency.com) and click Continue. If your domain resolves anywhere already, you'll see a warning explaining that pointing it here replaces whatever it currently serves — read it before continuing.
4. You'll see one DNS record to add:

Most DNS providers want the Host shown, not the full domain — they add your domain automatically. The page shows the relative form and lets you copy it with one click. If you're on a root/apex domain, add an A record at @ instead of a CNAME.

5. If Vercel also asks for an ownership TXT record (shown as a second row, host starting with _vercel), add that one too — it's usually only needed the first time.
6. Add the record(s) at your DNS provider, then return here and click Done.
7. Wait for the badge to read Verified. It updates on its own — you can close the page and come back. To check sooner, open View setup and click Recheck.

Connect your sending email domain

Click to enlarge

1. On Sending email domain, click Set up email domain.
2. Enter the Domain you'll send from (for example youragency.com) and the From address local part (for example hello, making hello@youragency.com). Click Continue.
3. You'll see four required DNS records and an optional DMARC record:

The first four records (the TXT ownership record and the three DKIM CNAMEs) are required for verification. The DMARC record is optional — it improves deliverability but doesn't block verification, and if your domain already has a _dmarc record, keep the one you have instead of adding a second (only one is allowed).

4. Add the records at your DNS provider, then click Done.
5. Wait for Verified, or open View setup → Recheck.

What the status badges mean

• Waiting for DNS — no record has been detected yet.
• Propagating… — records were found; verification is finishing.
• Verified — live. Your portal or sending domain is active.
• Needs attention / Failed — something about the records doesn't match. Open View setup, compare each row against what's actually in your DNS, and fix any mismatch.

DNS changes typically take a few minutes but can take up to 24–48 hours to fully propagate, depending on your provider. The page checks automatically, so there's no need to keep it open.

Common mistakes

Copy each record exactly as displayed in your setup, including provider-owned target domains. The examples here explain record shapes; they do not replace the values generated for your domain.

• Wrong host value. Most DNS providers expect only the part before your domain (what the page shows, for example app or _amazonses), not the full domain again. Only use @ for a root-domain record.
• A instead of CNAME, or vice versa. A subdomain (app.youragency.com) needs a CNAME. A root domain (youragency.com) needs an A record. The page tells you which one to add based on what you entered.
• Skipping the ownership TXT record. If Vercel shows a second record starting with _vercel, both records are required — adding only the CNAME leaves the domain unverified.
• Missing a DKIM record. All three CNAME rows for email must be added — partial DKIM won't verify.
• Editing an existing domain instead of removing it first. You can't edit a connected domain's value directly. Open View setup, click Remove, then add the domain again with the correct value.
• "This domain is already connected to another workspace." Someone else on the platform has already connected this exact domain. Contact support — don't create a different domain to work around it.

If a record doesn't verify

1. Open View setup and compare each row, character for character, against what's saved in your DNS — copy-paste rather than retype.
2. Confirm you added the record type shown (TXT vs CNAME vs A) — some providers default to the wrong type if you paste a full value into the wrong field.
3. Check you haven't accidentally added the record twice, or added it at the wrong subdomain.
4. Click Recheck. If it's been more than 48 hours and the status hasn't changed, contact support with the domain and which record is failing.

What changes for your clients once a domain is live

• Portal domain verified: your clients open their workspace at your domain rather than the default one. Invite links and demo links also switch to it.
• Email domain verified: call summaries and notifications send from your address instead of the default one.

Removing a domain reverts both back to the platform default immediately.

Related: Brand your portal, Configure notifications, Share a demo.