How walkthroughs work
What your users see when Skavelo walks them through a task.
The user asks how to do something
For example, "How do I export my invoices?" Skavelo answers in a sentence or two, including anything the clicks won't show, such as filtering the list first, and starts the walkthrough under the answer. When no drafted walkthrough fits, it builds one from the screens it has learned.
If the user asks Skavelo to do the task and gives the details, it fills in the form for them instead. See Filling in forms for users.
Skavelo highlights the first step
Skavelo scrolls the button into view and marks it with your chosen highlight style. Beside it, a small card shows the instruction, such as "Click Export CSV in the top right", with the step's title and details when it has them, and the step count. The widget goes down to its launcher so the card is the one thing to read.
To ask a question partway through, users click Ask on the card or the launcher. The widget opens on the same step, and closing it brings the card back.
If a step's button is behind something an earlier step opens, such as a field inside a window that Add Domain opens, the card points at that earlier button first: "First, click Add Domain." Once the window opens, the card moves to the field. If the step belongs on another page, the card points at a link there.
When there's nothing on the screen to point at, the step shows in the widget with what Skavelo can't find, a button to go back a step, and Ask about it, which fills in a question for the user to send. On phones, steps always show in the widget.
The user follows along
Clicking the highlighted button moves to the next step automatically. Users can also use Next and Back on the card. The cross on the card ends the walkthrough. If a step opens a new page, the walkthrough continues there.
The walkthrough finishes
After the last step, Skavelo confirms that the walkthrough is complete and asks whether it was helpful. The rating appears in Conversations.
The user can choose Show me again to go through it once more from the first step. A replay doesn't count as a new question and doesn't use any conversations from your plan.
When a button can't be found
Your app may show different screens to different users, or a button may only appear after something loads. If Skavelo can't find the button for a step, it first looks for a way in: a button from an earlier step that's on screen, or a link to the step's page, and points there. With nothing to point at, the widget says what it can't find and shows the instruction on its own, so the user can still follow along. Skavelo never highlights a different element as a guess.
Skavelo watches the page as it changes, so in single-page apps the highlight appears as soon as the button does.
Asking something else mid-walkthrough
If the user types a new question during a walkthrough, Skavelo ends the walkthrough and answers the new question.