Coveo Solutions Inc. (CVO) Earnings Call Transcript & Summary

Hi, everyone. Thanks for joining us at the year-end Coveo 2022, celebrating innovation. I'm Elaine Cobb, SVP of Customer Success. Today, we'll be looking back on a very innovative year. New features and releases all built to help you achieve your goals, reach your KPIs, drive results and be more efficient while delivering incredible digital experiences. For over 15 years, we've been committed to your success and in November of 2021, we had a major milestone by going public. We couldn't have done this without the trust and support from our growing community of partners and customers. It was great to be back in person and meet with our customers and partners in 2022. We connected with so many of you at Salesforce Dreamforce and Dreamforce World Tour, Adobe Summit, TSIA World, KMWorld, NRF and SAP events with more to come. In the spring, we held Relevance 360. You learned not just the latest releases in e-commerce and service, but you also heard from customers just like you. I also want to share a really special word of gratitude to our powerful partner alliances. You support not just SaaS, but our customers too. You help them get the most out of Coveo every day. You're a foundational part of everything we do. And thanks to the many innovative contributions from our Coveo community, we've been named a Gartner Magic Quadrant leader, a Forrester Wave Leader, InfoTech ES Market Report leader and a Software Reviews Enterprise Search Champion to name a few. And we're so excited to sharing that success together, so excited. In fact, we'd love to turn the spotlight on you, our pioneering and impressive customers. And now the moment many of you have been waiting for, we would like to announce the winners of the Coveo Relevance Awards 2022. Winners of this year's Innovators Award are Athena Health, Project Management Institute, Synopsys and Zero. This award celebrates teams, organizations and trailblazers who deliver unprecedented end-to-end experiences. From customers to employees, they find innovative creative ways to use Coveo's AI-powered relevance platform. Winners of this year's impact award are Caleres, Commvault, Forcepoint and Informatica. This award recognizes a company whose efforts and successes have made a clear impact on business outcomes. With tangible results and impressive metrics, each of these leaders has achieved the highest impact on revenue or profitability by deploying Coveo. Winners of this year's industry leader award are FleetPride and 2 other companies who wish to remain private, including a leading travel and expense management company, as well as a leading financial services company. This award honors a customer who's driven organizational change with Coveo. This transformation has distinguished them as the best of the best in their industry. Winners of this year's Pinnacle Award are Adobe, NetApp, Workday and Salesforce. This award celebrates companies with the broadest deployment of Coveo. They have amplified the impact of our relevance platform across their enterprise in multiple use cases, delivering clear results with both customers and employees. Congratulations to all. It's really been a privilege to see your success. All right. That's all for me. Let's hand it over to Nick and Seher to walk you through the amazing innovations we're driving for you, your team and your company.

Hello, everyone. Welcome. Thanks again, Elaine, for this great introduction. It's really been an amazing year for sure. Today, we have Nicolas Bordeleau, our VP of Products. Welcome, Nick.

Hi, Seher.

And my name is Seher Samnani, Product Marketing Manager here at Coveo, Together, we'll walk you through some of the amazing innovations we've done this year at Coveo, on our platform. Nick, ready to jump in?

I'm ready. Let's get started.

