# Developing Walkthrough guides

Walkthroughs provide contextual guidance directly within an application's flow. They can be single- or multi-step Guides that assist users through processes in a streamlined fashion, using rules and trigger logic to create a tour-like experience.

## Using Adopt Editor for developing Walkthrough Steps, Actions, and Decisions

After [creating a Walkthrough-type guide](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/creating-guides.md) in Nexthink Applications and [accessing the guide in Adopt Editor](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor.md#accessing-specific-guide-in-adopt-editor):

* [Define walkthrough **Steps**](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides/defining-walkthrough-step.md) as the foundation of the walkthrough guide. Steps provide written instructions with customizable appearance, display options and behavior. In addition to Steps, you can define **Actions** and **Decisions** to enhance and personalize the walkthrough flow:
  * [Define walkthrough **Actions**](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides/defining-walkthrough-action.md) to automatically perform tasks on behalf of the user, such as clicking a button or copying and pasting values.
  * [Define walkthrough **Decisions**](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides/defining-walkthrough-decision.md) to set conditional logic that alters the walkthrough sequence, based on the presence or visibility of UI elements. When these conditions are met, the walkthrough can redirect to specific Steps.

Alternatively, you can [record a Walkthrough-type guide](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides/recording-walkthrough-guides.md). Instead of manually adding each step, you can start a recording session and perform actions directly within an application. Adopt automatically captures each interaction and converts it into a step.

## Using AI-generated suggestions to streamline walkthroughs

Walkthrough creation often results in multiple steps for actions that belong to the same UI component. Adopt reviews these steps and identifies when they represent a single meaningful interaction. This allows users to refine their recordings by grouping related actions and eliminating redundant steps, while maintaining a clear and accurate walkthrough. AI-generated suggestions can:

* Remove redundant or ineffective steps.
* Merge steps that would result in the same outcome.

To generate suggestions, click the magic wand button at the top of the Adopt editor.

### How Step Generalization interprets component interactions

Applications often include inputs like dropdown menus or date pickers, where a user selects a specific value during recording. By default, guides replicate that exact choice. Step Generalization allows Adopt to generalize these interactions, so viewers can select any value during guides. This makes guides more flexible and reusable across different scenarios where the selected input may vary.

<figure><img src="/files/EL6cposdZ8mjYMouGffW" alt=""><figcaption></figcaption></figure>

### How Adopt collects data for AI suggestions

Adopt uses structured telemetry to understand how administrators work with recorded steps and to improve the quality of suggestions over time. This data helps ensure that suggestions are accurate across different applications, environments, and UI component types.

Refer to the [Adopt Guide Recorder AI model card](https://docs.nexthink.com/legal/global-ai-hub/adopt-ai-model-card) documentation for more information.

***

RELATED TOPICS

* [Getting started with Adopt](/platform/user-guide/adopt/getting-started-with-adopt.md)
* [Guide creation & management from Nexthink Applications](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications.md)
* [Guide content development from in-app Adopt Editor](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexthink.com/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor/developing-walkthrough-guides.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.