What is a Demo Site?

A demo site is a small set of hosted pages where people can try your Velaro bot on realistic scenarios and tell you what worked. Each page covers one scenario, shows a short checklist of phrases to type, and has the live Velaro chat widget on it. Every page also has a Feedback box, so testers can report results without leaving the page.

A typical example is a demo for a medical equipment supplier: one page for product questions, one for troubleshooting an oxygen concentrator, one for sending a photo, one for talking to a person, and so on. Testers copy a phrase, paste it into the chat, and mark what happened.

Use a demo site when you want a customer, a pilot group or your own team to test the bot against real questions before it goes live on the main website.

Step 1: Teach the Bot the Customer's Content

The demo is only as good as the knowledge behind the bot.

1. Open Knowledge Base and use the Web Scraper to add the customer's website. Only scan sites you own or have permission to index.

2. Upload manuals, guides and policy documents with File Training.

3. Wait for the scan to finish, then check pages scanned to confirm the pages you expect are there. If an important page is missing, scan that page directly.

4. Click Publish to Index so the bot can use the new content.

See the Web Scraper guides for blocked sites and re-scan behavior.

Step 2: Choose the Bot Profile, Routing and Deployment

1. Pick the bot profile (name, tone, greeting) that testers should meet. A dedicated profile for the demo keeps your live bot untouched.

2. Choose the team routing for the demo, so a request to talk to a person reaches the right team or the right fallback.

3. Choose the deployment (the chat widget settings) for the demo pages, and confirm the widget opens and replies on a test page before you invite anyone.

Step 3: Build One Page per Scenario

For each scenario, create one page that contains:

• A short title and a one-line description of what the tester is checking.
• The phrase to type, written exactly as a real customer would say it.
• A Copy button next to each phrase. If the browser blocks copying, the button selects the phrase so the tester can copy it by hand.
• Three marks for each phrase: Matched, Did not match and Not sure. Matched means the bot answered the way you expect. Did not match means it answered wrong, answered with something unrelated, or did not answer. Not sure is for anything the tester cannot judge.
• The live chat widget.

Keep each page to a handful of phrases. Testers give better feedback when a page is short.

Step 4: Add the Feedback Box

Put the same Feedback box on every page. It asks for:

• Name
• Email
• Message
• Overall feedback or things you want to try

When a tester sends it, their marks and comments go by email to the Velaro support and management mailboxes and to Teams, so the right people see results quickly. Each submission includes the page it came from and the marks for each phrase.

Testers can leave and return: their marks stay saved on the page until they send them.

If testers see "Failed to fetch"

1. Hard refresh the page (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac). Pages keep older files in the browser cache, so a refresh loads the current version.

2. Press Send again.

Their answers are still on the page, so nothing needs to be re-entered.

Step 5: Read Results and Fix the Cause

1. Read each submission and list every phrase marked Did not match or Not sure.

2. Group them by cause, not by phrase. Ten phrases that fail for the same reason are one problem. Typical causes are missing knowledge, a skill that does not trigger, wrong team routing, or a greeting that sets the wrong expectation.

3. Fix the cause in the bot's knowledge, skills or routing, so similar questions are fixed too, not only the exact phrase tested.

4. Rescan the website or re-upload the changed file if the fix is in the content, and publish to the index.

5. Retest the same phrases, plus a few new ones phrased differently, and ask testers to send a second round.

Repeat until the phrases that matter are all marked Matched.

Frequently Asked Questions

Do testers need a Velaro account?

No. Testers only need the link to the demo pages. They type into the chat widget and use the Feedback box.

Where do the feedback emails go?

To the Velaro support and management mailboxes and to Teams. The tester's email is included in the message so you can reply.

Can I use the demo with my live bot?

It is safer to use a dedicated bot profile and deployment for the demo, so test changes never reach your real customers.

Why did the bot answer correctly for me but not for a tester?

Testers phrase things differently. Use the exact phrase they marked, read the conversation, and fix the cause so different wordings work too.

Will the demo count against my plan?

Demo chats are normal conversations, and scans and re-scans follow your plan. Limits depend on your plan; see your plan under Billing, Usage Overview.

A tester marked Not sure. What should I do?

Read the chat yourself. If the answer was acceptable, mark it as expected; if it was vague or incomplete, treat it like Did not match.