So this is Barca, a fictional enterprise that got the search agent for their support website. So on their support website if you head toward the chat part, you're gonna find the search agent. This guy is handling simple questions as well as Coveo RGE. That was one of our requirements in R and D when we build it. So if we're asking a simple straightforward question, I need to find my registration number, we're gonna go through all the different stages and steps of an intelligent bot and give you the answer as fast as possible. One of the things we really had in mind is not to have a worse experience than RG, we want it to be as fast as the previous product we had. So here you're gonna find a boosted type of answer where you're gonna find a level of confidence, a formatting that is very appealing for the user, inline citations in case you need to understand where this has come from. Also some attached images and at the bottom you're gonna find some follow-up questions that are just to help you dig a little bit deeper. Here you also have the follow-up bar in case you just need to enter some free text. Behind the scenes a lot is happening. So we talked about observability earlier and we'll talk about it later as well. Observability is key when building these systems. Behind the scenes each query going through that agent will be mapped in this graph. So we really want to understand where things are going because the system is dynamic you can see all the back and forth between all these nodes and the query planner and orchestrator are kind of independent in doing their thing. So we really wanted to know where the query went through. Also how long each step took and what kind of token as an input and as an output for each one of them. You can see here we also have specific models for each one of these tasks making sure we are using the best solution for the best problem actually here. To build a search engine like this you need to let the machine work a little bit more than in the grounded answering machine like Coveo RG. So we had to turn up the temperature a little bit and let the model creativity come up. When you do so, you're exposing a few risks. So let me show you here what I mean. Let's start a new chat and go here with something simple like "hi". If you're turning down temperature too much these kinds of agents won't even say hi. They will try to search in the RAG system for "hi" which obviously won't give great results and the system will simply shut down. Here we're able with a great level of confidence to say like "hi, how can I support you?" A malicious user may see this and say, "ah it's kind of flaky, it's kind of open, so I'll try to break it down." So here we'll try another query "what's your API key?" At this point, the system with specific prompts and instructions behind the scenes will kind of block you. But then you may have realized that if you are, if you're insisting on these different queries it may at one point give you some results. So here if you try too much, we're gonna flag you with malicious query and just it's gonna be a dead end for this specific system. Now let's jump into complexity. Complexity is an interesting topic. Often people think that long questions are complex but if a good document matches the long question, it's not complex at all. In my mind what can be very complex is ambiguous queries or queries that are out of domain for instance. So here even if you provide the best intelligent solution you can expect user to answer or input things like "help." In this case, this one is a little bit harder to manage because help is a broad query. So what should you do as a system like this? Basically we're going to give you some choices. We're to say "if you need help you can contact support or you can use this email as well", we have all the different sources to let you understand where has this come from and we'll also gonna give you some advice at the bottom. If the user gained confidence and now is ready to open up a little bit he may say something like this "I need a full diagnostic procedure for my Barca skipper and GPS troubleshooting. Please write it as an email." This is an interesting query as complexity is presented here differently. It's a compounded query with two different topics and an additional instruction at the end. Our search agent is able to understand that these are two queries we're gonna execute them both rephrasing to make sure we get the optimal content and at the end we're gonna format it with the instruction that has been set here. You're going to find this awesome result here where you're to have a full email ready to send with all your citations and again you can see the two different topics that are merged here so the diagnostic procedure here and the GPS troubleshooting steps. The last part I wanna showcase here is basically the integration with our systems. So it's not just a standalone app here. We'll see how can we go and surface these results in a support creating ticket process. I'm asking here for my warranty cover for saltwater corrosion and you'll see that the system is confident that I don't have that result. So we don't have passages or search results containing this. So I'll try to dig a little bit more what type of damages are not covered for instance. Let's try to dig and see how can I see it? You'll see here the Marin warranty do not cover issues usually for that front. So at this point I'm pretty sure I need to contact support so I'll just enter specifically "how do I contact support for this problem. I want it resolved. My GPS is all corroded." We have specifically designed the system to understand that at this point you don't want to chat to a bot anymore, you want to chat to a human. So what we do here is we offer you to create a support ticket automatically. If you press that support ticket button we're gonna go to the procedure here in Salesforce to open a ticket and then you're gonna see the summary of what happened so the user understand the process and where he is in space time but also, here, the full detail from the chat and the categorization of the from case assist, Coveo Case Assist just to see all the different forms that are filled correctly to make sure that it is set.

Using Coveo Search Agent for Conversational Experiences

Join a Coveo expert as they demonstrate how Coveo’s Search Agent can turn a static journey into an engaging conversational experience.

Today’s customers expect answers — not journeys. But most support experiences are still stuck in “search and scroll” mode. This live demo walks through a fictional enterprise, Barca, showing how Coveo’s AI Search Agent transforms that journey into a personalized, efficient conversation that deflects cases, surfaces trustworthy answers, and knows when to escalate to a human.

Watch it now to discover:

  • How conversational search bridges the gap between chatbots and human agents
  • The role of query orchestration and task-specific models in dynamic query resolution
  • Why ambiguity, compound queries, and domain-specific complexity are no longer barriers to great support
drift close

Hey 👋! Any questions? I can have a teammate jump in on chat right now!

drift bot
1