All right. Before we start talking about all of their mainframe features, we at Coveo do want to acknowledge that these are disruptive times. If there is disruption, not just in political, technological, social, but also in economical environments, everything is impacting our ability to do what we need to do to operationalize and also the investments being made into digital transformation. But we have to remember that even during these disruptive times, there has been a lot of digital transformation. We need to ensure that we're efficient and we're able to provide the stakeholders and the customers, the experience that they expect. We, at Coveo, have been around for about 17 years, as you may know. If you're newer to Coveo, you might have heard us talk about our different support areas of website, commerce service, but we do want to talk about also, the fact that we provide these experiences -- we help you provide these experiences to your customers, to your stakeholders, not just on one area like the website, but also the e-commerce store or your support agents or your workplace and provide a Holistic 360 experience to everyone. We also understand that the SaaS world has changed. The expectations of users like yourself, who are working very hard to provide experiences, are expecting composable architectures. We've heard the word headless this year a lot in a lot of different companies and headless is becoming the new it thing, but Coveo has always been there, providing you composable architecture, providing you flexible, templated APIs and libraries for you to be able to build experiences that your customers are expecting. We also have been -- we know and we have been investing into the user friendliness of our products. We understand that it needs to be quick, efficient and you need to get to market fast, with simplified journeys of setup. Our cloud infrastructure has always been robust. Security of your customers' data has always been important to us, and we continue to invest into those areas. And lastly, the business capabilities, as much as digital transformation and the customer journey has to be a full flow. We understand that certain areas of businesses require certain use cases and certain platform features that we also invest into, like for service, for e-commerce, et cetera. And before I jump in and hand over to Nick to walk us through all of the innovations, the 5 key areas that we have invested are pillars of our platform that help you build on is the connectivity and the indexing. The search experience, the UI, the front-end piece as well as the machine learning and the business rules, where you can get to market really quickly and provide automated experiences and personalized recommendations to your customers, as well as getting insights into how these experiences are performing for your customers. So analytics and reporting is also a very important piece of our platform. And lastly, the infrastructure, the developer toolings that we offer, so that you can build faster, you can build it the way you like to. All right, Nick. That's all for me. Let's start with connectivity. Let us know what's under the hood.

