Custom Domains for Your White-Label Voice AI Client Portal: Setup, DNS and the Mistakes That Leak Your Stack (2026)
TL;DR: Put your voice AI client portal on a subdomain you own, like portal.youragency.com, not on a vendor URL and not on your root domain. Create one CNAME record at your DNS provider, keep it DNS only (no proxy) until the certificate is issued, wait for it to resolve, and only then send client invites. Then close the other white-label leaks: login emails, the browser tab title, the favicon and the invoices. I build production voice agents for US clients on Retell, n8n, GoHighLevel and Twilio, and we run VoiceDash, where a custom domain is included on every plan. This is the setup I use and the mistakes I see most.
The custom domain is the smallest technical step in white-labeling a voice AI product and the one clients notice first. The very first thing a new client sees is the link in their welcome email. If that link points at a vendor's domain, the client starts asking who that vendor is before they have heard a single call.
Why the domain matters more than the logo
You can upload a logo in thirty seconds, and most agencies do. The domain gets skipped because it involves DNS, and DNS feels like an IT ticket. That is backwards. The domain does three jobs the logo cannot.
It sets trust before login. A client clicking portal.youragency.com is clicking your link. A client clicking a vendor subdomain is clicking a stranger's link, and the more careful clients (medical practices, law firms, anyone with a compliance person) will forward it to someone to check. I wrote about that buyer in voice AI agent security, and the portal URL is part of the first impression.
It keeps the white label intact. Agencies that sell AI receptionists as their own product usually do not want clients googling the underlying platform and comparing prices. The full picture of what to hide and what to disclose is in how to white-label Retell AI. A vendor URL in the address bar undoes most of that work.
It is an asset you own. If the portal lives on your domain, the bookmark, the saved password and the link in the client's team wiki all point at you. That matters for retention, which I cover in voice AI client retention, and it matters if you ever change tools behind the scenes.
Pick the right hostname
Use a subdomain, not your root domain
Your root domain (youragency.com) already serves your marketing site, and your email almost certainly depends on records there. Pointing the root at a portal is how agencies take their own website offline. Use a subdomain. Nothing on your main site or inbox changes.
Names that work
Short and boring wins. Clients will type it from memory on a phone.
| Hostname | Good for |
|---|---|
portal.youragency.com |
The default. Clear, neutral, works for every client |
app.youragency.com |
When you position the agent as your own software product |
clients.youragency.com |
When you also have an internal app on app. |
dashboard.youragency.com |
Fine, but long to type |
Avoid putting "ai", "voice" or a platform name in the hostname. If you add SMS follow-up or chat later, the portal name should still fit.
One agency domain vs one domain per client
Almost every agency I talk to should start with one agency subdomain and let each client log in there to their own scoped workspace. Clients see their own logo and colors inside, and you manage one DNS record instead of twenty. Separate per-client domains sound premium, but they mean a DNS change on the client's side every time, which turns a ten-minute onboarding into a week of chasing their IT person. Save that for the occasional enterprise client who insists, and check what your portal plan supports before you promise it.
The DNS setup, step by step
The exact target value comes from your portal's settings screen. In VoiceDash, connecting a custom domain is part of the branding step, alongside your logo and colors. The steps around it are the same at every registrar.
1. Find where your DNS actually lives
This trips people up more than anything else. The place you bought the domain is not always the place that answers DNS. If you moved your site to Cloudflare, Vercel or a website builder years ago, the nameservers probably point there. Look up your nameservers first and edit records wherever they point. Editing records at the registrar while Cloudflare runs your DNS does nothing, and you will wait an afternoon for a change that never lands.
2. Create the CNAME record
Add a new record:
- Type: CNAME
- Name / Host:
portal(just the subdomain part; most providers add your domain automatically) - Target / Value: the hostname your portal settings give you
- TTL: automatic or the lowest option offered
A common typo is entering portal.youragency.com as the name, which some providers turn into portal.youragency.com.youragency.com. If the record looks doubled in the list, fix it.
3. Turn the proxy off if you use Cloudflare
If your DNS is on Cloudflare, set the record to DNS only (grey cloud), not proxied (orange cloud). A proxied record hides the real target, so the portal provider often cannot verify the domain or issue a certificate for it. You can experiment with proxying later if you have a reason to. Most agencies never do.
4. Wait for it to resolve, then verify
New records usually resolve within minutes, though DNS can take longer depending on old TTLs and caches. Check it from outside your own network with a public DNS lookup tool rather than your laptop, which may be caching an old answer. Once the record resolves, verify it in your portal settings and give the HTTPS certificate time to issue.
5. Test like a client before you send anything
Open the portal URL in a private window on your phone, on mobile data. Log in with a test client account. Check that the padlock shows, that your logo loads, and that nothing on the page says anything other than your brand. Only then send real invites. The rest of my first-week checklist is in how to onboard voice AI clients.
The mistakes I see most
Sending invites before the domain works. The client's first click hits a certificate warning and they assume they are being phished. You do not get that first impression back. Set the domain up before the first client, not during onboarding.
An existing record on the same name. If portal already has an A record or an old CNAME from a tool you stopped using, the new record will fail or conflict. Delete the old one first.
CAA records blocking the certificate. Some domains have CAA records that only allow one certificate authority. If the certificate will not issue and everything else looks right, check for CAA records and ask whoever set them up.
Changing the domain after clients have bookmarks. Moving from app. to portal. six months in breaks every saved link and password manager entry. Choose once. If you must change it, keep the old record pointing at the portal while clients move over.
Letting the domain registration lapse. Your portal now depends on your agency domain renewing. Turn on auto-renew and keep the payment card current. It sounds obvious until it happens.
Close the other white-label leaks
A custom domain fixes the address bar. A few other places can still show a vendor name, and clients do notice.
- Login and invite emails. Check the sender name and the email body of a test invite. The client should see your agency name, not the portal vendor.
- Browser tab title and favicon. Open the portal and look at the tab. Your brand should be there, not a default icon.
- Invoices and receipts. If you bill through the portal, the invoice should come from your business. With VoiceDash, client billing runs through your own Stripe account, so invoices, receipts and the card update flow carry your business, and payments go straight to you with no cut taken. My setup for plans, minutes and overages is in how to bill voice AI clients.
- Call recordings and transcripts. These come from the voice platform, but clients play them inside your portal on your domain, so the platform name never needs to appear.
- Your own sales material. Screenshots in proposals should show the portal on your domain. A vendor URL in a screenshot is a leak too.
What a client actually sees when it is done right
The welcome email comes from your agency. The link reads portal.youragency.com. The login page has your logo. Inside, the client sees only their own agents, calls, recordings, transcripts, analytics and usage. Nothing mentions Retell, and nothing suggests the client is looking at anyone else's software. That is the experience I describe in white-label dashboards for Retell AI agencies, and the domain is the piece that holds it together.
Build it yourself or use a portal
If you are building your own portal, custom domains are one of the parts people underestimate: domain verification, certificates per domain, renewals and the support load when a client's DNS is misconfigured. I break down the full cost in build vs buy a voice AI client portal.
If you would rather skip that, VoiceDash includes a custom domain on Starter, Growth and Ultimate. You connect your Retell account, add your logo, colors and domain, create a client and share the link, all in under 10 minutes with no code. VAPI and Bland support is coming soon, so if you run agents there today, keep that in mind before you plan around it.
The bottom line
The domain is a ten-minute task that decides whether your client portal feels like your product or someone else's. Use a subdomain you own, create one CNAME, keep the proxy off, verify before you invite anyone, and then close the email, tab and invoice leaks.
If you want your Retell clients on portal.youragency.com this week, start your free trial of VoiceDash or book a demo and I will walk through the domain setup with you live.