AI Assistantv2.0.1 · 203
Sign in

Documentation

Getting started

Getting a white-label live means standing up your tenant — your brand, your host, your users — and pointing bro at your tools. The workflow is self-service in the AI Assistant Console: open Console → Integration for the selected tenant and follow the live, tenant-specific checklist. That section is the source of truth for URLs, identity claims, code snippets, preflight, and publication; it replaces static per-tenant handoff files.

The five steps

1 · Tenant 2 · Host 3 · Identity 4 · Tools 5 · Publish

1. Your tenant

A tenant is your isolated space on the platform. It carries your name, a short slug, and your branding. Everything your users do — conversations, history, connected accounts — stays inside your tenant and is never visible to any other. A platform owner can create the tenant in Console → Platform → Tenants or through the AI Assistant management MCP; the invited tenant admin then completes the Integration checklist without an operator handoff.

2. Your host

Your assistant is served on a host you choose, mapped to your tenant:

  • To start, every tenant receives its own <tenant-slug>.busymate.ai host.
  • Your own domain (for example assistant.yourdomain.com) once you point it at the platform and it’s verified. From then on, your users only ever see your domain.

Under the hood, a host resolves to exactly one tenant. A host we haven't mapped yet stays neutral and unbranded — your branding appears only once your host is verified and activated, so there's never a half-branded window in front of your users.

3. Your users' identity

Decide how your users are known to the assistant:

  • Signed in as themselves — you connect your own sign-in, and each user reaches bro as them, so bro can act on their data (and only theirs).
  • Anonymous guests — if you'd rather let anyone chat without signing in, you can enable a guest mode. Guests get answers and guidance but not actions on a specific user's private data.

You can offer both: guests for the front door, identified sessions for signed-in users.

4. Your tools (optional)

If you want bro to do things — not just answer — connect your own MCP server. That's how bro reads and changes your users' data through your API, under your rules. This is optional: a knowledge-and-answers assistant needs no tools at all. See Connecting your tools.

5. Publish

When branding, host, identity, and (optionally) tools are set, run preflight and publish from the console. Publishing is versioned — a change you make is prepared, validated, then activated, so what your users see only ever moves forward to a complete configuration. A missing identity contract, unreachable connector, or unsafe tool policy blocks publication with an actionable result.

Embedding bro on your own site

Beyond a hosted page, you can embed bro directly into your product — a side panel or a chat bubble on your own pages. The embed runs on your site's origin (which we add to your tenant's allowlist), so the assistant lives right where your users already are, still fully your brand. It's one script tag:

html
<script
  src="https://busymate.ai/embed/v1.js"
  data-assistant="your-tenant-slug"
  data-label="Ask us"
  async
></script>

Hosted page, embed, or both — it's your call, and you can add the embed later without redoing anything.

What to prepare

  • Your product name and brand assets (logo, colors, a short welcome message).
  • The host you want (a subdomain to start, or your own domain to verify).
  • How your users sign in — or whether you want guest access.
  • Optionally, your MCP server URL if you want bro to take actions.

Next

PreviousOverviewNextThe assistant experience