Your information, put to work

The answer starts
with what you know.

Your website. Your catalogue. Your documents. RAVO looks them up before it answers, so the conversation is built on your own information rather than on what a model happens to know.

Sample catalogue record

Product information

Ceramide Body Lotion, fragrance-free

  • Fragrance-free
  • Ceramides
  • Dry and sensitive skin
  • £30.99
Information supplied by the business
A customer asks

“Recommend a fragrance-free moisturiser for sensitive, dry skin under £40.”

RAVO answers
For fragrance-free, sensitive skin that’s also dry, I recommend the Ceramide Body Lotion at £30.99, and the Rich Moisturising Cream for dry and sensitive skin at £26.99. Are you looking for a face moisturiser or a body lotion?

The shopper’s requirements meet relevant fields in the catalogue.

You choose the sources. Agree how they are maintained, and where the assistant should refer someone to your team.

Explore your information in a demo ↗Data and privacy ↗
For your connected catalogue

The product is shared.
The connection is local.

Map the catalogue’s locations to your RAVO sites. Agree the fields and update process so the experience has the right business context.

Example catalogue recordSample dark-oak exterior woodstain tin

Exterior Quick Dry Woodstain

Product reference
WOOD-EX-DARK
Finish
Dark oak
Use
Exterior wood
Catalogue location
Newcastle catalogue location
Mapped RAVO site
Newcastle store
Local product information
Woodcare, aisle 7
Same question: “Where can I find this?”
You can find exterior woodstain in aisle 7, in the woodcare section.
Catalogue location
Leeds catalogue location
Mapped RAVO site
Leeds store
Local product information
Garden care, aisle 4
Same question: “Where can I find this?”
You can find it in aisle 4, beside garden care.

Documents explain your business. Structured catalogue fields bring product and location detail. The connection is scoped to your systems.

Discuss your information sources ↗
A closer look

Look up what is relevant

Products, documents, website content and store information can supply context for a question. Which sources are relevant depends on the question and the information connected to the assistant.

Explain using that context

The retrieved material informs the response. This gives answers a relationship to your business information rather than asking a model to know your catalogue unaided.

Make the limits part of the design

Grounding reduces reliance on general model knowledge; it is not a guarantee that every answer will be correct. A good deployment also defines what the assistant should not answer and when customers should speak to your team.

Keep the knowledge useful

Agree who owns source content, how it is updated and how representative questions are checked. Accurate source material is an essential part of a useful assistant.

Bring your questions

Start with one question. See where it could go.

Start with a question your customers actually ask, and explore how it could be answered on screen.