Serve your website chat widget, iframe and shareable agent link from your own subdomain. Learn how CNAME setup works, what it covers and what it doesn't.
Your customers see your brand on every page of your site, then a chat widget loads from a hostname that belongs to someone else. For security-minded buyers, corporate firewalls and brand-conscious teams, that mismatch raises questions. This article explains what publishing chat on your own domain means, how the DNS side works, and how to set it up in AI SNS CHAT without surprises.
Why host chat on a domain you control
A chat widget is a small piece of third-party software running on your website. By default, the script, the iframe and any shareable link point at the platform's hostname. A custom domain swaps that hostname for one of yours, such as chat.yourshop.com.
The reasons teams do this tend to fall into four groups:
- Brand consistency. The link a customer clicks or shares starts with your name, not a vendor's.
- Trust. People are more willing to type an order number into a page on a domain they recognise.
- Network policy. IT teams in larger companies often maintain allow-lists of hostnames. A subdomain of your own company domain is easier to approve than a new vendor domain.
- Portability. If you ever change vendors, links you printed, emailed or put in QR codes still use your hostname, and you only repoint DNS.
None of this changes how the AI answers. It changes where the chat is served from and what the customer sees in the address bar and in page source.
What a custom domain does and does not cover
It helps to be precise about scope, because "my own domain" can mean different things to different people.
In AI SNS CHAT, a verified subdomain covers three things:
- The embed script you paste into your website.
- The iframe version of the chat.
- The agent link, the shareable page for your agent.
What it does not cover matters just as much. If you also run the agent on WhatsApp or Messenger, those conversations still happen inside WhatsApp and Messenger, on Meta's apps and under Meta's names. Your domain has no role there, and nothing about those channels changes when you add a domain. The same is true of Telegram, LINE, SMS and the other messaging channels. You can see the full list of connections at /connections.
The last row is the one people most often misunderstand. A custom domain is about your web-facing chat, not about the messaging apps your customers already use.
Choosing the right subdomain
You connect a subdomain, not your bare root domain. That is normal for CNAME-based setups, and it is also good practice because your main website keeps working exactly as it does today.
Some naming patterns that work well:
chat.example.comfor a general-purpose assistanthelp.example.comfor a support-oriented agentask.example.comfor a conversational, question-first tonesupport-jp.example.comorsupport-uk.example.comwhen you run separate agents by market
A few practical rules:
- Pick a name you will not regret. Once you print it on packaging or put it in a QR code, you will want it to stay stable.
- Do not reuse a hostname that already serves something. If
help.example.comalready points to a knowledge-base tool, choose a different name or plan a migration. - One agent, one subdomain is the simplest mental model. If you manage several agents, decide up front which hostname belongs to which.
- Keep it short and readable aloud. Staff will say it on the phone.
If you run agents for several brands or clients, the same pattern repeats per agent, and each one gets its own subdomain under the relevant company's domain.
How the DNS side works
DNS setup is the part that makes non-technical teams nervous, but the concept is small. A CNAME record is an alias. It tells the internet: "when someone asks for chat.example.com, treat it as if they asked for this other hostname." The platform then recognises requests arriving under your name and serves your agent.
Verification is then a DNS lookup. The platform checks whether your subdomain's CNAME is in place and points where it should. If the lookup finds the record, the domain is verified. If it does not, you get the opportunity to fix it and check again.
- 01Choose a subdomain
- 02Add the CNAME at your DNS provider
- 03Verify by DNS lookup
- 04Use the new script, iframe and link
Where the record is added
You add the CNAME wherever your DNS is managed. That is usually one of these:
- your domain registrar's control panel
- a dedicated DNS host
- your cloud provider's DNS service
- your IT department or agency, if they control the zone
If you do not have access, the quickest path is to send the person who does two things: the exact subdomain you want and the CNAME target shown on the setup screen.
Common reasons verification fails
- The record has not propagated yet. DNS changes can take anywhere from minutes to hours to be visible everywhere. Wait, then check again.
- The hostname was typed with a typo or with the domain repeated. Some DNS panels automatically append your domain, so entering
chat.example.comcan turn intochat.example.com.example.com. Check how your panel treats the name field. - A conflicting record already exists. A subdomain generally cannot have a CNAME alongside other record types for the same name. Remove the old record first.
- The target was copied with extra spaces or the wrong value.
A safe rollout plan
Switching hostnames on a live site is low-risk when done in order. A sensible sequence:
- Finish the agent first. Test it in the Playground, tidy your knowledge sources, and confirm the welcome message and handoff behaviour.
- Add and verify the subdomain without touching your live website yet.
- Open the agent link on the new hostname and test it from a phone and a desktop browser, including a network that is not your office.
- Update the embed on a staging page or a low-traffic page of your site.
- Roll out site-wide once you are satisfied.
- Update anywhere the old link was published: email signatures, QR codes, help-centre articles and social profiles.
Step 6 is where teams usually leave stragglers, so keep a list of every place the link appears.
A simple planning example
Suppose, hypothetically, that a shop publishes its agent link in five places: the website footer, order confirmation emails, a printed leaflet, a social profile and a help-centre article. Each of those is a separate edit. If the team only updates the website, three of the five will keep showing the old hostname. A short checklist, one line per location, costs ten minutes and avoids that.
Pairing a custom domain with other trust signals
The domain is one signal among several. These pair well with it.
- Branding. Widget studio includes remove-branding, and there is a paid add-on called "Remove Powered by AI SNS IO" if you want your chat to carry no platform mark. Your hostname and a clean widget together make the experience feel native.
- Access control on shared links. The shareable agent link can be protected with a password or per-user sign-in, and it can be restricted to your office network. This is useful for internal assistants, such as an HR or IT helper, that should live on a company hostname but never be public.
- Message protection. Per-agent prompt-injection and abuse filters and per-device rate limits protect the agent regardless of the hostname it is served from.
- Clear security information. If a customer or a procurement team asks how data is handled, point them to /security, where practices are described as designed with reference to GDPR and APPI. The site is also explicit that it is not SOC 2, ISO 27001 or HIPAA certified, so do not describe it that way in your own materials.
Mistakes to avoid
- Treating the domain as a channel. It does not put your agent on WhatsApp or Messenger. Those are separate connections.
- Forgetting about plan limits. Custom domains need the Hobby plan or higher. Check /pricing for current plan details, since prices are read at runtime and an admin can change them.
- Using a root domain. Plan on a subdomain.
- Deleting the DNS record later by accident. During a DNS clean-up, an unfamiliar CNAME looks like clutter. Leave a note in your DNS provider's comment field if it has one, or document it in your internal wiki.
- Skipping a test on mobile. A large share of web chat happens on phones, and a link that works on your desktop may behave differently on a mobile browser or inside an in-app browser.
- Changing the hostname after publishing it widely. Decide once.
Doing this in AI SNS CHAT
Custom domains are set up per agent, so the steps below apply to each agent that needs its own hostname. You need the Hobby plan or higher.
- Open the agent. From the dashboard, select the agent you want to publish.
- Go to Agent → Settings → Custom domains. This is where the domain is added and checked.
- Enter your subdomain. Use a subdomain such as
chat.yourcompany.com. The screen shows the CNAME details you need. - Create the CNAME at your DNS provider. Add the record exactly as shown. If someone else manages your DNS, send them the subdomain and target.
- Verify. AI SNS CHAT confirms the domain with a DNS lookup of the CNAME. If it is not found yet, wait for propagation and try again.
- Use the new hostname. Once verified, the subdomain covers the embed script, the iframe and the agent link. Update your site's embed and any places where you published the link.
Before you go live, a few related settings are worth checking:
- Channels → Chat widget to review how the widget behaves, and Widget studio for appearance and the remove-branding option.
- Channels → Help page if you also want a standalone support page for the agent.
- Shareable link options if the link should be password protected, require per-user sign-in, or be limited to your office network.
- Agent security settings to review prompt-injection and abuse filters.
- Helpdesk → Scheduling so handoffs go to whoever is on shift, with the customer-facing message generated from your rota rather than an invented wait time.
If you run several agents, repeat the process per agent and give each its own subdomain. If you are not yet on a paid plan, you can start from /signup and explore the rest of the platform on the plan you have, then upgrade when you are ready to publish on your own hostname. A fuller overview of what is included is at /features.
Frequently asked questions
Does a custom domain also change how my WhatsApp or Messenger chats look?
No. A verified subdomain covers the embed script, the iframe and the agent link. WhatsApp and Messenger conversations stay inside those apps, so your domain is not involved. You connect them separately under Channels.
Which plan do I need?
Custom domains are available on Hobby or higher. The Free plan does not include them. Check the pricing page for the current plan details, because prices are loaded at runtime and can be changed by an administrator.
How does AI SNS CHAT know my domain is set up correctly?
It verifies the subdomain with a DNS lookup of the CNAME record. If the record is missing, mistyped or has not propagated yet, verification does not pass. Correct the record, wait a little, and check again.
Can I use my root domain, like example.com, instead of a subdomain?
The feature is built around a subdomain CNAME, so plan on something like chat.example.com. This also keeps your main website untouched, since only the subdomain points to the chat.
Can I keep my agent link private while using my own domain?
Yes, as a separate setting. The shareable link can use a password or per-user sign-in, and it can be limited to an office network. That makes it suitable for internal assistants that should sit on a company hostname without being public.


