Optimizely CMS

Answers grounded in the intranet you already have, found by meaning rather than by exact wording — because nobody searches using the words the policy was written with.

What it is

A connection to intranet sites built on Optimizely, searching through the site’s own Elasticsearch index. It combines semantic search with plain query-string search, and can fetch a whole page when an excerpt is not enough to answer properly.

Use it for

• “What does our travel policy say about hotel standards?”
• “Find the guidance on this, and give me the whole page rather than a snippet.”
• “What are the latest news items on the intranet?”
• “Search for this exact phrase, not something like it.”

Tools

Function	Answers
Usage guide	When to search semantically and when to match exactly — the assistant reads this first
Hybrid search	Pages matching a question by meaning as well as by wording
Query-string search	Pages matching a literal search expression
Fetch content	A whole page, for when the excerpt is not enough
Latest news	Recent news items from the site

Data and permissions

• Read-only. Nothing is written to the CMS.
• Reads the site’s existing index. No separate crawl, and no second copy of your content to keep in step.

Getting started

The integration needs access to your Optimizely site’s search index. Talk to your Customer Success Manager.

Limitations

• Permissions are at index level, not per user. The connection searches the index it is pointed at, and everything in that index is reachable by anyone using the assistant. Point it at content that is open to the whole organisation, and control the rest through assistant access.
• As current as the index. If the site’s own index is behind, so is the answer.
• Optimizely specifically. Other CMS platforms need a different connection — for a site without a usable index, the intranet crawler is the alternative.
• It finds pages, not documents inside pages. An attached PDF is not indexed by this route.