Create your first experience
Finish one of the drafts generated in your Onboarding Space, on your own app, and preview it. Or draft it from your spec with your AI assistant.
The guided setup already drafted a welcome tour, a few feature intros and a checklist in your Onboarding Space. Step 3 is finishing one of them, on your own app, and previewing it. One hour. No developer.
You will have at the end: one short experience that runs end to end in preview on your app.
Pick the one to finish
Open Get Started, expand 3. Create an experience, click Open the space. Or go to Spaces > Onboarding in the sidebar.

Finish the Welcome tour first if your goal is onboarding. If your goal is something else, First experience by goal says which draft to finish, or which new experience to create with start something new. One experience, short, is the rule: three to five steps for a tour, one block for a banner, one question for a survey.
If the Space holds 0 experiences, the setup could not read your product. Click New Tour on the Get Started page and follow the same steps below from an empty tour.
Finish the Welcome tour
From your assistant
If your plan is written down, your assistant can do the drafting and you keep the checking.
Draft from your spec
"Read {spec page} and draft {ADM 0 Welcome tour} from it: same titles, texts and buttons, in the same order." Ask for a gap analysis first if the Onboarding Space already holds drafts: the assistant compares them with your spec and lists the differences.
Pin the steps that point at an element
The assistant never writes a selector. On a page of your app where Jimo runs, capture the element in the browser console with jimo.push(["get", "anchor:capture", [element]]) and paste the result to the assistant. See Pinning steps to your app.
Walk it with a preview link
"Send me a preview link for {experience} on {environment}." The link opens the draft in your app, without the dashboard and without publishing.
The prompts, ready to copy, are in Prompt library: setup.
Preview it
Click Preview at the top right of the builder. Your app opens with the tour running as a user would see it. Go through all the steps. Click Exit preview at the top left when done.
What preview does and does not prove

It proves the content and the positioning. It does not prove the trigger, the audience or the environment; those are Step 5.
Leave the rest for later
The checklist and the feature intros in the Space are drafts too. Leave them until the welcome tour is live for real users: wiring a checklist to tours is a second-level job, covered in Checklist and tours together and in What to build next.
Verify
The tour runs from the first step to the last in preview, on your app, with every step attached to the right element.
No step says "element not found" in the builder.
The theme is yours (colors, font), not the default. If not, fix the theme in Settings > Themes, then apply it from the builder's Theme tab: a change in Settings does not reach experiences that already exist.
Go further
First experience by goal: what to finish first for each goal, and what needs no selector at all.
The builder in full: Flow Builder, Content Builder, In-app builder, Positioning, Preview, Multiple languages.
Tours & Modals for everything a tour can do.
Next page: Step 4, Install Jimo
Last updated

