Coveo AI-Relevance Platform: Enterprise AI Search and Answers

My main use case for Coveo was to index the search results on our search pages like insights, listings, articles, stories, and other content.

One specific example of how Coveo worked for one of our search pages is when we had an external database managed by another team. We used to import those database items into a Sitecore master database, and while those items were getting published, they would also get indexed in Coveo, allowing us to search for specific items using their item ID or listing name, which would then appear in the search results managed by Coveo.

I faced some challenges regarding the accuracy of the search results with Coveo. For instance, if we searched for properties, listings would appear based on the property names, but the search accuracy wasn't always perfect. Suggestions in Coveo, such as office spaces, would yield popular office options that were cost-effective.

Coveo positively impacted my organization because the majority of our users who visit our website primarily use the search pages, making it a major functionality of our site.

I definitely noticed an increase in user satisfaction and improved search accuracy as a result of using Coveo.

The best feature Coveo offers is that items imported into the master database of Sitecore get indexed in Coveo very quickly, probably under a minute, allowing those items to be visible on the search page promptly.

The speed of Coveo's indexing helped our business users in many ways, specifically by ensuring their business campaigns and client expectations weren't negatively impacted due to slow search results.

The integration of Coveo with Sitecore is very good, particularly regarding implementation, customization, widgets, maps, and facets.

I believe Coveo can be improved by integrating artificial intelligence features. For example, if I type 'office spaces' looking for cheap and average sizes, improving AI could provide better search results based on user search history.

I have been using Coveo for the last 3.9 years, and recently we have replaced Coveo search with a Sitecore search in our project.

Coveo has never experienced downtime or issues in my experience.

Coveo is definitely scalable and can handle large volumes of data and users.

I reached out to Coveo's customer support many times, and it was one of the best experiences I had with their support team. I would rate the customer support as a nine on a scale of one to ten.

We are currently using Sitecore search in place of Coveo, which we recently replaced.

I do not have metrics related to return on investment with Coveo currently.

I didn't work on the licensing part of Coveo because I was an employee and not the manager.

Coveo was the first option in my mind before making a choice.

The quick indexing into the search results is the best scenario I faced with Coveo. In terms of accuracy and reliability of output, I believe Coveo is probably the best in market scenarios. Coveo is deployed in my organization as software as a service and integrates with my code base directly. I am not sure about Coveo's governance and security regarding its AI capabilities. I would rate Coveo an eight on a scale of one to ten.

Coveo's main use case revolves around content indexing and search integration, primarily when working with Sitecore as a CMS implementation.

In our Sitecore CMS implementation, we have very large content volumes, and Coveo helped us significantly with relevance through the use of indexing, query pipelines, and security features. Relevance was the most valuable feature for us. We were able to determine what content was shown to users and which was not, so Coveo provided substantial value from a relevance perspective.

From a business perspective, Coveo's biggest value is having more control over how users discover content, including relevance, ranking, personalization, and analytics, which can help improve the search experience without requiring a developer to change application code for every small adjustment. The exact value obviously depends on how well the organization configures and uses those capabilities.

Before moving to Coveo, we had metrics of user clicks around two million, but after we went live with Coveo, user clicks and all view analytics jumped up over 3.5 million, which was a significant upgrade after implementing Coveo.

In my view, the best feature that Coveo offers is relevance, which is one of the strongest areas. You have more control than you would typically get with a basic search implementation, particularly through query pipelines and ranking configuration. The important thing is that good relevance still requires proper configuration and understanding of your content, so I would not expect the platform to solve every relevance problem automatically.

I find query pipelines particularly useful because they give you a way to influence search behavior based on the context of the query without having to pull that logic into your application. For example, you can apply different ranking on query behavior depending on the situation, which provides a good separation between the application and search configuration.

Recently, I have been exposed to working with Coveo Atomic while working on the headless Sitecore implementation, and I appreciate the Atomic library because it provides reusable search components, so you don't have to build every part of the search interface from scratch. It makes the front-end integration faster while still allowing the developer to customize the experience when needed.

The main area I would improve is the learning curve because there are many concepts and configuration options, and understanding how indexing, query pipelines, security, and all those pieces work together requires experience. Coveo's onboarding experience could be simpler, especially for developers using the platform for the first time, and I believe that improvement on the documentation is also needed because while Coveo has extensive documentation, it is sometimes difficult to find exactly what you need.

As a developer, when trying to find something regarding how to do indexing, I have to read the documentation, but if there were screenshots showing how it can be done, it would make a developer's life simpler. Additionally, including code examples would greatly enhance the experience for developers.

I have been using Coveo mainly in enterprise search implementation, particularly in Sitecore environments, so I have been working with Coveo for the last five to six years.

From an enterprise perspective, scalability is one reason we consider a platform Coveo because we don't have to build and maintain the underlying search infrastructure ourselves, and the platform is designed for large content environments. My direct experience is more focused on implementation and integration, but I haven't seen scalability become a major limitation.

I recommend starting with search requirements rather than starting with product features. Understand your content sources, security model, and relevance.

So far, I haven't touched Coveo's AI-powered solutions, so I may not be able to comment on that because my experience is mostly with integrating Coveo, but not with the AI-powered solution models. I haven't used those AI features much, so I cannot provide insight on the accuracy and reliability of output.

