Constructor.io Search vs. Coveo Relevance Cloud

Constructor.io Search takes all of the guesswork out of maintaining a search engine. As merchandisers or product teams, we have educated guesses at how search relevance should work but the customer is always king. We can't always predict the ways in which consumers will search or what their intent is. That's why the behavioral-driven approach that Constructor.io employs works so well. It means that merchandisers can focus on their sales and promotional responsibilities, instead of wasting time and bandwidth on base-level relevance questions.

Incentivized

Coveo Relevance Cloud is a great solution to implement into Salesforce to provide Knowledge-Centered Support, Enhancements to a Customer Community, to provide sales aids, or to complement your customized app in Salesforce.

Incentivized

• Optimizes for business KPIs, not string matches, so merchandisers can focus on strategy instead of maintaining a dictionary.
• Gives merchandisers control to curate the right customer experience per their expert understanding.
• Customer/technical support during and after implementation.

Incentivized

• Good library of connectors to enterprise repositories including MS SharePoint, Exchange, Confluence. OOTB using the Open Connector API administrators were fairly easily be able to index content repositories.
• Good security integration with existing repositories.

Incentivized

• Visibility of the personalization algorithm.
• Exposing detailed analytics within the customer-facing dashboard.
• "Top searches" available via API.

Incentivized

• Coveo does its job but is lacking.
• The results displayed by Coveo are not always relevant.
• The results displayed by Coveo are not sorted, nor is there an option to sort.
• The results displayed by Coveo are not location-specific, so results not relevant to my area or country gets shown.

Incentivized

We still have many clients which have custom search implementations supported by Coveo which crawl their Sitecore instances. From that perspective, I'm very likely to use it again. One of the main drawbacks I have heard is that Coveo is relatively expensive. The size of your project budget may have a greater influence on your decision to use Coveo if the custom features are not must-haves for your organization

Incentivized

• Quick to find things in a massive database when needed.
• Results need to be more concise - sometimes we spend more time looking for the right file than if we were to just search amongst our own networks instead.
• Coveo is not always the most useful but does its job when general information is needed.

Incentivized