Skip to content

Branding and domain

Set your portal branding, put the portal on your own domain with two DNS records — verification and HTTPS are automatic — and send mail from your own provider.

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. The organisation owner or a primary-workspace admin manages them.

The cleanup paths are the exception to the active-plan rule: brand Reset, logo removal, and domain removal stay available on a lapsed plan, so a downgraded org is never locked out of tidying up its own white-label.

Branding

Settings → Branding sets:

FieldEffect
App nameThe product name in the dashboard and in emails
LogoUploaded in the dashboard — no need to host it yourself
Primary colourThe accent across the portal
Email from nameThe display name on transactional email
Email reply-toThe reply address
Support URLWhere your clients' help link goes
Powered byShow 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.

Note:

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. 1
    Claim the bare hostname, e.g. support.acme.com. It becomes pending and the card shows the two DNS records to publish.
  2. 2
    Publish both records at your DNS provider: a CNAME from your hostname to whitelabel.evoriqa.com, and the TXT ownership proof — host _sw-domain-verify.<your-domain>, value the token shown. Only a proven domain resolves to your brand, so a pending claim can never hijack another organisation's.
  3. 3
    That's it. Evoriqa re-checks DNS every couple of minutes and the card walks itself from Add the DNS records to Issuing HTTPS… to Live — while only one record has landed, the badge names the missing one (Waiting for the TXT record / Verified — add the CNAME). The certificate is issued automatically, with no proxy or TLS work on your side.
The Custom domain card listing the CNAME and TXT records to publish, each with a copy button
The Custom domain card listing the CNAME and TXT records to publish, each with a copy button

Apex domains can't take a literal CNAME — use your provider's ALIAS/ANAME or CNAME flattening. Full detail, including what a custom domain does not change, is on Custom domains and the widget.

A live domain serves invite-only auth: no "Sign up" link, and only accounts inside your organisation can sign in on it. Opening self-serve sign-up is a separate switch — see Client sign-up.

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. 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. 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. 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.

Note:

TLS is required on credentialed SMTP. Custom SMTP accepts the standard submission ports — 25, 465, 587, and 2525. On a credentialed STARTTLS port (587, 25, or 2525) the connection must upgrade to TLS: if the server strips the STARTTLS offer, the send fails rather than dropping to cleartext, so passwords and links are never sent in the clear. Port 465 is implicit TLS and needs nothing extra.

Warning:

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