I would rate Coveo an eight out of ten. I choose this rating because the platform is powerful, has strong relevance, and enterprise capabilities, but I deduct a couple of points mainly due to the learning curve and some areas that can take time to understand when implementing Coveo for the first time.

My main use case for Coveo is the search page. I use Coveo for my search page by creating sources in Coveo cloud organization and then providing it with data from our website and then displaying that search result on the search page.

Coveo has impacted my organization positively, as the search has been very good; the search terms and fuzzy search have all become very effective. I don't have particular data regarding specific outcomes or metrics at this time.

One thing that stands out to me about using Coveo for this process is that, as it is a cloud platform, it is very easy to integrate with your website as compared to other search options available.

The best features Coveo offers are the machine learning models and Coveo API. What I like about the machine learning models is that they are very easy to integrate; you just need to create some settings in the cloud organization, and then when you start using the search, it automatically learns from those searches and provides auto-suggestion in the search box.

Regarding Coveo's AI capabilities, I think its governance and security are good; as it is a cloud-based platform, the security is already very good as it uses SSO or login features. The accuracy and reliability of output from Coveo comes when the machine learning models learn from the searches that are done on your live site, so it becomes better over time, and I think those are reliable.

In terms of integration capabilities with other platforms or tools I use, I think it is pretty good; integration is straightforward. I have done it with Sitecore as well, and it provides out-of-the-box packages to integrate it, so it is very easy. I would describe the user interface and overall user experience with Coveo as very good.

I think Coveo can be improved by providing a sandbox for developers, even if you are not part of an organization, and the API configurations can be made a bit easier because there are a lot of options right now which confuses users. If I had to rate Coveo's flexibility regarding customization for my specific needs, I think it would be six out of ten.

I have been using Coveo for two years.

I think Coveo is stable.

I think Coveo's scalability is good.

The customer support for Coveo is very good.

I have used Solr before Coveo, and we switched to Coveo to utilize its AI capabilities.

Coveo is deployed in my organization as a SaaS-based software, so you don't need to deploy it; it comes by default on a cloud and it basically will provide you an organization so you can log in and then work with Coveo.

I can't say I have seen a return on investment with Coveo; I don't have these metrics.

I was not part of the pricing and licensing experience as it is handled by my organization, so I'm not aware.

Before choosing Coveo, we did not evaluate other options.

I would rate Coveo an eight out of ten. I chose eight out of ten because, as this is a cloud-based platform, there are some limitations, but overall it's a good tool.

Coveo already has a very good e-learning platform with multiple courses to learn and certifications to achieve, so it is very good in terms of the learning curve for new users or developers working with it. The documentation and resources available for Coveo are helpful, and even if you are a new learner, you can go through the documentation and it covers everything related to Coveo.

As far as I have used it, Coveo's performance and speed with large data sets is pretty good. I would advise others looking into using Coveo that it's a great product; just start looking into the documentation and utilize it well so your search page becomes better.

Our main use case for Coveo is to retrieve data efficiently. Before using Coveo, we stored this data in Salesforce itself, which took longer. We migrated our database to Coveo.

A specific example of how we use Coveo to retrieve and store data is related to our website, which functions as a doctor's website. Previously, we stored all data related to our doctors' content in Salesforce directly. When a doctor searches for it on our website or opens our record page, content pages, or content landing pages, content loading time took around 300 milliseconds. While not a major difference, in terms of user experience, it matters. After migrating to Coveo, it took less than 10 milliseconds to load all this data. This is our main use case, and we also have other use cases, such as content recommendation to our doctors based on trending content and personalized content.

Regarding the content recommendation use case, Coveo helps us personalize content for doctors with an ML-related feature. We send every detail of the doctor's viewing of pages to Coveo directly with the help of Google Analytics. First, we send the data from Salesforce to GA once a doctor views any particular content, and GA sends all this data to Coveo to train our ML models. With the help of those ML models, we see what the trending content is currently. Our doctors are specialized in 12 to 13 different specialties. Based on their specialties, we recommend content directly on the dashboard pages and on the content detail pages.

The best features Coveo offers include content recommendation, which is one of the best features. Additionally, the retrieval of data takes less time. It has moved from 300 milliseconds from our Salesforce data retrieval to less than 10 milliseconds in our Coveo retrieval. This is one of the other best features. The best thing is that we do not need to make an API callout for every communication between Salesforce and Coveo. I believe we are using headless communication, which is considerably faster. These are the best features I have observed.

Coveo has positively impacted my organization primarily by reducing the waiting time from 300 milliseconds to 10 milliseconds. Coveo also provides us very high data storage. We store our Salesforce records directly into Coveo as well. It syncs, and it takes around one hour to have a sync between Salesforce and Coveo.

Besides the improved speed and data storage, I have noticed increased productivity. Productivity has increased. The improvement is good, but I do not have the exact metrics of those details.

Coveo almost fulfills all my use cases, so I do not have any other recommendations or suggestions for Coveo.

One other suggestion is that as of now, the sync between our Salesforce and Coveo is one hour. I know we can make it real-time also. I do not know much about it, but I think it costs higher if we make it real-time. I would say that could be one of the improved features. It can give us more satisfaction if it is a real-time sync.

I have been using Coveo for a year.

Support is very good with Coveo.

It was great working with a product such as Coveo and integrating that product with our Salesforce. The experience has been good. I would rate this review a 9.