Custom domains
Put Echo on your own domain
Enterprise teams can map a subdomain to their Echo so chat, catalog, calendar, tip, and links pages feel fully branded.
Overview
Custom domains are built for Enterprise users who need Echo to feel native to their brand. Add a subdomain, create the required CNAME and verification records, and Echo resolves public pages from that host once checks pass. The mapping covers the Echo page plus storefront routes like catalog, calendar, tips, and links. Generated product and catalog links also respect the active custom domain, so conversations do not unexpectedly send customers back to echoai.so when a brand domain is configured.
What you get
- Subdomain mapping - Use ai.yourbrand.com or chat.yourbrand.com for public Echo pages.
- CNAME and TXT verification - A CNAME pointing to echoai.so and a TXT ownership record must both pass before traffic is routed.
- SSL handled - Echo manages the secure serving layer after verification.
- Branded storefront links - Catalog and product links respect the active custom domain.
How it works
- 1. Add your domain - Enter the subdomain you want to use in Enterprise settings.
- 2. Create DNS records - Add the CNAME and verification records shown by Echo.
- 3. Publish branded links - Your Echo and storefront pages resolve on your own domain.
Who it is for
- Agencies - Give client Echos branded subdomains instead of generic platform URLs.
- Established brands - Keep customer trust high when sending catalog and booking links.
Frequently asked questions
Can I use a root domain?
Echo is designed for subdomains like ai.yourbrand.com or chat.yourbrand.com.
Which plan includes custom domains?
Custom domains are available on Enterprise.
Do storefront links use the custom domain?
Yes. Catalog, calendar, tip, and links pages resolve through the branded domain.