Busymate AI

Documentation

Getting started

On this page

Getting your Busymate AI assistant live takes five steps — workspace, web address, sign-in, systems, publish — and you do them yourself in the Console. Open Console → Integration for your workspace and follow its live checklist. It is generated from your real settings, so its URLs, sign-in fields, code snippets and checks are always current.

The five steps

1 · Workspace 2 · Web address 3 · Sign-in 4 · Systems 5 · Publish

1. Your workspace

A workspace is your own space on the platform. It carries your name, a short slug, and your branding. Everything your customers do — conversations, history, connected accounts — stays inside your workspace and is never visible to any other. A platform owner can create the workspace in Console → Platform → Tenants or through the Busymate AI management MCP; the invited admin then completes the Integration checklist without anyone handing off.

2. Your web address

Your assistant is served at a web address you choose, mapped to your workspace:

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

Under the hood, an address resolves to exactly one workspace. An address we haven't mapped yet stays plain and unbranded — your branding appears only once your address is verified and switched on, so there's never a half-branded window in front of your customers.

3. Your customers' sign-in

Decide how your customers are known to the assistant:

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

You can offer both: visitors at the front door, signed-in sessions for your customers.

4. Your systems (optional)

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

5. Publish

When branding, web address, sign-in, and (optionally) systems are set, run the checks and publish from the Console. Publishing is versioned — a change you make is prepared, checked, then switched on, so what your customers see only ever moves forward to a complete setup. A missing sign-in setup, an unreachable connection, or an unsafe action rule blocks publishing with a clear reason.

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 own address (which we add to your workspace's allowed list), so the assistant lives right where your customers 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 web address you want (a subdomain to start, or your own domain to verify).
  • How your customers sign in — or whether you want guest access.
  • Optionally, your MCP server URL if you want bro to take actions.

Next

Questions

Do I need my own domain to start?

No. Every workspace answers at its <slug>.busymate.ai address immediately. Add your own domain when you are ready — see Serve your assistant on your own domain.

Can I add the embed later?

Yes. Hosted page, embed, or both; adding the embed later changes nothing about the workspace.

What blocks publishing?

A missing sign-in setup, an unreachable connection or an unsafe action rule. The checks name the blocker; the draft stays a draft.

Who creates the workspace?

A platform owner, in Console → Platform → Tenants or through the management MCP. The invited admin then completes the Integration checklist without anyone handing off.