Awesome. Thank you, Seher. So around connectivity, all of you guys know that we have a really strong cluster in terms of connectivity. We already have more than 40 connectors, but we are not stopping there. We're always adding always improving. This year, we did a lot around that topic. We basically added 2 new connector, and we improved greatly and done major changes around 2 others that we already have in the platform. First one, Slack, no need for introduction, everybody knows Slack. There's a lot of content in Slack. There's a lot of discussion happening around other pieces of content that exists in the enterprise, being able to get this content out of Slack, bringing it into the unified index of Coveo, makes it available then to share that knowledge across the enterprise. Obviously, when you get more content into the index, the index get bigger, you can share that content in various interfaces. But also there's more and more model in Coveo that are learning from the content of the index. So the more you can have knowledge inside the index, the more the index becomes smarter and the more relevant it become to your users. The other one we added this year is SAP, SAP Commerce, Commerce Cloud. So this one is also -- I don't think it needs any introduction. Commerce Cloud from SAP is a big platform for large enterprise. We see that a lot of our customers were using that platform. So we decided to build a connector for it, basically, so no need to reinvent the wheel each and every time. If you want to stream content from SAP to Coveo, it's now much more easier. You can go in Coveo and just configure it versus building something that [ boosts ] to Coveo, much more efficient. On the existing connector that we've improved, there's a database one that was -- before it was only available on-premises through the Crawling Module. So it means that you were able to connect the database, but you had to deploy something on-premise. We are bringing that connector to the cloud, meaning that now you can connect the Coveo cloud to any other databases that are exposed to the cloud. They can reside in the cloud. They can be on-premise as long as they are exposed to the cloud. Making it much more faster to connect to those databases. There's one less piece that you need to manage, so much simpler to index those database. This connector for now supports Oracle database, MySQL, SQL Server, but we're working to add more database sources to be able to be crawled with that generic connector. The last one that we greatly improved this year is the REST connector. The REST Connector is the opposite of the database. It was only available in the cloud. We're bringing this one to the Crawling Module. So if you add any private REST API inside of your business that you don't want to expose to the cloud, you can now use the REST connector through the Crawling Module to be able to connect to those sources, and you don't need to expose that data publicly. It's only exposed to Coveo, and then Coveo is exposed publicly to be able to push to our cloud platform. So those are 4 great improvement that we've done around the connectivity in the crawler part of Coveo. Another part we did around connectivity is simplifying the method of discovery and extraction; because we have all of those connectors, those crawlers that are responsible to extract information from your systems, they extract everything that there is to extract. But a good practice is to keep your index lean and mean and you want to only index the content that you know you'll need to surrender, to play with ranking, to do faceting or sorting or whatever. But if you don't need some content at the Coveo, the good practice is to keep it out. This task was a bit complex to be honest, so we decided to have this UI here. It's basically a cash in between your content and the index of Coveo. Anything that goes out of the Crawler is now stored in a temporary environment, and you can go there to see what is -- sorry, what is mapped, what does not map, see some distribution of the value, see some sample value. So it's now, way easier to be able to understand what the crawler is getting out of your system, what you're pushing to Coveo, what you're missing, what should I create as a facet, what should I create as a sorting, what should I index just to be able to display or fine-tune the ranking. So you're able to transfer to create those mapping much more easier with that UI. Speed and performance, we've also greatly improved the speed of indexing. Not to be confused with the speed of crawling. Speed of crawling is oftentimes limited by the system we are crawling. Let's say, for a crawling sales force, but the rate at which we can extract from one source from Salesforce is limited by the system we are crawling. But on the other side, on the Coveo side, if there's multiple crawler, sending content or you're rebuilding or if you're pushing a lot of content, this content can stack up, and we need to process this content to put it into the index. And nowadays, adding fresh content that is -- as soon as it changes, is available to be searchable, is extremely important. So now the index is able to ingest content twice as fast, actually, a bit faster than twice. But to be conservative, we build it twice. It depends on the size of document size of the indexes. But your content that is in the Coveo platform, waiting to be indexed now much faster to be -- to go into the index. This one is the quality of life. But we think it is still important, is still innovation. The source for innovation were a bit harder to configure, when you wanted to have some specific users and group, directly into your sources. It used to be a adjacent task. Now there's UI for that. We have a pretty simple UI to be able to specify for this source, this source is source. I don't want it to be open to everyone. I don't want to respect the ATL that are coming from the system. I want to resize my own ATL, so my own users who have access to some piece of content. So now it's really easy to do through the UI. And because we have that, we're also able to let you know before you finalize the creation of a source or before you finalize the security of your content, we can also let you know and warn you, are you really sure you want to make that content available and then you can take informed decision, versus just creating content and risking, exposing that content if it's not secured properly. Another area of investment, search experiences. So we've -- I've shown you before that we created the Slack connector. We also created a slack application. So the Slack connector is responsible of getting the content out of Slack, to be able to bring it back into the index, into the unified index and then expose it somewhere else. This one here is responsible of doing the opposite, bringing all the content from your total unified index into Slack. We spend a lot of time in Slack. I personally spend a lot of time in Slack. I'm always there chatting with colleagues trying to solve issues, discussing about problem, progressing on some key projects. So there's a lot of things that are happening in Slack. And when you want to perform a search, I find a document, I try to see if something exists around a topic. You typically need to get out of slack, and go either in the IPS or open a browser to be able to search and find the content that you need to have to. So with this, it's fairly easy. You just need to go -- you just need to open Slack. And actually, I'll show you how it works. So I'll stop this from here. Switching to this Coveo test environment. To install the Slack application, you just go to Slack, the Slack app store, you go there, you get the application. Very simple to integrate. You just need to connect it through your [indiscernible], provide an API key, provide a query pipeline. Once that is done in Slack, You can pretty easily use the well-known slash command, to find out whatever application are integrated. There's now one for search Coveo, and then I can search for any topic that I have in mind, just hit that. And now I have a search perform on the popular and not so popular covered topic that I picked. I have option to do faceting if I want to search on a specific document type, specific source that can be customizable. And the results -- good old results are there. So you can -- from your flow of work, from where you're currently discussing with colleagues, you can perform search right away and get the information at your fingertips. And if you want to consume the information, just like before you click on results, they open in a browser. If they are a browser, they open in the app, if they're from an app. But the search itself can be performed within Slack. Going back to slide -- another great thing that can be done within the Slack app is agent swarming. So we've seen that in service scenarios, when agents are working and trying to solve an issue at some point, they might need to work with some colleagues. So the concept here is that you can click on the swarm button, that transfers you to the Slack application. It looks in the index from the topic of the support case, from the description from whatever you have on that support case. We extract the information from there, look into the -- into your business, try to find the right expert, invite them into a channel. So that channel now becomes the swarming environment for all these people to try to solve the issue. And because we're also indexing Slack, the results of those swarm can also be presented to users -- to support agents who are trying to help customers. So if a swarming ended up being successful in closing a case, those swarm can also be brought back to other future cases, when people are trying to. So it's basically closing the loop, and making it easier for people to collaborate with Coveo content. Another thing we did this year was to bring basically Atomic UI into hosted search pages, talking about local search UI. So if you want to build a quick prototype, a quick search interface that is leveraging Coveo and Coveo Atomic, you can now go into the Coveo platform and build an interface that can actually get you access to your content really fast. And you can reiterate on that interface, to fine-tune a couple of things. Let me find my browser, it's right here. I just want to show you briefly how that looked like. So from the Coveo organization, if you go into search page, you add a simple builder, which is the new one I'm talking about. So that's creating me basically a new search interface. By default that interface is -- by default configured to have results, facets, search box, query suggestion, everything is configured there by default. So already I enabled the search in the content of that organization. It's a trial organization with the default content. But if I would like to filter out what source should be in there, I can go there. I can do manual selection. If I want also to change the result, layout, going from grids to list. If I want to have a different way to enter those results. Maybe I want to have something more commerce-ish, with larger images or something more condensed. I can go there, can play with what's going to be rendered in there as well, faceting, sorting, everything can be configured, everything can be added, removed and you can also go as far as playing with the style of that UI. That's currently at the moment, it's really interesting for 2 reasons. It's interesting for prototyping, because as you've seen, it's really fast to be able to build some new interface. If let's say you want to try a new source, you want to show to your colleagues at with work. You can really quickly build that interface and share it with them. One thing I haven't showed yet is the option to share those interfaces. You can basically propagate it through your colleagues to see what you've done to see if it works. The other benefit of that interface is, because it's low code and no code, if you have limited access to developers, if you have limited access to development resource, once that page is created, it's altered into Coveo. And if you do any changes, if you change the behavior, if you change anything, you don't need to republish or you don't need to propagate that from the dev to QA environment. As soon as you hit save, those changes are live and they are effective. So you can create a different copy of the page and then one is live, one is your staging environment. But you don't need any more, to add a developer that does all the job for you of configuring the interface, transferring from an environment to another, and you can do much more. You can also down-- actually, there's a lot of things that can be done with those new interfaces. I'll stick it to that short intro for now, in a manner of keeping track of time. Another thing we did this year, which is quite interesting, is in the intelligent facet generator. That feature is part of the dynamic navigation experience set of feature. So the index has always been able to provide the right facet to the right user, based on interaction on the data. So basically, if you have a, let's say, an e-commerce shop like we have here, as people navigate through your content, as they click on different facets, as they click on different results, the index becomes smart and it's now able to provide the right facet for the right queries. The problem is that before you have enough traffic, the facets, you need to curate them manually or you need to have a set of generic facets that fit with all of your users. With that feature, the initial training of the feature is done basically based on the index. So based on what's returning from a specific query, the index is going to be able to search and get the right facet right away for you. So that's much more efficient for the time that your index is ramping up learning about the behaviors and also for queries that are less frequent. If nobody is searching for those terms, if nobody is searching for those type of product or those type of document, the index cannot know what are the right facets. With that feature, we're kind of bridging the gap and making sure that we always have the right facet. That facet definitely blend in the dynamic navigation experience. As soon as we have data from actual users, they will take over and that data will be permanent. Another feature we released this year is an instrument to the Salesforce user action. User action are actually used in a service environment, service scenario. So that's basically -- if I'm a customer, I come to the website of my provider, I try to find information about the problem I'm having. So I'll probably go there, I'll do a couple of actions, I'll do a couple of queries, take on a few documents. And at some point, if I'm not able to get the answer I'm looking for, I'll create a ticket. So at that stage, all the -- and the things that you've done are collected, they are used to improve the relevance of the index for visitors after you, and also to improve your own session. But that data is actually quite important, quite useful for the agent that's going to be helping you. So that's what user action are basically. There's a lot of improvements that have been done this year, mostly around the way we're presenting and where do we put the context. So from now on, the ticket created is actually the starting point of the timeline. Timeline has been reversed. We're showing you really what was performed before you created that ticket. We know what document you've consumed. We know what the query that you've performed. So as an agent, I now have a lot of context about what you've done before contacting me, and I can pick it up from here versus asking you to do a lot more things that you've already done on the website. Another addition we're doing this year is the Quantic Insight Panel. So for those of you who know about Salesforce, Salesforce is all about Salesforce Lightning web component. That's the set of components that are available to build those interfaces inside Salesforce. So Coveo offer headless. Coveo offer Atomic. Now there's Quantic. Quantic is basically a wrapper on top of the Coveo UI library, and we're offering you an easy way to be able to deploy inside panel and also other type of search interface directly within Salesforce. So if you want to deploy a full search page, if you want to deploy an inside panel, if you want to do any interaction related to Coveo inside Salesforce, it's now way easier. You just have to drag and drop those components. Those components can be also configured to behave the way you want them to behave, inside Salesforce. That feature is currently in early access. If you want to try it out, if you want to get your hands on it, please contact your CSM. They'll be able to get you in touch with the right product manager or maybe there's even a program already where they can get you an insight, and get to try the Quantic Insight Panel components. Next section, machine learning and business roles. We did a lot around that, too. So we worked a lot on the case classification and smart snippet model. Those are 2 models for our service in the business. Case classification for those who don't know, case classification is basically when you land on the support side, as I was saying before, I'm searching, I'm searching at some point, I want to create a support case, that support case -- the more information I provide, the most relevant information I provide, the better chances the agent is going to be able to help me with that support case. So that case classification is basically helping you to find out what else should you provide in that support case. Maybe you should provide a product version. Maybe you should provide a category of problem that you're having. So we're proposing you action to take and information to provide and classification to add on your support case, to make sure that the information is treated the right way on the other side. And smart snippet is basically what you -- what we know and learn and what we know and learn from Google. Basically, you go to a search engine, you type in a query and then you get the results, you get the procedure. How do I reset my iPhone? You don't want to click on a link to be able to then go to a website and then consume the procedure. You do this, you do that, you get those 2, at the same time, and they'll be set. That's the feature. So those features were released last year. There was a lot of improvement done on the models themselves this year to make them more efficient. And the UI you're seeing here is basically a UI that we're providing now on top of those model, to make it less of a black box. You want to understand what those models are doing. So we have the good old way to understand when the model was last built, when the model -- how the model is hosted, how is it performing. But now there's more information about these precise model, to let you know how good on the prediction. When we say case specification, we're predicting case specification for users, are they good? Are they not good? Do I have enough trained data set? What's the size of that data set? So we're giving you much more information to be able to have -- to make informed decision about those model in the future. And then, we are ranking. This one is also quite interesting. This one is precisely for commerce. So when you're browsing a commerce site, you probably don't have just one intent. You probably come to the site, you have, yes, one intent at the moment, but this intent might change over time, if I'm browsing for a, I don't know, a snowboard, I might at some point want to search for gloves as we have here, or maybe I want to search for bindings to complete my product or whatever. But the intent is not just the list, the convenience of action that you've done in the session, and what you've done previously on the site, your intent is actually limited to a set of actions that you've done recently. So that model is basically a way to find out, what are those actions that make your intent. What is this intent, providing it to you as context to your query and then the whole ranking of the index is now changed. We know in the example, we have here, 2 people searching for gloves. One is into skiing, the other one is into golfing. You're going to have different products, obviously, based on what you've done before. The particularity of that model is that it's able to fine tune to the precise intent that you have at that moment. It was previously available for query suggestion. So we had query suggestion that we're kind of aware. Now that feature is going deeper and it's now available to change the whole ranking of the index, based on the current intent that you have at that precise moment. Groups and campaign; groups and campaign are a nice way to group rules together. If you want to create some rules to influence the ranking. And now you can do a lot, but you -- oftentimes people want to have their own set of rules, business rule or maybe there's an event coming next week, and you want to have some specific rules that are going to boost some content at the top, boost some specific topic. And you want those to be time boxed or you want those to be targeting some specific users. So now you can group those rules together in a group and in a campaign, basically. You can time box them, you can do AB testing on them. It's a really a nice way to be able to provide more flexibility around managing those rules. Rules -- before that were just a big list of rules, and it was kind of hard to be able to navigate those. And now with groups and campaign, it's much easier to group them together, associate them with a purpose and then maybe associate condition or time box them or tag them to precise audiences. Similar to groups and campaign, audience specific recommendation. That's basically a way to create a decision tree when you do recommendation. So recommendation, we have multiple models that get recommendation a different phase of a buying journey or of a browsing on an e-commerce -- on a website or on a support portal. All of those models actually are providing good recommendation. But if you -- as a product merchandiser, I want to be able to associate those model with precise condition. Before it was -- one set of audience, one model, now we're offering the option to queue multiple decision, multiple conditions, one after another, associating those to precise model. Making it much easier for a non-developer to control what's happening on the recommendation placement on the site. The example here is that returning visitor, we should focus recommendation on larger price ticket items versus new visitors or all visitors that will get more basic recommendation. So to be able to do those and stack those conditions, those different model one to another, there's now a way to do it and to Coveo's [indiscernible]. Around analytics and reporting. We did some change around the consumption dashboard. We're actually finalizing and releasing those as we speak. So consumption before, it was a big bucket. So you've purchased multiple SKUs, you've purchased multiple products from Coveo. You have queries, you have users, you have recommendation, you have a lot of entitlement. They were all computed together. We wanted to provide more granularity to our users so that they know, where they're consuming, where they are overconsuming, where they are under consuming. So now it's really easy to be able to see all those SKUs, associate Search hub with different SKUs that you've purchased and be able to see yourself the consumption that you're doing on those queries, without having to ask Coveo for the [indiscernible] dashboard or your CSM for the [indiscernible] dashboard, you can now consume it directly within the platform. Another great improvement we did to the platform is around Coveo Analytics. So Coveo uses Snowflake to store the analytics on the background. Snowflake is a great platform, where you can do lots of things. Because the analytics are in there, we decided to offer it and to our customer and offer our customer the option to be able to see the data directly from Snowflake. There's a couple of benefits. You can go there and merge Snowflake -- sorry, Coveo Analytics data with other data sources. In commerce, we often see people who wants to see if there's a relationship between the weather and buying trends on the website -- on the commerce side. So that's one possibility. You can merge multiple sources together to have better understanding. And you can also simply plug another tool, another BI tool on top of Coveo Analytics, to be able to do different analysis of the same data. On the platform infrastructure, so we had -- we already had the option to do snapshots into Coveo. We improved the way to manage those snapshots from a UI perspective. We're now providing you much more information about what's the content of a snapshot, much more information about how to create that snapshot, how to transfer it from one environment to another. Just a quick backup, snapshots are basically a way to create a snapshot of an organization and transfer it to another one. So if you have your sandbox, you want to push it to product, you go to your sandbox organization, create a snapshot, transfer it to the product organization without -- this means that you don't have to remember what change needs to be done in one organization and keep them in sync. You just need to transfer the configuration from one to another. So now there's a UI that guides you toward that. And we also had the option to do it through the CLI. CLI, the command line tool to interact with Coveo. you probably already have a deployment pipeline that take all of your commerce or website or whatever integration where Coveo was in, That takes it from one environment, migrate it to the other where Coveo was a part of it. So with that tool, you can add scripts to talk with Coveo, grab a specific snapshot, transfer it to a specific organization and automate the full deployment of your site -- not just your site, and then have to do manually for Coveo. So that's quite powerful for the bloggers. Another feature we added for product listing pages -- product listing pages are basically category page that you have on a website. We're adding a merchandising hub in there, and it's basically an easy way for merchandiser to go and see those -- all of those category pages, because there's a lot, to be honest, of category pages, and basically create a set of rules that are applied specifically for those category pages. We're kind of back passing or creating a new UI on top of the query pipeline, making it easier to go in for that page. That's what I want to boost. I want to pin those things at the top and that's drag and drop, that's really easy to play with. I want to lose those things. I want to bury those. I want to have that feature result at the top. I want to exclude those products, I want to include those. So that's really easy to go and play with the merchandising of a listing page directly within the merchandising hub. Seher, we also have a lots of new things in terms of learning and development.

