What gets captured (and what doesn't)

Worth knowing before you record on a page with real data on it.

What's recorded

Clicks on buttons, links and menus — identified by their visible label, so the draft can say "click Save" rather than describing a coordinate.

What you type into fields, and what you pick from dropdowns.

Form submissions.

Moving between pages, including within single-page apps.

Repeating the same action twice in a row is recorded once, so a double-click doesn't become two steps.

What's deliberately not recorded

Passwords, card numbers, security codes and one-time codes. Fields identified as sensitive — by their type, their autocomplete setting, or their name mentioning things like password, CVC, card, SSN, secret, token or OTP — have their values discarded, and the area is painted over in black in the screenshot.

So a recording that passes through a login or a checkout doesn't capture the secret parts.

The HeyThula widget itself. The recording bar and chat launcher are hidden from every screenshot, so your guide shows your product rather than our furniture.

Screenshots

Opt-in, via Enable screenshots on the recording bar. Then:

• One screenshot per step, taken at the moment you act.

• A blue box highlights the element you clicked, so the reader can see exactly where.

• The full page is captured, not a crop — context around the highlight is the point.

The bar shows a running count of how many have been captured.

Requirements

Chrome or Edge. Screenshot capture uses a browser feature Safari doesn't offer; on Safari the button says so and recording continues without pictures.

Share the tab, not the window or screen. The browser will ask what to share — choose the current tab. Anything else is declined, since it would capture things outside your product.

Limits

A recording captures up to 150 steps. Long enough for any sensible guide; if you're approaching it, the guide is almost certainly two guides.

Recording on real data

The safe habit is to record on a test account. Sensitive fields are protected automatically, but a customer's name sitting in a list isn't a password — nothing blacks that out.

Anything captured ends up in a draft you review before publishing, so you get a chance to catch it. It's easier not to record it in the first place.