White-Label Domain & Branding Setup

White-Label Setup

Three things turn your organization into a fully branded platform: a custom domain, your branding, and your own SMTP server. Domain and SMTP are required for a production setup; branding can be refined at any time.

1. Custom Domain

Your customers log in on your own domain (e.g. chat.your-agency.com). The setup wizard at Account → White-Label Setup walks you through it:

Enter your domain — a subdomain like chat.your-agency.com is recommended.
Create a DNS record at your DNS provider:
Type Name Value TTL
CNAME chat.your-agency.com connect.webchatagent.com 300
Click Check DNS now. Once the record has propagated (usually minutes, up to 24 h depending on your provider), the domain is marked Verified.

Type	Name	Value	TTL
CNAME	`chat.your-agency.com`	`connect.webchatagent.com`	300

The TLS certificate for your domain is issued automatically on the first visit — no certificate upload needed.

The domain must point directly at connect.webchatagent.com (DNS only). If you use Cloudflare for your own zone, set the record to "DNS only" (grey cloud), not proxied.

Once verified, the domain appears in Settings → Account with a green badge and your platform is reachable at https://chat.your-agency.com.

2. Branding

Under Settings → Account → Branding you control how the platform looks for your customers:

Field	Used in
Platform name	Browser title, dashboard header, all emails
Logo	Dashboard sidebar, login page, email header
Favicon	Browser tab
Primary color	Buttons, links, accents across the dashboard
Powered-by text & URL	Optional attribution line in the chat widget
Email footer text	Footer of every email sent to your customers
Imprint & privacy URLs	Legal links in emails — point these at pages on your own website

Changes apply platform-wide after saving.

3. SMTP (your own email server)

All emails to your customers — invitations, password resets, notifications — are sent through your SMTP server with your sender address. This is mandatory: without a working SMTP configuration, no emails are sent for your organization (the platform never falls back to its own sender, since that would leak the platform identity and break SPF/DKIM).

Configure it under Settings → Account → Email / SMTP:

Field	Example
SMTP host	`smtp.your-domain.com`
Port	`587` (default)
TLS/SSL	depending on your server
Username / password	your SMTP credentials
From name	`Your Brand`
From address	`noreply@your-domain.com`

Use Send test email to verify the configuration before inviting customers.

Make sure SPF/DKIM records for your sending domain include your SMTP provider — otherwise your invitations may land in spam.

4. Widget embedding under your brand

The widget script served from your domain uses brand-neutral element tags — give your end customers snippets with <chat-widget> (floating) or <chat-agent-inline> (inline), loaded from your white-label domain:

<script src="https://chat.your-agency.com/widget/chat-widget.js" async></script>
<chat-widget chatbot-id="THEIR_CHATBOT_ID"></chat-widget>

The same applies to Session Context Data: besides the neutral context-data attribute, the widget accepts the brand-neutral JavaScript names window.chatWidgetContext (global variable, may be set before the script loads) and the chat-widget:context event. For cookie consent, the neutral event chat-widget:consent works alongside the branded one. Document these neutral names for your end customers — their pages never need to reference the platform.