Reviewing a generated draft

A recorded walkthrough becomes a draft, waiting under Guide drafts at the bottom of the collections list in Help Center.

Nothing is published automatically

Every generated guide arrives as a draft. It isn't on your help centre, it isn't in search, and the AI can't use it, until you publish it.

That's deliberate. A draft is a first version written from what you clicked; whether it's correct is a judgement only you can make.

What you'll get

A title, an intro, and the steps you performed — each with its screenshot and the element you clicked highlighted.

The description you gave when you started shapes how it's written, which is why a vague description produces a vague guide.

What to check

The steps you didn't mean to take. A wrong turn you corrected is still a recorded step. Delete those.

Wording that describes rather than instructs. Generated text can read like a narration of clicks. "Click Save" beats "The user then clicks the Save button".

Missing context at the start. Recordings begin where you began, which is often already halfway. Readers may need a sentence about where to start and what they need first.

Anything private in a screenshot. Passwords and card fields are blacked out automatically, but a customer's name in a list isn't. See What gets captured.

Edit it like any article

The draft opens in the normal editor. Rewrite text, delete steps, add headings, drop in a paragraph of explanation. It's an article from here on.

Number your sections Step 1 —, Step 2 — and search engines can show the steps directly in results. See Search engines and your help centre.

Then publish

Set live when you're happy. See Publishing a generated article.

When to record again

If the flow changed, re-record rather than editing screenshots one at a time. A recording costs a couple of minutes and produces consistent pictures; patching a stale guide rarely does.