Overview
Whitelabel lets you replace the default brand with your brand: installation name, logos, accent colors, icons and your own domain. The result is a platform that looks entirely yours to your team and your end customers.
Whitelabel configuration is done at the platform operator/administration level (it's not a per-customer-account preference), because it affects the look of the whole installation.
Prerequisites
- Operator/super administration access to the platform (or a request to whoever runs the installation).
- Ready brand assets: light and dark logo, icon/favicon, color palette.
- For a custom domain, access to that domain's DNS.
Step by step
- Access the platform administration panel (super admin).
- Open the brand/whitelabel configuration.
- Set the installation name shown across texts and titles.
- Upload the logos (light/dark) and the icon/favicon.
- Adjust the accent colors to match your visual identity.
- Configure the custom domain (and certificate), pointing DNS per the instructions.
- Save and verify in an incognito tab, checking logo, colors and page title.
Settings & options
The panel has two independent names: Installation name controls login and page titles; Brand name identifies the brand in emails and the widget. For a consistent identity, use the same spelling in both fields. Spaces are allowed. Custom names are preserved when the platform's default files are updated.
Enabling an account's white label feature hides attribution on supported surfaces; it does not fill identity fields or automatically replace logos. Configure each field in the super admin panel and save. Remove Powered by hides attribution across the installation.
The panel does not configure DNS, certificates, email senders or the identity of mobile apps already distributed. Colors affect compatible components; compiled legacy styles may need separate changes. Script-based colors and CSS require Custom Scripts to be enabled. Manually entered content and images containing the old brand are not rewritten. Reload pages after saving and check login, emails, the widget and Help Center separately.
The ConversaLabs identity is configured through light/dark logos, the symbol, favicons and installation icons. Files uploaded in the whitelabel panel take priority over defaults: updating default files does not replace an existing upload. Check both logo versions, the super administration login and the icon after reloading.
- Installation name: replaces product references in the interface and emails.
- Logos and icon: appear on login, in the sidebar and in the browser tab.
- Colors: align the interface with your identity.
- Custom domain: uses your URL instead of the default domain.
Share card
In Public sharing, set a Public description of up to 300 characters (160 is recommended), an optional Share title and, when needed, a Share image URL. When the title is empty, the platform uses the Installation name. When the public description is empty, the platform retains its standard public description, independently of the installable-app setting. The image URL must be public HTTPS; the server does not download or test that image. When it is empty, the card reuses the managed brand icon when one is available.
The recommended image reference is 1200 × 630 px. The panel preview confirms the values published in HTML, but it does not confirm when WhatsApp, social networks or other services will refresh their own caches. Validate the published HTML and treat a remote card refresh as a separate step.
Use cases
- An agency delivering the platform as its own product to clients.
- A company that wants its support hub with the corporate identity.
- Standardizing emails and login screens with the company brand.
Tips, limits & best practices
- Use logos with a transparent background and versions for light and dark themes.
- Test on small screens: the icon and name also appear on mobile.
- After changing the domain, confirm that links (including this Help Center) remain valid.
- Do not put personal data, tokens or management links in the public description, title or URL.
Troubleshooting
- I can't find the whitelabel options: they live in platform administration — ask the installation owner for access.
- The logo didn't update: clear the browser cache and reload; confirm the upload was correct.
- The custom domain won't open: review the DNS pointing and certificate per the instructions.
Browser icons and upgrades
Public survey, payment, contract and widget pages use the same browser icon as the panel.
The Help Center keeps its own portal logo when configured; without one, its tab follows the
installation icon. The legacy /favicon.ico address redirects to that resolved icon without
caching it. A customized installation with no usable icon gets no default product icon.
Only HTTP(S) URLs and safe local paths are accepted; unreadable branding configuration does not break
these pages. The API viewer allows the icon's exact storage origin, without allowing other
external image origins.
After an upgrade, existing managed branding scripts receive the content produced by the current brand settings. Disabled scripts stay disabled, deleted scripts are not recreated, and targeting and recorded incidents remain intact. An unchanged script is not saved again. With no configured script-based branding, the upgrade does not touch scripts. Saving in the whitelabel panel remains the explicit way to create or reactivate managed scripts.