Can visitors steer the demo or try the product themselves?

Steering

• Phrases like "show me …", "take me to …", "what about …", "go back", "skip", and "that's enough" change the route. They work in every language the demo speaks; anything else is answered as a question.
• With more than one stop, the agenda shows each as done, now, or next, with Show next, Skip ahead, and Wrap up.
• Show me opens only read-only pages you approved. A visitor can add up to six stops per demo, going back included.
• Asking the guide to set something up works only where our team has set that up with you, with at most two builds per demo.

Try it yourself

• Try it yourself hands the visitor the screen. Their clicks, scrolling, and typing go to the demo browser, and the screen shows You're driving.
• A blocked click says which control and why, for example that Save is read-only in this demo, or that Invite is never used in a demo.
• Leaving your domains, or opening a blocked page such as payments, invitations, or logout, shows "That page is outside this demo, so the screen went back."
• Hand it back returns the screen to the guide.
• After two idle minutes, or ten minutes in total, the guide takes the screen back and carries on.

Ask about this

• On larger screens, Ask about this lets a visitor click a button, tab, or heading to ask about it. The guide shows the explanation in a callout right beside that spot on the screen (and in the chat) without leaving the page, and offers a one-tap Open button when they want to open or click that item.
• If nothing is named under that spot, the room says "Nothing named is under that point. Try the words on a button or heading."

Keep exploring

• When the walkthrough ends, the browser stays open for a minute, and Keep exploring on the finish card hands the visitor the screen again.
• It ends early if someone is waiting for a live seat, and the same limits apply.

More