Sharing and Embedding Walkthroughs

Once a walkthrough is recorded, you have three ways to publish it: a standalone share URL, an iframe embed on your own site, or a personalized playback bookmarklet. Pick whichever fits your audience.

This page covers all three. The patterns transfer across walkthroughs, so the embed code you copy for one walkthrough is identical in shape to every other — only the UUID changes.

The standalone share URL

Every walkthrough has a public-by-default URL of the shape:

https://app.getfoxchat.com/embed/<walkthrough_id>

The walkthrough_id is the UUID assigned at save time. You can find this URL in your walkthroughs dashboard — each row has a Copy share URL button. The URL renders the full-fidelity embed player: prev/next/replay/restart controls, narration, optional background music, optional lead-modal end screen, FoxChat-branded chrome.

This is the URL you send to a customer who needs to learn one specific feature, paste into a Slack message, or link from a knowledge-base article when you want a clean external page rather than an embed.

The iframe embed

To embed a walkthrough player inside one of your own pages — a help article, a feature landing page, a blog post — copy the iframe snippet from the dashboard. The shape:

<iframe
  src="https://app.getfoxchat.com/embed/<walkthrough_id>"
  width="100%"
  height="600"
  frameborder="0"
  allow="autoplay; fullscreen"
  title="FoxChat walkthrough">
</iframe>

Drop that into the HTML of your page. The embed adapts to the iframe width — visitors see the same player chrome, just in a frame instead of full-page. The allow="autoplay" permission lets the narration audio start automatically when the visitor clicks play.

The personalized playback bookmarklet

The third option is a bookmarklet that, when clicked on the original recorded site, replays the walkthrough as an overlay on the live product. Useful for:

• Onboarding new teammates — "drag this to your bar, click it on our app, watch how I send a campaign."
• Async product reviews — record a walkthrough of a bug repro, share the bookmarklet, the recipient runs it on their own logged-in account.
• Self-testing — click the bookmarklet on the live site after a deploy to verify your walkthrough still plays cleanly.

The dashboard generates a personalized playback bookmarklet with the walkthrough_id pre-embedded. Drag it to your bookmarks bar; you click it on any URL. See playing back walkthroughs for the controls.

Visibility settings

Each walkthrough has a visibility level you can set from the dashboard:

• Public — anyone with the URL can view; the URL is also indexable by search engines and can appear in our public walkthrough directory.
• Unlisted — anyone with the URL can view, but it's not indexable and not in the public directory. The default for newly recorded walkthroughs.
• Private — viewable only by you and other members of your FoxChat workspace. The share URL still resolves, but it requires a signed-in account with access.

Switch between levels at any time. URL remains stable.

Custom domain (optional)

If you'd rather the share URL live on your own domain — walkthroughs.yourbrand.com/<id> instead of app.getfoxchat.com/embed/<id> — configure a custom CNAME from the dashboard's Workspace settings page. We provision an automatic TLS certificate and route the embed player at the new hostname. The original app.getfoxchat.com URL keeps working as well, so existing links don't break.

Lead capture on the end screen

The full-fidelity embed player can show a configurable lead form on the final step. Useful for marketing walkthroughs — "watch the tour, then drop your email for a follow-up." Toggle it from the per-walkthrough settings page in your dashboard. The captured emails land in the conversations log alongside any chat your widget collected.

The bookmarklet replay does not show the lead modal — that surface is intentionally lean. If lead capture is important for a particular walkthrough, share the embed URL rather than the bookmarklet.

Translating walkthrough narration

Because narration is text, walkthroughs are translatable. Two paths:

• Per-walkthrough machine translation. The dashboard offers a one-click translate-to-language for any saved walkthrough. The output lands as a sibling walkthrough with the same step structure and translated narration; you review and tweak the wording before publishing the translated version.
• Visitor-side display translation. The embed player can also display the original narration with on-the-fly subtitles in the visitor's preferred language. This is the right path when you want one canonical walkthrough rather than maintaining N translated copies.

Pick the first path when you want full editorial control over the translated copy. Pick the second when you have many walkthroughs and translation accuracy matters less than coverage.

Analytics on shared walkthroughs

Every share surface logs the same events: walkthrough opened, step viewed, walkthrough completed, lead captured (if the lead modal is enabled). These events show up in your dashboard's Walkthrough analytics tab, broken down by visitor and by step. Use this to find drop-off points — if 80% of visitors abandon at step 3, that step's narration probably needs a rewrite.