Hey, everybody. This is Daniel Rajan from the product marketing team at Coveo. And I'm Mathieu Lavoie-Sabourin from our product management team at Coveo. Today, we're excited to bring to you Coveo for Agentforce two point o, A big step in enabling Agentforce get smarter with better knowledge, even more context, and giving you greater control. Let's dive in. The challenge today is AI any AI agent, agent force needs to be grounded by all of your enterprise knowledge, which is often large and complex in terms of file sizes and formats and permissions. We're not talking about two, three repositories. We're talking about large enterprises that typically will have fifteen, twenty, thirty different repositories across different types of connectors that need to be brought in together. And millions of documents and items. And the challenge is this knowledge lives in places outside of Salesforce. And each team has their own preferred tool to store this knowledge and context. And so this results in multiple sources of truth. And the challenge to unify all of this knowledge is costly. It's disruptive and just not practical. And this is why we released Coveo for Agentforce in the first place. Coveo unifies all of this knowledge regardless of where it lives. It now becomes a single source of truth for Agentforce to be grounded. And then using our proprietary rag AI and ML models, it retrieves the best of the best content, setting up agent force to deliver on self-service success and helps you improve operational efficiencies. So before Matthew jumps into the demo, I'd love for you to talk about Coveo for Salesforce in general, broader than Agentforce. Talk about our partnership and our integration. We have a great history with Salesforce. We've been AI partner contributing to the Salesforce platform by additioning the Coveo AI relevance platform, which essentially allows to tap into all of the knowledge that enterprises that we work with have spread across lots of different repositories. Once again, not four, five repositories, not with content that only lives in Salesforce. We have over forty different connectors as well as universal connectors to bring content from everywhere across the enterprise into a single source of truth. What we've then done over the last years, is then power Salesforce experiences with our relevance AI models to power better search experiences that are more relevant, our multistage rag to power generative answering experiences to deliver end to end answers to help improve self-service, case deflection, and agent efficiency. Also, adding behavioral analytics to better understand the success that we're delivering in APIs to increase the connectivity and the types of integrations that we can power. And we've done so very successfully notably across Salesforce Commerce Cloud, Salesforce Experience Cloud, and Salesforce Service Cloud. But things kinda took a shift recently with, Agent Force, which brought us to release our first Agent Force integration in the spring, allowing for that unified hybrid index and our connectivity to then power agent force experiences as well, making agents smarter, more accurate, and better to help large enterprises benefit and accelerate time to value with Agentforce. Got it. So Coveo is an AI search and generative answering company. That's our strength. But now with Agent Force, we are diving into the agentic era and setting up Agent Force to retrieve content and knowledge from any source and really grounding Agent Force to deliver. So Exactly. I want to ask, how is Coveo different to what data cloud would do for Agent Force? That's a great question. And we we are complementary to data cloud. Essentially, we augment data cloud when it comes to adding more content. So if you think of data cloud and Coveo as your memory or your brain that will power your agent, Coveo allows to expand that brain and ensure that that brain can actually help make Agentic for successful for large enterprise that have a lot of content, which would be very difficult or nearly impossible to migrate into data cloud. Again, we're thinking about large quantities that go way beyond a hundred k, for example. So what we've seen, if knowledge is all in Salesforce and you have maybe fewer than, you know, a few dozens of thousands of, of documents, data cloud will likely be a fit for you. But the types of enterprise we work with will have way over a hundred k documents. We're talking about millions of documents that need to be retrieved, multiple sources scattered with complex personalization and relevance needs as well as complex item level permissions, for example. This is where Coveo can really be brought in to help ensure success in an Agentic force deployment by ensuring that all the content, all the intelligence, and the knowledge that's spread across and available for those large enterprises can be made available for Agentic. Awesome. And, Matthew, you mentioned our partnership goes a long way. And so over the last decade or so, we've been working closely with Salesforce AI, and they really trust Coveo, depend on Coveo for, the to be their search and retrieval layer. And what that really has resulted over the years, just highlighting a few, stories along the way, is that Coveo has impacted these enterprises in terms of self-service success, case deflection, and cost savings, in customer service. So a lot of shared success with Salesforce over the years. So, I want to dive into the demo. Matthew, I'd love for you to talk about, Coveo for Agentic force two point o. Show us what's changed. Yeah. Absolutely. Let's get into that. Alright. So let's now dive into a demo and showing what Caveo has actually brought to Agentic force to make it more accurate and more relevant. So the first thing we developed with our action is the possibility to tap into Caveo to retrieve content from across multiple repositories, allowing a larger breadth of content and knowledge to be used, making Agentic force more accurate, smarter, more relevant. So here in this example, I'm a support agent working in service cloud using agent force to answer question, but I could also be, for example, an end user or a client, using agent force within experience cloud, for example, with the same use. So the first thing I'll do here is just ask a question. Right? What we do here under the hood is very simple. We go and tap into Cavill's retrieval layer, retrieving the very best content from across all sources available in a Cavill index, making sure we then retrieve the very best passages, the very best chunks of text, providing that back to agent force so that agent force can provide more accurate answer using a, again, a larger breadth of content, whether this content lives in Salesforce or whether it lives in Jira or Confluence or SharePoint or any other complex repository that needs to be brought in, making sure those answers are more accurate. Another thing we've developed also is tapping into the, intelligence layer that we have and the large language models that we have. We've built an action to help classify cases. So we have a proprietary large language model under the hood, which will find what is the most relevant and accurate classification to classify this case here, which as you can see, doesn't have a classification. It was created without the both in first category classification. So here, Coveo will serve as the intelligence layer to find what is the most likely classification based on historical cases that were closed and properly AI, providing that intelligence back to agent force, allowing agent force to then take this intelligence, apply AI to the record, or for the support agent to make the changes themselves. Awesome. So classification of cases, it it actually takes AI, especially for enterprises with a long list of taxonomies and categories. And a misclassified case is a big culprit in delaying response times and delaying resolution AI, also messes with analytics when cases are misclassified. So this is a really, really good use case. So there's question answering, There's case classification. And so now what's improved in Coveo for agent force two point o? Well, yes. To bring this a step further, what we've done is we've brought the possibility to first and foremost control the prompt. Right? So by allowing agent force to use within a prompt template where we've seen users, use this tool for more flexibility and more complex prompt, asking your, LLM or your Agentic talk in a specific tone and providing just longer, more complex instructions that can also tap into dynamic variables such as our Apex classes to retrieve content from, Kavio directly within a prompt template. So that's the control piece. And then the second piece we've added is context, allowing you to tap into context about the record such as the subject, the description, the categories, or context about the user, for example, what region that user is in, what, is their role, or what business line they work in, which can then allow to, perform actions such as solve this case, for example, which will be using both the context of the case, so the subject, the description, the categorizations, as well as a prompt template to have more control over how the output should be delivered, Essentially tapping into the very best that's available within agent force, but also the very best content that's available within Coveo and Serena AI a better end to end resolution to a case. Once again tapping into all the possible content that lives within the Coveo index. This is really powerful. So, essentially, case resolution is, out of the box use case with Coveo for Agentic force to AI out. Very seamless and very easy to do, but also very customizable. And with that customization, we even see the other use possible use case we brought with our new integration, such as create a knowledge of ours based article from this case. So using the information in the case, the notes that an agent has entered, and then tapping into Kavira once again to retrieve what is the relevant existing documentation about this issue. Right, on top of any new information that may have been brought in the case itself. And then using a flow, we're able here to actually create a brand new knowledge article from scratch using Agentic force with Coveo as the grounding layer to create new knowledge, which will, of course, then accelerate reusability of that knowledge and ensure that such cases don't need to be created by end users in the future as content will now exist to solve those cases upstream. Awesome. So in essence, Coveo for Agentic force two point o gives you more context. It gives you more control. And this sets you up really to, open up a whole world of possibilities and unlocking new actions, new use cases for customer service and support. That's Absolutely. That's that's amazing. Hey. Thanks, Matt, for walking us through the demo. It's really, really powerful. So to take us home, why is Coveo critical for Agentic force? For one, it helps accelerate your implementation. Your knowledge can live in any source. Coveo's unified index and out of the box connectors makes it faster to implement Agentic force. Secondly, it actually brings any content regardless of formats and files and sizes and permissions. And so there's universal connectivity that Coveo brings and also respects and enforces item level permissioning. All these are usual obstacles that we have been hearing talking to customers and implementing Agentic for successfully. And the one other point is it helps you preserve data cloud credits for what it's really meant for, which is structured data use cases. So using Coveo as the source of truth for unstructured data and your enterprise knowledge, it helps you preserve that data cloud credits for structured data use cases. And lastly, Coveo is really the foundation to power agentic experiences through Agentic force. Matt, any final words? AI. Thank you. You've, you brought it brilliantly. And, you know, we've seen great success of forwarder clients, testing out for agent force and bringing this to self-service as well as agent use cases, essentially making agent force responses better going from okay response to making the response much more accurate, much more powerful, and using, again, a larger breadth of content, which is really the key differentiator of using Coveo. So Coveo for agent force two point o is available on the agent exchange today, and we're excited for what you are gonna do with it. Thank you.