How Relio Works

Baby Steps Updated Mar 1, 2026

Overview

Relio is an AI-powered sales assistant that lives on your website as a chat widget. When a visitor asks a question, whether it is about a product, a health concern, or even just a casual question, Relio recommends relevant products from your catalog.

Think of it as having a knowledgeable store assistant available 24/7, one that knows every product in your catalog and always steers the conversation toward a purchase.

The Flow

Here is what happens when a visitor uses your chat:

  1. Visitor sends a message ("I am looking for something to help with joint pain")
  2. Relio understands the intent and figures out what the visitor actually needs
  3. Smart product matching searches your catalog by meaning, not just keywords. It understands that "joint pain" relates to glucosamine, collagen, turmeric supplements, and similar products
  4. Intelligent ranking ensures the most relevant products appear first, with your preferred brands getting a boost (see Owner Bias)
  5. AI generates a response with a natural, conversational reply that explains why these products are good options
  6. Product cards appear with images, titles, prices, and a "View Product" button

The entire process takes about 2-3 seconds.

What Makes It Smart

Unlike basic chatbots that match keywords, Relio uses intelligent product matching:

  • "I need something for my grandmother's birthday" → Finds gift-appropriate products, even if none are tagged as "gifts"
  • "Ce pot lua pentru dureri de stomac?" → Understands Romanian and searches in the correct language
  • Follow-up questions → Remembers what was discussed and refines suggestions

Relio also enforces safety rules and never makes medical claims, using cautious language for sensitive topics.

What You Control

From your dashboard, you can control:

  • Which products are recommended (active/inactive toggles)
  • Which brands get priority (Owner Bias)
  • How the chatbot looks (colors, position, avatar, name)
  • How many products appear per response (1-4)
  • Whether prices are visible or hidden behind a "View Price" CTA
  • Where the widget appears (URL restrictions)
  • Lead capture to collect visitor info when they ask for human help