Custom domains: what carries your hostname
Your clients' portal, widget snippet and channel webhooks carry your domain with automatic HTTPS; your own workspace stays on app.evoriqa.com.
Read this before planning work around it. A live custom domain carries your clients' side of the product: their dashboard, the pre-login pages, their widget embed snippet and channel webhook URLs, and their emails. Your own workspace stays on app.evoriqa.com — its snippet, webhook URLs and every email to you and your staff — because your staff session lives there.
What is and is not white-labelled
| Surface | Carries your domain or brand? |
|---|---|
| The dashboard your clients log in to | Yes, with a live custom domain |
| Pre-login pages on that host | Yes |
| A client's widget snippet and channel webhook URLs | Yes — https://<your-domain>/widget.js, https://<your-domain>/api/… |
| Emails to a client's users | Yes — links on your domain, plus sender name, reply-to, logo |
| The widget's appearance | Yes — colours, avatar, and the "Powered by" badge, per chatbot |
| Your own workspace's snippet, webhooks and links | No — app.evoriqa.com, where your staff session lives |
| Emails to you and your staff | Brand yes, links no — they point at app.evoriqa.com |
| Google sign-in on your domain | No — password sign-in only; Google stays on the platform |
A link to your domain would land a staff member in the client portal, signed out, so staff links always use the platform address. Webhook routes accept either host, so a URL you already pasted with your domain keeps working.
Who can set one
Custom domains are part of white-label and require an active reseller plan. The organisation owner or a primary-workspace admin can manage one. Without a reseller plan the write is refused with a 403. See Reseller overview.
Setting one up
- 1Claim the hostname in Settings → Custom domain — a bare host such as
support.acme.com. The card shows the two DNS records to publish. - 2Publish both records at your DNS provider:
host: support.acme.com type: CNAME value: whitelabel.evoriqa.com host: _sw-domain-verify.support.acme.com type: TXT value: <the token from step 1>The
TXTproves ownership — only a proven domain resolves to your brand, so a pending entry can never take over someone else's. Apex domains (acme.com) can't take a literalCNAME— use your provider's ALIAS/ANAME or CNAME flattening instead. - 3Wait. Evoriqa re-checks DNS every couple of minutes and the card advances from Add the DNS records through Issuing HTTPS… to Live on its own (while one record is still missing, the badge names it). The HTTPS certificate is issued automatically — no reverse proxy or TLS work on your side. Once Live, your clients' snippets, webhook URLs and email links carry your domain too.
While the plan lasts
Branding and the custom domain apply only while the organisation holds a reseller plan. If it lapses terminally, the portal and emails revert to Evoriqa defaults, the domain's HTTPS stops serving, and after a 30-day grace window the hostname is released. Within that window, resubscribing restores everything — brand, domain, and HTTPS — without re-entering anything. A past_due subscription keeps the brand through the dunning window.
Removing a domain stays available to the organisation owner even without a plan, so a stale mapping can always be cleared.
Where to go next
- Branding and domain — the full white-label surface.
- Appearance — the per-chatbot branding that visitors actually see.
Last updated