Thanks so much Nick. This definitely was a lot of innovation that we've done. But we also are very committed to helping our customers learn and self-serve. So last year, in 2021, we had released our developer certification on our Level Up platform. This year, we're coming up with a newer version, where we have 4 new skill packs. We have about 40 courses that you can take, so that you can learn about Coveo, get a very deep dive into it, and build a solid Coveo implementation. The other things that we've also done, is we've helped create courses not just for the new features that we've released, not just for the technical users, but also for business users. We want you to understand the different concepts. We want you to be able to really grasp what every feature can give you and then help you build over it. So about 50 new courses and training materials have been created, highly recommend you checking them out and going your path, the skill sets you want to build for Coveo. And lastly, let's just take a really quick peek into 2023. Nick, do you want to run us through? I'm very excited for 2023. This is just a release quick sneak peek?

Yes. Quick sneak peek only. I'm going to cover mostly what's in the beginning of the year. And as she said, really quick sneak peek, if you want to learn more about the feature or the full road map, you can contact Coveo to get a more detailed roadmap for next year. The first thing we were going to release next year -- actually the first thing I'm talking about, but the first thing next year we are releasing, but the first thing I'll cover today is the infrastructure. So we are actively working on an active-active environment, to be able to replicate the index from one environment to the other, making it much more resilient, if there ever is something that happened, that shut down a whole data center, a whole region, that means that we'll have a copy -- an active copy replicated up-to-date, ready to take queries from another region. We'll deploy that in the U.S. continent first, and we might do something later after that for other regions, but we're deploying it -- we'll be deploying it for the U.S. at first. This also has the benefit to be much more performant in terms of queries, because we have 2 index available at the same time with the same replication. If you're closer to U.S. West, you're going to query on that index much more faster. If you close to U.S. East, it's also there to respond and it's also faster. Next thing we're doing around the infrastructure is, we are adding a new region for Canada. So if you have a legislation that require you to keep your data on Canada soil, that will be possible this year and all the benefits of adding a new region, primary region in Canada are going to be available. We are also investing heavily into the models. What you see here is an interface that we'll be releasing next year. That makes it easier to understand what are the models. We basically want to encourage our customers to deploy more machine learning model. Those models exist. It's up to you to create them. It's up to you to understand what they do. So we are adding more information on the UI to let you know what are those models, what are they going to be doing? What's the impact? Visual representation of those model also in action -- is also linked to the demo environment, if you want to see them in action, for you to create those models to make -- really take the benefit of the whole Coveo platform. We are also investing to make those models easier, to be created by adding them to the flow of the service and commerce and workplace and website scenario. So when you do, let's say, a case specification, the model will be created automatically, and then things like that will automate the creation of those models for you, when it's time to create those model, making sure that you have those model deployed in your environment. We are also working heavily on the web source. The web source is actually a source that pretty much all of our customer is using, pretty much all our customers have some sort of content that they want to index that is coming from our website. The current UI is a bit cryptic, quite powerful to be honest, probably the most powerful out there, but a bit hard to understand, a bit hard to configure at first. So we're changing the whole UI, keeping the same feature, but just changing the way to configure changing, the way to interact with the crawler, to make it easier to deploy those web sources. Another improvement we're doing is around security. We're always working to improve our security and maintain our security position. The next one we'll be adding is ISO-2701 certification around that. So if you are looking to deploy Coveo to other departments, to other use cases, that should probably help you to alleviate those discussions -- those security discussion with your security department around Coveo. Coveo will be 2701. We're already SOC1, SOC2 Type II and then things like that, but we're adding one more for the European region mostly, but it will also support the U.S. region as well. And that's what I have for today.

