What is Conversational AI 2.0?

What is the difference between Aisera Conversational AI 1.0 and 2.0?

Conversational AI 1.0 is any bot you create without enabling the Conversational AI 2.0 option in the Advanced tab of your bot settings.

Some comparisons between 2.0 and 1.0 are highlighted below.

Event	Process
Request Analyzer	The Request Analyzer only considers Small talk and Toxicity
Intent Extraction/Query Generation	As in version 1.0, the logic to generate the query is the same in both systems. This process is handled outside the Fulfillment Engine.
Search	Using the generated search queries, the system searches through: • Private KBAs/Service Catalogs (Neural Search). This is the same as in version 1.0. • Public KBAs (Public Search Service): Different logic - 2.0 the bot will search public sites in parallel. As in 1.0, Public KBAs are only used when the bot did not find a response in the Private KBA. For Public KBAs, if there are 20 allowlisted sites, the Aisera Gen AI platform uses Google to determine which sites are best to search for the given query. The platform uses the top 3 sites that Google recommends and provides the website content as context to the LLM and pulls the relevant chunks. • Flow Search (ICM+): Searches in all systems are conducted in parallel, and the results are then sent to the validation step.
ACL filtering	The validated chunks of information gathered are filtered by ACL to ensure that only the allowed content is used. In Conversational AI 2.0, only the Private KBA and Service Catalog items are considered for ACL.
Validation step	The final search results are passed through the LLM for evaluation. If the content is not relevant, these results are filtered out. If no results are left at this point, then bot will go to Fallback.
Decision Step	The validated chunks are passed to the decision engine to determine if the Fulfillment was provided or if a Context Disambiguation Service (CDS) question is needed. • Private/Public validated chunks: These either provide the RAG answer or trigger a CDS question. • Service Catalogs/Workflows: These are simply shown without triggering CDS questions.
Response Generation	The final response provided by the chatbot.

Intentless Workflow Search

With Intentless deployment, since there are no Intents, the traditional ICM search is not used to match workflows with requests. Instead, the intentless workflow search engine uses workflow descriptions to match a workflow to a user request. These are descriptions in natural language, specifying when a workflow will be triggered. The Intentless workflow calculates which user inputs may be required to execute targeted workflows. This is achieved using LLMs to intelligently review workflow descriptions and determine the mandatory and optional input data fields needed to execute the workflow. This process of conversationally collecting required input variables is called slot filling.

Citation Feature

The Conversational AI 2.0 Citation Feature allows you to view reference documents for each segment of the knowledge response you receive.

See Analyze Output of Knowledge Generation for more details.