Bot Essentials

The Aisera Gen AI Platform is a SaaS application, which means it has server software running in the cloud, that interacts with your client application (that's usually a browser, but in this case it is a bot or AI Search application).

You can set the login credentials for your bot when you create it. In the example above, the bot uses an email address as the login credential.

Bot Channels (Look and Feel)

The default bot application is a Webchat bot, but other applications are available that have specialized functions and features.

The 'look and feel' of your bot is known as a Channel in Aisera Gen AI (and most other AI) terminology.

Bot Conversations

An AiseraGPT bot can engage in conversations as well as derive information from data sources to serve as answers to customer requests.

Domains (EDPs)

The type of conversation you want your bot to have is determined by the Domain or category of information that you want your bot to use. For instance, in the screenshot of the default bot above, the bot is taking a food order for pizza. You might refer to this as the Restaurant, Hospitality, or Pizza Order domain.

The type of application that you build with the Aisera Gen AI Platform depends on the Enterprise Domain Pack (EDP) that you choose when creating your application and the Channel or 'skin' that your application uses.

When you create an AiseraGPT Bot, the bot creation wizard will ask you what Domain you want to use for your bot.

For instance, if you want to create an Aisera Assist bot for your IT department, you would choose the IT value for the EDP and then create a description or purpose for your bot.

The EDP that you choose for your application or bot determines the default Conversations and Intents that it will use.

Conversations and Intents

The EDP that you choose for your application or bot determines the default Conversations and Intents that it will use.

Choose the View Conversations button on your application's Details page to see the conversations that are included with the EDP that you have chosen.

Select the View Intents button on your application's Details page to see the Intents that are included by default with the EDP that you have chosen.

When you select a specific Intent, you can see more information and make customizations in the Intent Details window.

Requests, Intents, and Fulfillment in Workflows

Each conversation with the chatbot takes in a Request, determines the Intent of the Request, and provides Fulfillment for that Request as a Response. In it's simplest form, there is a one-to-one correspondence between the question (request) and the answer (response).

In the world on Gen AI, you associate the Request with an Intent (intention) so that the chatbot can fulfill the request in the best way possible, even if there are different ways to make the same request. For instance, the Requests, 'Do you know the time?' and 'What time is it?' have the same Intent. But the Requests, 'Do you know what time my meeting is?' and 'What time is it?' have different Intents.

As you can see from the diagram below, the Fulfillment can take different forms, depending on the Intent of the Request.

In the Aisera platform, you set the conversation and action sequences for your application or bot using Workflows that you build with the AI Workflow Studio and then associate with a specific application.

A Hyperflow is an advanced type of workflow that allows you to build a flow based on the integrations that are connected with your application or bot.

Intentless Requests with RAG Answers in Hyperflows

The Aisera platform also supports Requests that are more complicated, and may include an Intentless goal that requires a set of Actions and RAG indexing of your documents to complete.