Your glossary of Hu:toma AI terminology

Updated 11 months ago by Matthew Clementson


A bot or chatbot is an Artificial Intelligence machine that responds to user input, as entered in normal, “natural" language. The bot's response is also in natural language so that the user has a "conversation” with the bot.

User-to-bot conversations can be on any topic that the bot developer designs. The conversation can also provide a service, such as looking up the weather, providing customer support, or booking a cab. This is entirely for the bot developer to decide.


One of the unique features of the Hu:toma platform is the ability to use bots created by others in our store.

If you link to a bot from the store, you create a new bot that has the combined capability of both your own bot and the linked bot.

There is no need to know any of the technical details of how that linked bot works: our platform will seamlessly guide your user's conversations from your bot to the linked bot when it detects the conversation best suits the linked bot.

To help you find bots you might want to link to, you can browse or search the Botstore.


A client is a way for an end-user to access your bot. This could be hosted on your website, or integrated to some third party service such as Facebook Messenger or Slack.

Developer Console

The developer console is a website that a registered user of our platform goes to if they want to:

  • Create a bot
  • Edit a bot
  • Test a bot
  • Publish a bot to our store


An entity is a category of items like Cities in the USA or Coffee types available on my menu, along with a list of valid values for that category. One or more entities are required by an intent.


An intent is the capability to capture context data from your chat users that allows you to take an action, either in your client or using a webhook.

An intent requires one or more entities to be matched.

For example, a weather bot would have an intent with a location entity for where to get the weather for. Then a webhook for the weather data REST API would be called, passing in the recognized location.


A REST API provided by a service such as a weather data provider or a restaurant chain's booking. This can be used to do a real-world action when an intent is matched.

How did we do?