White label: what must really disappear for the end client and their visitors
Real white label goes beyond swapping a logo. Here is what visitors and end clients should never see, and where blabla.bot stands on each point today.
Agencies and white label5 min read
“White label” is an easy promise to put on a landing page. In many tools, it boils down to replacing a logo and a colour. What remains is a “powered by” line at the bottom of the chat, an error message naming the vendor, or an email sent to the client with the platform’s name on it.
For an agency reselling an AI assistant under its own brand, every one of those details matters. Your client pays your agency, not a third-party vendor. Their visitors talk to the assistant of their business, not to a product they have never heard of. This article lists what really has to disappear, and states plainly what blabla.bot does today on each point.
Two audiences, two requirements
Two different people are involved.
- The visitor to your client’s website opens the chat, asks a question and reads the answer. They should only ever see your client’s brand.
- The end client is the business you equip. They should see your agency as their provider. Depending on your commercial choice, they may or may not know which technology you use.
The requirements differ. The visitor must not be able to guess anything about what happens behind the scenes. The end client should get useful information (consumption, answer quality) without the underlying platform stepping into the relationship.
What the visitor must never see
The platform’s brand
The blabla.bot widget does not display the blabla.bot brand. There is no mandatory “powered by” line. The appearance follows the client’s identity: a preset (Clean, Soft or High contrast), a main colour, the client’s logo, the launcher position, the greeting and up to three suggested questions.
Only one credit line exists, and it is off by default: “Assistant set up by” followed by your agency’s name. Turn it on if you want to sign your work for visitors.
Internal information
The visitor must never learn which AI model is used, what the conversation costs, your credit balance, or the instructions you wrote for the agent. None of that is sent to the widget.
The reason for an outage
This is the point most often overlooked. When your credit balance runs out, or a site’s monthly budget is reached, the assistant has to stop answering. A message such as “insufficient credits on the agency account” would be a disaster for your client.
In that case, blabla.bot shows the visitor a neutral message: the service is temporarily unavailable, please try again later. The actual reason only appears in your console.
Sloppy visuals
A white label that is hard to read hurts as much as a foreign logo. The widget checks the contrast between the text and the chosen main colour: below 4.5:1 (the AA level of the WCAG accessibility guidelines), publishing is blocked and a corrected shade is suggested. Logos are accepted as PNG, JPEG or WebP.
What the end client should not have to deal with
Platform invoices
blabla.bot bills your agency, and only your agency. Each credit top-up comes with an invoice in your name. Your client receives nothing from blabla.bot: you bill them yourself, at the price and on the terms you choose. You set your resale price freely.
Emails in the platform’s name
Today, blabla.bot sends no email to your clients. Consumption alerts are addressed to your agency.
What is still to be built, openly
Complete white label covers more than the widget and billing. Here are the points we do not consider settled, so you can factor them into your offers.
| Item | Current status |
|---|---|
| Widget without the platform’s brand | Available |
| Neutral outage message | Available |
| Agency credit line in the widget | Available, off by default |
| Invoices addressed to the agency only | Available |
| Client area under the agency’s brand | Planned, not available yet |
| Script served from the agency’s own domain | Not available, open question |
| Emails to the end client under your brand | Open question |
Two points deserve a word of explanation.
The client area. Eventually, your client will be able to see what you choose to show them (statistics, conversations) in an area carrying your brand. It does not exist yet. In the meantime, you report to your client yourself, for example in your monthly maintenance report.
The script address. The embed code loads a script and a chat window served by blabla.bot’s infrastructure. An ordinary visitor never sees it. A curious visitor who opens the page source can read that address. If your client requires that no technical trace remain, tell us: it is a question we have not settled yet.
A pre-launch checklist
Before installing the assistant for a client, check the following:
- The logo and main colour are the client’s, and the contrast check passes.
- The greeting and suggested questions speak the client’s language.
- Your agency credit line is on or off, as agreed.
- The agent’s instructions never ask it to mention your agency or a third-party tool.
- A contact address is set for human handoff, and it belongs to the client or to you, never to the platform.
- A monthly budget is set on the site, so a traffic spike cannot trigger an unexpected pause without warning.
- You have tested the agent in the simulator, including questions about “the tool behind it”: the agent must answer on behalf of the business.
White label is judged on details
White label is not a cosmetic option: it is what lets you sell a service under your name, keep the client relationship and set your price. It is judged on the details people forget, such as an error message or an invoice. On those points, blabla.bot chose discretion by default, and we say clearly what remains to be built.
Tags
- white label
- agencies
- widget
Read next
Agencies and white label
Web agencies: offering an AI assistant to your clients and reselling it
Why an AI assistant fits naturally into a web agency offer, how to set one up for a client step by step, and how to set your own resale price with confidence.
· 5 min read
Widget and integration
Customise a chat widget's look without giving up accessibility
Brand colour, logo, position: how to dress a chat widget in a client's colours while keeping a contrast that every visitor can read, on desktop and on mobile.
· 5 min read
Agencies and white label
Managing all your clients' sites from a single console
Clients, sites, agents, statuses, consumption and budgets: how the blabla.bot console organises a multi-client portfolio, plus a weekly follow-up routine.
· 5 min read