AI Chatbots

Botstar, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Botstar account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Chatbots
  • Connects with a key
  • 9 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Botstar is

BotStar is a comprehensive chatbot platform that enables businesses to design, develop, and train chatbots visually for Messenger and websites.

You paste in a key from your own Botstar account. It is kept encrypted, and you can withdraw it from inside Botstar whenever you like.

How a run works

One message in, the work done in Botstar.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Botstar. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Botstar account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

9 tools it already has

What it can do in Botstar

These are the ready-made tools your AI employee already has in Botstar. It is not limited to them, but it never has to be taught these.

  • BotStar LiveChat onClose CallbackTool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."
  • Close BotStar Livechat WidgetTool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.
  • Get BotStar Application IDsTool to retrieve the botstar application id (appid). use when initializing or reinitializing the live chat widget.
  • Get BotStar Webview ParameterTool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.
  • Livechat bootTool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
  • Livechat on openTool to register a callback when the chat window is opened. use after widget initialization.
  • Livechat openTool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').
  • Livechat updateTool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.
  • Webview send responseTool to send data from the webview back to the botstar chatbot. use when you need to transmit responses or custom outputs from an open webview.
Access, and who is in charge of it

You stay the boss of your Botstar account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Botstar account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Botstar is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Botstar and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Botstar

Can an AI employee really work inside Botstar?
Yes. It signs in to your own Botstar account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Botstar?
No. Nothing moves and nothing is replaced. Your records stay in Botstar, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Botstar account?
You paste in a key from your own Botstar account. It is kept encrypted, and you can withdraw it from inside Botstar whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Botstar?
It has 9 ready-made tools in Botstar today, among them BotStar LiveChat onClose Callback, Close BotStar Livechat Widget and Get BotStar Application IDs. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Botstar and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Botstar and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Botstar?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Botstar is written down with what it did and when.