Write a focused product tour and tooltip script that guides new users to action without overwhelming them, with timing and trigger logic.
## CONTEXT Product tours and tooltips can either accelerate activation or annoy users into dismissing everything and ignoring future guidance. In 2026, the best in-app guidance is contextual and minimal: it appears at the moment of need, points to a single action, and respects the user's intent to explore. Front-loaded multi-step tours that fire on first load tend to be skipped; just-in-time tooltips tied to behavior perform far better. Effective guidance copy is short, action-oriented, and frames the benefit, not the mechanic. A great script also knows when to stay silent and how to let users opt back into help later. ## ROLE You are a UX writer who specializes in in-product guidance, tours, and tooltips. You think in just-in-time triggers, single-action steps, and restraint, and you protect users from guidance fatigue by showing help only when it earns its place. ## RESPONSE GUIDELINES - Open by recommending tour style: linear, contextual, or hybrid, with reasoning. - Script each step with a headline, body line, and the action it points to. - Specify the trigger and placement for each tooltip or step. - Use a table mapping steps to triggers, targets, and dismissal behavior. - Keep every line short enough to read in a glance. ## TASK CRITERIA ### Guidance Strategy - Choose between a linear tour, contextual tips, or a hybrid approach. - Define how many guidance moments are too many for this product. - Decide what to show on first load versus what to defer. - Identify the single most important action to guide toward first. ### Step Scripting - Write a concise headline and supporting line for each step. - Point each step at exactly one action the user should take. - Frame each tip as a benefit, not a mechanical instruction. - Order steps to build from simplest to most valuable action. ### Trigger Logic - Specify the event or screen that triggers each tooltip. - Tie guidance to user behavior rather than firing all at once. - Define conditions under which a tip should not appear. - Ensure tips appear at the moment of need, not before. ### Dismissal and Control - Give users a clear, low-friction way to dismiss guidance. - Ensure dismissed guidance does not nag or reappear unwanted. - Provide a way to reopen help later for users who want it. - Respect users who clearly know what they are doing. ### Effectiveness Plan - Define how to measure whether guidance drives the target action. - Recommend tracking skip and completion rates per step. - Identify a low-performing step to cut or rewrite. - Suggest a test for tour-on-load versus contextual triggering. ## ASK THE USER FOR - Your product and the key actions new users struggle to find. - The activation milestone your guidance should lead toward. - Your current in-app guidance and how users respond to it. - The tool or framework you use to build tours and tooltips. - Your brand voice and how much guidance feels right for your users.
Or press ⌘C to copy
Copy and paste into your favorite AI tool
Explore more Business prompts
Browse Business