White-label Alee: Remove the Badge & Rebrand

White-labelling is what turns Alee from "a chatbot tool I use" into "a chat assistant that looks like it was built in-house." It means stripping the "Powered by" badge, dressing the widget in your own name, colors and avatar, and — if you run an agency — shipping bots to clients under their brand or yours. This guide covers exactly what white-label unlocks in Alee, how to remove the badge, every branding surface you can control, which plan you need, and how agencies use it to resell.

What "white-label" actually means in Alee

People use "white-label" to mean two different things. In Alee, you get both:

• Badge removal — the small "Powered by Alee" line at the bottom of the chat panel disappears, so visitors see no mention of Alee.
• Full rebrand — the bot's display name, brand color, avatar, launcher icon, welcome message and persona all carry your identity, so the widget reads as a native part of your site.

Put those together and a visitor chatting on your site has no signal that a third-party tool is involved. That is the bar for a clean white-label, and it is what clients pay agencies for.

One thing white-label does not change: the underlying method. Alee still splits your sources into chunks, embeds them into the knowledge brain, retrieves the closest chunks for each question and has the model write a grounded, source-backed answer. White-label is about appearance and attribution, not how the bot thinks.

Which plan unlocks badge removal

Badge removal and full white-label are paid features. Here is how the tiers line up:

• Free — 1 bot, 200 messages/mo. Great for trying Alee, but the "Powered by Alee" badge stays on.
• Pro ($9/mo) — 2 bots. Removes the badge for your own brand.
• Agency ($49/mo) — 5 bots, plus the reselling and multi-client tooling. This is the tier built for white-label as a business.
• Scale ($99/mo) — 10 bots, same white-label powers, more room to grow.

If you just want your own widget to drop the Alee badge, a paid plan covers it. If you intend to run bots for clients under their brands, the Agency plan is the one designed for that — more on the reselling angle below. Check current details on the pricing page, and the full features list for what else each tier includes. (INR / UPI billing for India is on the way; until then paid plans bill in USD.)

Step 1: Remove the "Powered by" badge

1. Open the bot you want to white-label from your dashboard.
2. Go to the bot's appearance or widget settings — the same area where you set the brand color and avatar.
3. Find the "Powered by" badge toggle (it may be labelled "Show branding," "Powered by Alee," or "White-label").
4. Switch it off and save.
5. Open the live preview, or reload a page on your real site, and confirm the chat panel footer no longer shows the badge.

That is the whole mechanic. Because the widget loads from the single <script> line already on your site, you do not re-paste any code — the change goes live on every page running the script the moment you save.

If you do not see the toggle, you are almost certainly on the Free plan. Upgrade to any paid tier and the option appears.

Step 2: Give the bot your name and identity

Removing the badge is only half the job. A widget still called "Alee Assistant" in a red pixel-cat avatar is not white-labelled — it is just unbadged. Rebrand these surfaces so the bot reads as yours:

• Bot display name — set it to your brand or a friendly assistant name, e.g. "FlexFit Helper" or "Asha from GreenLeaf." This shows in the chat header and is the single most visible piece of branding.
• Brand color — paste your real brand hex so the launcher bubble, header and send button match your site. Guessing "close enough" is what makes a widget look bolted-on; grab the exact value from your logo or site CSS.
• Avatar — swap the default mascot for your logo mark or a friendly face. Square images (256×256 or larger), transparent PNG, key detail centred since it crops to a circle.
• Launcher icon — the floating bubble before anyone clicks. Use your logo mark for brand recall, or keep the default bubble for the universal "chat with us" signal.
• Welcome message — write the first line in your brand's voice. "Hi! I'm GreenLeaf's assistant — ask me about plants, care tips or delivery." India-facing? A "Namaste! Kuch bhi pooch sakte hain" greeting can feel more natural than stiff English.
• Suggested starter questions — the tappable prompts under the greeting. Phrase them the way your customers actually ask, so the bot feels tuned to your business.

Step 3: Set the persona so it sounds like you

