Types of In-App Guidance

Floating Prompt

Promote feature discovery and adoption with a short message that users can quickly read and dismiss. Place the prompt at one of nine different locations on a page.

For example, show a prompt to let users know they can pin a favorite list view, which helps boost their productivity.

Targeted Prompt

Highlight a specific element on a page by pointing to the element with an arrow and graying out the rest of the page. Select the specific element that you want to target and position the prompt at one of 12 positions relative to the element. You can also target specific fields on a record page, dynamic form, or Create window.

Or, let Salesforce determine the best location for the prompt depending on the current page configuration.

For example, show a targeted prompt on the Details tab of the Contact record page.

Docked Prompt

Drive feature adoption and help guide users through more complicated tasks. Embed images, videos, and step-by-step directions in a larger-sized prompt that stays available for users.

For example, show a docked prompt that includes a video to let users know about changes to the layout of the account page.

Comparison of Prompt Types

To help you select the right type of in-app guidance, compare supported features and environments.

Consideration	Floating Prompt	Targeted Prompt	Docked Prompt
Lightning Experience supported
Experience Cloud sites supported
Rich text supported			Supports more rich text options than floating and targeted prompts, including color, links, and list formatting.
Image
Embedded video
Optional Action button
Optional Dismiss button
Snooze icon
Behavior when a user leaves the page	Disappears	Disappears	Remains available. Users can maximize or minimize the prompt, or leave the prompt open as they navigate pages.
Size	Takes up a small area of the page, which users sometimes ignore.	Takes up a small area of the page, which users sometimes ignore.	Takes up a larger area of the page than floating or targeted prompts.
Special considerations		Changes to a floating prompt if the targeted element is removed from the page. Changes to a different position if the selected position is near the edge of the page or doesn’t entirely appear on the page. Shows a warning on the In-App Guidance page in Setup and in In-App Guidance Builder when the user doesn’t have access to the targeted element on the page.	Allows for more content than some users want or need. Too much information can overwhelm users. Review the writing tips in Tips for Writing Effective In-App Guidance.

Because floating prompts and targeted prompts take up a small area of the page, you can set up a schedule for the prompt so that users see it again. See Considerations for Creating In-App Guidance.

Walkthrough

Provide guided, in-context training and onboarding on a single page or across multiple pages. Connect up to 10 prompts in a step-by-step, guided experience. Users can see their progress through the walkthrough at each prompt, such as Step 1 out of 4.

Tip To keep users engaged and encourage completion, we recommend that you limit a walkthrough to 5 steps. Consider breaking up a longer walkthrough into two shorter walkthroughs.

• In Lightning Experience, walkthroughs can have a mix of all prompt types. We recommend docked prompts only for the final step so that you can include more information and calls to action.
• In supported Experience Cloud sites, walkthroughs can have only floating prompts.

For example, show a walkthrough that introduces new sales team members to a specific feature.

Prompts in a walkthrough behave differently compared to standalone prompts.

• Each prompt includes a progress button, labeled Next, except for the final prompt, where the button is labeled Finish.
• The final prompt provides an optional action link instead of an Action button.

A walkthrough can include prompts across multiple pages, even pages that only open when a user completes a required action. For example, create a walkthrough that shows users how to create a lead. Add prompts that highlight fields in the New Lead window. Then, add a final prompt that only appears on the lead record page after the user completes all the fields in the New Lead window and saves.

Note In this example, the Next button is unavailable in the final prompt that's associated with the window until the user completes a required action in the window. This pattern ensures that users complete a requirement before the walkthrough advances to the next prompt on a different page.