Branding and domain

Set your portal branding, verify a custom domain with a DNS TXT record, and send transactional mail from your own provider account.

Reseller and agency accounts only

White-label covers three separate things: the portal's look, the domain it runs on, and where its email comes from. Each is configured on its own, and all three require an active reseller plan. Organisation owner only.

Branding

Settings → Branding sets:

Field	Effect
App name	The product name in the dashboard and in emails
Logo	Uploaded in the dashboard — no need to host it yourself
Primary colour	The accent across the portal
Email from name	The display name on transactional email
Email reply-to	The reply address
Support URL	Where your clients' help link goes
Powered by	Show or hide the badge

The logo and colour render across the whole portal — the dashboard chrome and the pre-login pages — and emails already carry your logo.

Reset clears the styling only: app name, logo, colours, and the badge go back to defaults. The custom domain, support URL, and email sender deliberately survive a reset, because they are operational wiring rather than styling — a reset never breaks a client's live domain or your mail deliverability.

Per-chatbot widget branding — colour, avatar, greeting, badge removal — is separate and set on each bot's Appearance tab.

Custom domain

Settings → Custom domain brands the portal on your own hostname:

1
Claim the bare hostname, e.g. support.acme.com. It becomes pending and a
verification token is issued.
2
Publish the TXT record shown — host _sw-domain-verify.<your-domain>, value
the token — and choose Verify. Only a verified domain resolves to your brand, so a pending claim can never hijack another organisation's.
3
CNAME the hostname to the deployment and add it to your reverse proxy or
hosting platform so a certificate is issued.

evoriqa does not terminate TLS or issue certificates for custom domains. Full detail, including what a custom domain does not change, is on Custom domains and the widget.

Email delivery

By default transactional mail — verification, invites, lead notifications, digests — is sent by the platform. Your name and reply-to are applied, but the From domain remains the platform's, because the envelope still leaves the platform's provider.

To remove it entirely, configure your own mail provider under the organisation's mail settings:

1
Pick a provider preset — Resend, SendGrid, Mailgun, Postmark, Brevo,
Mailjet, SparkPost, Amazon SES — and paste its credentials, or choose Custom SMTP. Credentials are encrypted at rest; custom hosts are vetted.
2
Activate with a test send. Saving marks the config pending; a branded test
email goes to the organisation owner and the config activates only if it succeeds. Up to 5 tests per hour.
3
Configure SPF and DKIM for your sending domain at your provider.

Once active, every branded send routes through your provider and leaves from your address.

Delivery telemetry ends at the SMTP handshake — sent or failed. There is no bounce or complaint feedback, so monitor deliverability at your provider rather than in evoriqa. A lapsed reseller plan falls back to the platform sender rather than dropping mail.

Where to go next

Last updated 8 August 2026