Editing Tours: Callouts, AI Features & Brand Settings

Capture gets you the raw material; the editor is where a good tour becomes a great one. This guide walks the editor through each tour type, the AI features that speed you up, and the brand settings that keep everything looking like your product.

Your capture opens in the editor with every click shown as a tick on the timeline. Working left to right:

• Callouts — add or refine the text guiding viewers through each step. AI-generated callouts give you a first draft; your product knowledge makes them sing.
• AI narration — turn scripts into voiceover audio per callout. Listen before you publish — you’re the editor-in-chief. (After a text change, the Generate button re-enables so you can refresh the audio.)
• Speed, action, and target controls — fine-tune how each step behaves from the per-tick controls.
• End screen — choose what viewers see at the finish: a call to action, a redirect, a next step. Don’t leave them hanging.

Every edit reflects back in your library automatically.

Editing a Dynamic Tour

Editing HTML tour

Sandbox Tours open in a visual drag-and-drop editor on an infinite canvas — your captured pages laid out as a map you can rearrange:

• Your pages live in the rail on the right — every captured screen, with a + tile at the bottom to add more. It offers two paths: Capture NEW pages (record more pages with the extension, straight into this sandbox) and Add from Library (pull in pages from a capture session you’ve already recorded — the Add pages dialog groups captures by session date and time, each with a Select All). One rule to remember: pages only connect within a sandbox, so bring every capture session into the same sandbox rather than creating a separate sandbox per session.
• Build the branching with element links. Click any element on a page — a nav item, a button, a link — and the “Link this element to” panel opens: choose Page and pick the destination page (or Exit to end the experience there). Check “Apply to every page it appears on” for elements like nav menus, so one link works everywhere, then Save. This is how viewers move through your sandbox — there’s no separate connector line to draw.
• AI data editing (Edit with AI) — rewrite the underlying data in one prompt: re-theme the sandbox for healthcare, translate it to Spanish, or brand it for a specific prospect.
• Edit Content and image swap — adjust captured text and replace any captured image with your own, so the sandbox feels like the prospect’s environment.
• When you’re done, Preview to click through it as a viewer, then Update to save.

.Sandbox Tour Editing Guide

What the AI does: drafts callout text by reading your captured screens, and turns narration scripts into voiceover audio. Both are user-initiated — nothing runs unless you trigger it.

Models and data handling: callout generation uses OpenAI’s GPT-4o and o4-Mini to process capture images; image encodings are retained in OpenAI’s system for 30 days for log retention, then permanently deleted. Narration uses OpenAI’s tts-1-hd; OpenAI does not store narration data — we store your script with its tour so you can edit later. Everything travels over HTTPS, and AI features are covered under our MSA. We don’t extract names or PII from your images; anything visible in a capture exists only as part of the image, under the same 30-day policy. (One more reason to capture with demo data.)

Review before buyers see it: AI callouts are first drafts; narration only publishes after you generate and approve it. Known limitation: tours built before July 2025 aren’t compatible with the current AI narration — a re-capture brings them up to date (Auto-Update makes this quick if the click path hasn’t changed).

Translating a tour: two paths today. Cloning a tour and prompting AI rewrites the callouts in the new language — fast, but the wording changes. A browser-language auto-translation option (the player translates to each viewer’s browser language, preserving your wording) is available in beta for Dynamic Tours; ask your CSM about joining the beta.

Brand settings live in two places, with a clear hierarchy: account-level Tour Brand Settings set the default look for all your tours, and Demo Style Settings (inside Discovery Demo creation) override them for that demo. If a tour doesn’t look right inside a demo, check Demo Style Settings first.

At the account level, each setting has a tooltip and a HEX field — worth a one-time session with your brand team. Section by section:

• Global Styles — background, border, and text color for full-screen callouts; text size and font family apply globally. Custom fonts work if available in the Google Fonts library (choose a font file with bold/italic weights so formatting behaves). Legacy Primary/Secondary colors are being retired — leave them alone.
• Button Styles — buttons inside full-screen callouts. Settings labeled Active control the hover state.
• Callout Styles — your standard (non-full-screen) callouts.
• Answer Styles — Discovery Flow answers: dividing line = the border framing non-active answers; match answer-button color to your callout background for a cohesive feel; Active = hover, again.
• Click Target Styles — target color is locked in at capture time: changes apply to future captures, not existing ones. For an existing Dynamic Tour, Auto-Update gives you a fresh capture with the new setting (Auto-Update is available for Dynamic Tours only; other types need a fresh manual capture).

Click Save and every tour updates immediately.

[SCREENSHOT: Brand Settings page]

Why can’t I add AI narration to my older tour? Tours built before July 2025 aren’t compatible with the current narration feature. A quick re-capture (Auto-Update helps if the click path hasn’t changed) brings them up to date.

I edited my callout text but the narration didn’t change. Why? Narration doesn’t regenerate automatically — after any text change, the Generate button re-enables so you can refresh the audio when you’re ready.

How do I translate a tour into another language? Two paths today: clone the tour and prompt AI to rewrite callouts in the new language (fast, but wording changes), or ask your CSM about the browser-language auto-translation beta for Dynamic Tours, which preserves your exact wording.

Can I export my tour’s text? There’s no text export today — for translation needs, use one of the paths above.

What does the AI do with my captured screens? It reads them only to draft callout text, and only when you trigger it. Image encodings are retained by OpenAI for 30 days for log retention, then permanently deleted; narration data isn’t stored by OpenAI at all. All AI features are covered under our MSA — your security team is welcome to ask us for documentation.

My tour looks different inside a demo than in the editor. Why? Demo Style Settings override account-level brand settings for that demo. Check there first — that’s the answer nine times out of ten.

Capturing Tours with the Chrome Extension · Managing Your Tours Library · Adding Tours to Demos & Sharing