|
Our W2W is an agentic demo. Prospects take a guided tour of your app, ask questions and connect with Sales for any issues. Testing is a must with this. Your chatbot needs to learn.
|
|
|
Normal software doesn't cost more to use after an update. AI does.
Until a model could hold a thread, stay grounded in your docs, and respond to a person in real time, a self-guided demo was a slideshow with captions. Now it can approximate the thing buyers actually want — a salesperson who's available at midnight, never pushy, and answers the specific question on the specific screen. That capability is roughly a year old at usable quality, which is exactly why this is worth doing before it's a checkbox in a bloated toolset.
The built-for-you version has the same drawbacks...at 5x the price.
The platforms selling the productized version want you to believe their agent is turnkey: plug it in and it just works. It doesn't, not without the same grounding, guardrail, and handoff tuning your own build needs. Both paths require real testing to get right — the difference is that one of them costs about 75% less and leaves you owning the logic and the data.
› A self-guided demo on your own WordPress page that greets visitors with a 2-3 question quiz, then walks them through your product screen by screen — with the bot phrasing each step for that visitor, not a generic caption.
› A chatbot that answers off-script questions from your own docs mid-demo, so a curious prospect doesn't have to stop and book a call to find out if you do SSO.
› A clean handoff for the moments the bot shouldn't answer: when it's unsure or the visitor signals real intent, it stops guessing and points them to a booking link or an email.
Prerequisites:
WordPress installed
This is scoped for the most common CMS out there.
WPForms Installed
We coded this to use WPForms as it's the default choice. A different form platform won't be much different. Check out the attached guide doc for more info.
› Build your WordPress landing page: This is the container everything else lives in: a simple landing page with room for the quiz, the demo, and the chat. Build it first so you have somewhere to drop the embeds as you go.
› Write the quiz for WPForms: The bot's personalization will be shaped entirely from what you capture here. Ask three things: who they are (their role), what they do (company or use case), and what they want (the outcome they're evaluating for). That's what lets the bot open with "since you're a RevOps lead trying to fix pipeline visibility, here's why this screen matters to you."
› Record the demo in Supademo: ($38/mo Scale). Click through your product with the Chrome extension and it captures each screen in Screenshot mode. For each slide you write talking points — the key facts, not finished prose — and the bot turns them into a version personalized for who its speaking to. Supademo fires an event telling your page which slide the viewer is on, and that one signal is what lets the bot lead instead of caption.
› Train the bot in Chatbase: ($32/mo Hobby). Point it at your product docs, then set its rules to answer only from those docs and the slide points — and to hand off rather than guess when it's unsure. That guardrail is the most important setting.
One honest caveat: Chatbase meters by message credits, and a bot that narrates every slide and answers questions burns them faster than a normal support bot, so a high-traffic demo may need a top-up.
› Wire it together: One script on the page. It reads the quiz answers, listens for the slide-change event, and sends the visitor's profile plus that slide's talking points to the bot. The reply renders in the chat, and the bot leads. There's one small server-side piece so your API key never sits in the page — the companion build doc (Subscribers only) has the full script, the proxy, and the gotchas. Then test: run ten real sessions and watch where the narration drifts before you call it done.