Looks are visible branding; tone is invisible branding — and visitors feel it. Use the bot persona / system prompt to lock in voice and rules:

• Tone — formal, warm, playful, concise. Match how your brand writes everywhere else.
• What it represents — "You are the assistant for GreenLeaf, an indoor-plant store. Speak as a helpful member of the team."
• Guardrails — what to do when an answer is not in the content (Alee already refuses to invent answers, but you can shape the wording), and when to capture a lead or share a booking link.

A bot that looks like you but answers in a generic, robotic voice breaks the illusion. Persona is what makes the white-label hold up in a real conversation.

The "custom domain feel" — how far the rebrand goes

A common question: can the chat run on my domain instead of Alee's? Here is the honest, accurate picture:

• On your site, it already feels native. The widget is injected by your <script> line and renders inside your own pages, so to a visitor it lives on your domain. With the badge off and your branding on, there is no visible Alee.
• Behind the scenes, the widget still loads its assets and talks to Alee's service to do the retrieval and answer generation — that is normal for any embedded SaaS widget and is not visible to visitors.
• Lead delivery stays in your stack. Captured name/email/phone can be pushed to your CRM, Google Sheets or email via webhook, or automated with n8n — so the data that matters lands in your systems, under your brand, not parked somewhere that screams "third-party tool."

For the vast majority of creators, coaches, gyms, stores and agencies, "feels like it's on my domain" is exactly what the on-page widget delivers once the badge is off and branding is on.

The agency angle: resell bots under your brand

This is where white-label becomes a revenue line rather than a cosmetic tweak. The Agency plan runs many separate client bots from one dashboard — a roster — so you can:

• Build a distinct bot per client, each trained only on that client's sources, with that client's name, color, avatar and persona.
• Ship every bot badge-free, so the client sees a clean assistant that looks built for them, with no Alee mention to raise questions.
• Manage the whole book from one login, instead of juggling a separate account per client.
• Charge a monthly retainer. A common model: you pay one Agency subscription, install and maintain bots for several clients, and bill each client a setup fee plus monthly management. The margin between your one plan and what clients pay is the business.

A realistic worked example: you run a small web studio. You take on three local clients — a gym, a dental clinic and a coaching academy. On the Agency plan you create three bots, train each on that client's website, PDFs and FAQs, set each one's name and brand color, switch off the badge, and embed the script on each site. Each client sees "GymName Assistant," "ClinicName Helper" and "Academy Buddy" — no Alee anywhere. You bill each client monthly to keep their knowledge brain fresh and triage their top questions. One $49 plan, three retainers.

If you outgrow five bots, Scale ($99/mo) takes you to ten with the same white-label powers. For a side-by-side on how this stacks up against alternatives, see Alee vs SiteGPT.

A quick white-label checklist

Before you hand a bot to a client (or call your own done), confirm:

1. Badge off — no "Powered by Alee" in the chat footer.
2. Name — header shows the brand's name, not "Alee."
3. Color — exact brand hex on bubble, header and send button.
4. Avatar + launcher — brand mark, not the default mascot.
5. Welcome + starters — written in the brand's voice and language.
6. Persona — tone and rules match the brand.
7. Leads — wired to the client's CRM, Sheet or email.

Tick all seven and the widget is genuinely white-labelled, not just unbadged. For more walkthroughs, browse our tutorials.

Frequently asked questions

Does removing the badge change how the bot answers?

No. The badge is purely a label in the chat footer. The bot still retrieves from your knowledge brain and writes grounded, source-backed answers exactly the same way — white-label only changes appearance and attribution.

Do I need a separate Alee account for each client?

No. On the Agency (or Scale) plan you run multiple separate client bots from one dashboard, each with its own training, name, color and badge-free branding — all managed from a single login.

Can clients tell the chatbot is built on Alee?

With the badge switched off and your branding applied — name, color, avatar, launcher and persona — there is no visible reference to Alee anywhere in the widget, so visitors and clients see only the brand you've set.

Ready to ship a fully branded bot? [Start free](/signup) with Alee, then flip on white-label when you're ready to drop the badge.