Thanks so much, Nick. Definitely a lot of information. If anyone has any questions, please put it in the chat. We do have a couple of questions in the chat. One of the first questions Nick, we have is, are you planning on integration with Cisco WebEx, and not just Slack?

Honestly, it's not planned yet. The fact that we don't have an integration plan, doesn't mean that it cannot be done. If you want to integrate with -- actually, we can integrate with multiple systems, because we offer multiple libraries, because we offer multiple things to integrate Coveo. It's fairly easy to integrate. We're not planning to build one for that precisely. But if you would like to explore the integration, please contact Coveo, PS can help you, R&D can help you to look at how those integration could be built.

Amazing. The other question also we have is, how do we test for ML changes? Example, boosting rules. Sandbox usually doesn't have a lot of clicks and production is for all users. Is there a way to create a group of users, potentially push changes that are specific to groups in a pod?

That's a good question. I don't have an answer on this webinar, but I know some teams are looking at ways to be able to replicate data from one environment and bringing it back to other environments. So basically taking your cloud environment analytics, bringing them back to your QA environment, where you could run and build new models. I think that, that should be a discussion between this -- I don't know who asked the question, but I invite them to contact us and have a discussion with our team. I know some discussions are around that topic, but nothing is planned in the roadmap. And maybe there's best practices that could be shared with that person to help them do the testing as best as is possible today.

One more question, Nick, and it's very similar to the Slack -- the previous question about Cisco WebEx, are we planning on integration with MS Teams?

Still same answer. Nothing is planned. But a similar answer, it's fairly easy to integrate Coveo. The Slack integration was not a big endeavor, honestly. Those platform wants to have integration. They -- just like us, we want people to integrate. So there's always API, there's always samples. There's always a lot of things to be able to create those integrations. And Coveo is really composable. So if you want to take the small UI that we have for Slack, if you want to bring in to teams or into Cisco WebEx, it's typically relatively easy to do it. So if you want to try it, let us know we can help you.

And what I would also say, our community is quite vocal sometimes, when they want a specific feature. So anyone who do -- like if we don't have any features planned and if you do want a feature for a specific integration, I would highly recommend, post it in the community, if the feature gets boosted enough, we can prioritize it and move it forward as well. That's all from us today. If you are not a customer of us just yet, and are ready to kickstart your digital transformation, I highly recommend, just book a demo with us, and we can walk you through all of the amazing things we can do to help you transform the digital experience. We will put the -- book a link in the chat right away.

Thanks, everyone. Thanks, Seher.

Thanks. Have a good day. Bye-bye.

Have a good day. Bye.