How Showalong works
Five steps, in this order: install the script, set what it may touch, map the common paths, let people talk to it, then approve what it learns.
-
Step 1: Add the script tag
Paste one line into your app’s HTML, the same place you would add an analytics snippet. Nothing happens until someone presses the button to talk.
The button can sit on your marketing site, inside your app, or both. You choose where it appears and who sees it.
<script src="https://cdn.showalong.com/v1/guide.js" data-site="YOUR_SITE_ID" async></script>Example. The real line, with your site ID, appears in your dashboard after sign-up. -
Step 2: Set what it may touch
List the pages the guide may open and the controls it may use. Anything that saves, sends, pays or deletes needs the visitor to confirm first, unless you mark it as safe for demos.
It stays on your site. It can’t follow links to other domains, and it can’t reach inside frames that belong to other sites.
-
Step 3: Map the paths people ask about
Walk through the flows you show most often and save them as paths. When someone asks for one, the guide follows the saved path at full speed instead of working out your menus while they wait.
For anything off the map, it reads the page and finds its own way. That works, but it is slower, so the common questions deserve a path.
-
Step 4: Let people talk to it
A visitor presses the button and speaks. The guide listens in the browser, answers out loud, and acts on the page while it talks: it points, circles, opens pages and fills in fields.
Captions show everything it says. People without a microphone, or somewhere quiet, can type instead and still watch it work.
-
Step 5: Approve what it learns
After calls, the guide drafts new paths and answers from what people asked and where it got stuck. You review each one, edit it if needed, and approve or dismiss it.
Nothing it learns reaches visitors until you approve it.
What it reads, and what it won’t do
These rules are part of the product, not settings you have to remember to turn on.
It reads the page, not a screenshot
The guide works from your page’s structure: its buttons, fields, links and headings. That is how it knows what each control is called and whether it is allowed to use it.
Text on your page is information, never orders
If a page contains words that look like instructions, the guide treats them as content to describe. Only the visitor and your settings tell it what to do.
It asks before anything real happens
Saving, sending, paying and deleting all wait for the visitor to say yes, unless you have marked that action safe in a demo workspace.
It stays on your site
No other domains, no other sites’ frames, and only the pages on your list.
Calls have limits you set
A cap on minutes per call and a monthly spending limit. When the limit is reached, the button hides until you raise it.
How fast is it?
We are measuring that now, on a sample app, with a public method. Until the results are in, we won’t quote a number.