How-to · 8 min read

How to set up a live demo agent: 8 steps

From picking a page to reading your first transcripts. The order we would follow, and where deployments go wrong.

A live demo agent is only as good as what you give it. This is the setup list we would follow for a first deployment, in order. It assumes Zodiem, but most of it applies to any agent that drives a real product.

1. Choose one page and one number

Start with the page where buyers decide, usually pricing or the main product page. Pick one number to judge success, such as qualified conversations per hundred visitors. Narrow beats broad for a first run.

2. Build a demo workspace

Create a separate workspace in your product with realistic sample data and no real customer records. The agent will click through it in front of strangers. Check that nothing in it would embarrass you, and that signing out, deleting or exporting cannot reach production.

3. Load knowledge, then review it

Add your public pages and the documents that explain the product. In Zodiem each source has a review status, so nothing goes live until you approve it. Read what was extracted. Wrong or stale knowledge is the main cause of a wrong answer, and it is the part you control.

  • Include pricing logic, limits and what you do not do.
  • Remove pages that are out of date.
  • Schedule a recrawl so changes do not drift.

4. Write the agent's role in plain language

Name it, describe who it is talking to and set the tone. Keep it honest: it should say it is an AI, and it should say when it does not know. Publish a version so you can roll back.

5. Rehearse with hard questions

Ask it what buyers really ask: price, security, integrations, why not a competitor. Include questions it should refuse. Zodiem's eval scenarios and personas let you score these runs, so you can compare a change against the last version.

6. Decide where leads go

Connect Slack or a webhook, and agree who reacts and how fast. A lead that arrives with nobody watching the channel is the same wait you were trying to remove. HubSpot is in testing, and Salesforce and Pipedrive are not available yet, so check the integrations status for your stack.

7. Launch quietly, then read the sessions

Embed the script on one page. For the first fortnight read every transcript. You are looking for wrong answers, missing knowledge and questions you did not expect. Fix the knowledge, republish and repeat.

8. Review after a few weeks

Compare your one number with the period before. If it moved, widen to a second page. If not, read the transcripts again before blaming the idea.

Sources

This guide describes how Zodiem works and cites no outside research.

FAQ

Quick answers.

How long does setup take?
The embed is one script. Preparing a demo workspace and reviewing knowledge is the real work, and it depends on your product.
Do I need a developer?
The embed script is a copy and paste. A demo workspace may need someone who knows your product.
Can I test before going live?
Yes. Use eval scenarios and personas, and publish only when a version scores acceptably.
What if it gives a wrong answer?
Fix the source in knowledge, republish and review the session. The inbox shows questions it could not answer.

See it live on a real product.

Talk to Aria now, or tell us about your product and we'll show you how it would run.