Skip to content

Custom domains: portal yes, widget no

A custom domain brands the portal with automatic HTTPS; the widget script stays on app.evoriqa.com. Setup, the status ladder, and lapse behaviour.

Reseller and agency accounts only
Warning:

Read this before planning work around it. A custom domain brands the portal — the dashboard, the pre-login pages, and emails. The widget script is always served from app.evoriqa.com, and there is no setting that serves it from your own hostname.

What is and is not white-labelled

SurfaceCarries your domain or brand?
The dashboard your clients log in toYes, with a verified custom domain
Pre-login pages on that hostYes
Transactional emailsYes — sender name, reply-to, logo
The widget's appearanceYes — colours, avatar, and the "Powered by" badge, per chatbot
The widget's script URLNo — always https://app.evoriqa.com/widget.js
Google sign-in on your domainNo — password sign-in only; Google stays on the platform

So a visitor who views the page source of your client's site sees an app.evoriqa.com script URL. Everything they see rendered — colours, avatar, badge — is yours to control on Appearance.

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

  1. 1
    Claim the hostname in Settings → Custom domain — a bare host such as support.acme.com. The card shows the two DNS records to publish.
  2. 2
    Publish 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 TXT proves 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 literal CNAME — use your provider's ALIAS/ANAME or CNAME flattening instead.

  3. 3
    Wait. 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, 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

Last updated