Answers for everyone
Visitors ask about products, prices, features or status. The assistant answers from your public content and systems.
Loading…
White-label
White-label AI that acts, on your domain.
Busymate AI puts an assistant on your site under your own name. It answers product questions for every visitor. For signed-in customers it can check and change things in their account, through your own systems. We run the assistant; the data and the systems stay yours.
One of our own products, set up as a white-label workspace: its own name, assistant, colours and web address — every field a setting, none of it code.
Built forAgenciesResellersSaaS productsService businesses
What it is
One assistant, for visitors and for customers
White-label means the assistant carries your brand and speaks from your data. Every conversation runs through your own systems — answers come from your content, with sources, and actions stay under your control.
Help for signed-in customers
A signed-in customer asks in plain words — “where is my order”, “change my address” — and the assistant does it in your systems, for that customer only.
Your data stays with you
Requests go to your own systems. You own the data and the rules. Busymate AI provides the assistant and the chat window.
How it works
How your site and the assistant trust each other
Your sign-in tells the assistant who the customer is. The assistant tells your systems what it may do for them. Both are short-lived, signed confirmations; no password or key is ever shared.
Your sign-in vouches for the customer
When a customer is signed in on your site, your site signs a short-lived confirmation and passes it to the assistant. We check it against your public key, so the assistant knows exactly who it is talking to. (For developers: a launch token, ES256, checked against your JWKS.)
Every action proves who it is for
When the assistant calls your systems, it carries its own signed confirmation naming that one customer and your connection. Your systems check it and answer for that customer only. (For developers: a signed call token bound to the customer’s subject and your connector.)
Anonymous visitors only ever reach your public tools — account tools stay out of reach without a signed-in customer.
Sign in from the chat
Your customers sign in without leaving the conversation
When a question needs their account, a sign-in card opens in the thread — with your fields, on your accounts. The password goes to your site, never to the assistant, and the same conversation carries on signed in.
Your assistant
Change the delivery address on my order
Sign in to see this — you will stay right here.
Email
Password
Sign inSigned in as a customer
Done — you are signed in. Which address should your order go to?
A question needs an account
“Where is my order?” The assistant does not send them off to find a button; it shows the card right there in the thread.
They sign in on your terms
Email and password, an emailed code, or the login you already run. Creating an account stays in your product as well — none is ever created with us.
The conversation carries on
Your site vouches with a short-lived signed proof, the session is refreshed in place, and the earlier question is answered — orders, bookings, balances, for that one person.
Already signed in to your product?
The chat can connect silently: it asks your login once, in the background, and only an existing session answers. If your login does not answer, nothing changes — the visitor stays a guest with the Sign in control.
What your developers connect
Two kinds of actions, one connection
Your developers expose one connection to your systems (an MCP server). Public actions answer anyone. Account actions receive the signed-in customer and answer for that one person. Two small endpoints complete it: your public key and a sign-in handoff.
Public answers
Open to any visitor, no sign-in needed.
list_plansProducts and pricesfaq_searchFAQs and how-tosservice_statusService status
Account actions
Each answer is for the signed-in customer only.
my_ordersMy ordersmy_subscriptionMy subscriptionupdate_profileMy profile — updates confirmed firstConfirm
Start from the starter project
We give your developers a ready-made starter project in plain Node with no extra dependencies. The actions, the public-key endpoint and the sign-in handoff are already laid out; they fill in the parts that read your data.
Go live
Four steps to your own assistant
Connect your systems
Start from the starter project and wire it to your data — public answers first, then the account actions you want to offer.
Run the checks
One command tries every action and both trust endpoints. All green means you are ready.
Register it in the Console
Add your connection URL, your sign-in issuer and your public-key URL. The Console checks them for you.
Publish
Press publish and your branded assistant is live on your web address. We are here if you want a second pair of eyes.
What you get
Yours in every way that matters
Your brand, your web address
The assistant lives at your address, with your name and your look — your own domain if you want one.
Help for every visitor
Product, pricing and support answers before anyone signs in.
Real help with their account
Signed-in customers check orders, subscriptions and settings in plain words.
Confirmation built in
Anything that changes something waits for a clear yes from the customer.
Data under your control
Answers come from your systems; content you ask us to index and the conversation history are stored per workspace, isolated and deletable.
See it in action
Businesses run this exact setup today — see a live example below.
Customers
Businesses built on Busymate AI
Each one has its own brand, web address and systems — see a live example.
2 businesses live · 14 languages · works with your own systems
BusyProxy
Customer support and real account actions for a proxy platform — payouts, devices, and verification, answered through its own API.
support.busyproxy.netSee a live example
BusySMS
Support and onboarding for an SMS-gateway product — from enrolling phones to OTP capture, live on its own support domain.
support.busysms.netSee a live example
These are the platform operator's own products, run by the same team — not yet an independent customer.
Questions
Common questions
- No. Every workspace starts at its own address on our domain. To use your own, add two DNS records; we verify them and set up the certificate for you.
- Answers and actions in their own account, through your systems. Your sign-in vouches for the customer, the assistant acts only for that person, and every change waits for a confirmation.
- Yes. One workspace per client, each with its own brand, web address, systems, allowed models, limits and usage — all managed from one Console or from your AI tools.
- Yes. When a question needs their account, a sign-in card opens in the conversation with your own fields, and the credentials go to your site — never to the assistant. Sign-up stays in your product too; no account is ever created with us.
- Requests go to your systems, so you own the data. Conversation history is stored per workspace, kept separate in the database, and never shared with another business.