Chat UIs: A Case Study

Whether adopted by a single department or rolled out across multiple teams, companies can have diverse needs regarding the integration of AI-driven chat experiences into their workflows, such as:

  • Use case n°1: The human resources department struggles to keep up with repeated questions about vacation policies, benefits enrollment, and payroll.

  • Use case n°2: The company has a wealth of internal documents, process guidelines, and best practices scattered across multiple places. All the employees waste time searching for the right information.

  • Use case n°3: In a fast-changing data privacy regulation environment, the legal department needs AI assistance to help them work with complex compliance requirements and draft updated agreements.

The type of requests and end users can be heterogeneous from one use case to another, so a good practice would be to create dedicated AI services for each of them to increase the generated answers accuracy and relevance.

The following sections explain how Answers and Agent Connect can be used together to solve these problems.

Leveraging Answers

Answers is an excellent candidate for use cases ‘1’ and ‘2’ previously introduced, as it will allow the simple leveraging of the company’s data.

The following diagram outlines the creation of Answers services to cover them, with examples of questions they could process.

../../_images/answers-case-study-0.png

Leveraging the LLM Mesh to create an agent

With the need of multi-step reasoning and adaptation to specific tasks, the use case ‘3’ would require to leverage the LLM Mesh to build an Agent.

The following diagram outlines the type of interactions users could have with such type of agentic-AI.

../../_images/agent-case-study-0.png

Leveraging Agent Connect

Some employees might need to access several of these AI services. Finding the right entry point to consume them will become more and more complex as their number grows and sometimes the right answer requires to combine some of them.

Agent Connect solves these problems by providing a single place to interact with any of the Answers instances and agents.

../../_images/agent-connect-case-study-0.png

Note

‘Agent Connect’ follows the security rules set on the projects hosting Answers or Agent Connect. To go further, please check the Agent Connect documentation.

Once connected to your Answers and/or Dataiku agents, the Agent Connect service is able to smartly route user queries to the right set of generative AI services:

  • When multiple services are selected to fulfill the initial request, the requests are sent concurrently via a pool of threads.

    • Finally, the responses from each selected AI service are presented to the Agent Connect LLM that combines them to answer the user.

  • When only one service is selected, its answer is forwarded as is to the user.

  • When no service is selected, the Agent Connect LLM answers the user according to their conversation history.

The following diagrams illustrate how Agent Connect would behave and process user requests once connected to the 3 AI services.

Request example 1

../../_images/agent-connect-case-study-1.png

Request example 2

../../_images/agent-connect-case-study-2.png

Request example 3

../../_images/agent-connect-case-study-3.png