All posts

How to write product tour copy people actually read

Nobody reads a tooltip. They glance at it, between two clicks. Write for that glance and the tour gets read anyway.

4 min read
Isometric illustration of a tooltip card with a short bold title, two text lines and a small blue button

Most product tours are written by the person who built the feature, five minutes before release. The result explains the feature. The user, meanwhile, wanted to know what to click.

Tour copy is a small, odd kind of writing. It sits on top of the thing it describes, it is read in a second or two, and the reader is in the middle of something. These rules are for that situation.

Write for a glance, not a read

A visitor looks at a tooltip the way they look at a road sign. They take in the title, maybe the first line, and act. Everything you write should still work if only the title is read.

  • Title: under about six words. Say what to do or what this is.
  • Body: one or two short sentences. Often one is enough.
  • Button: one to three words.

If a step needs a paragraph, it is probably two steps, or a help article that a step links to.

One step, one idea

Each step points at one element, so it should say one thing about it. A step that explains the filter, the sort order and the export button in the same tooltip makes the user read three things while the spotlight shows one.

Split it, or cut it. Not everything on the screen needs a step. A good tour leaves out most of the interface and covers the path to one result.

Say what the user gets, not what the feature is

Describes the featureSays what the user gets
This is the Projects menu.All your work lives in projects. Start one here.
Use the filter panel to filter results.Only see what is yours: filter by owner.
The Reports module offers powerful dashboards.Share a live dashboard with one link.
Click here to access integrations.Connect your calendar so deadlines show up there.

The spotlight already says “this is here”. The text can spend its few words on why it matters.

Lead with a verb when the user has to act

When a step asks for an action, put the action first: “Create your first project”, “Pick a template”, “Invite one teammate”. A user who reads only the first two words still knows what to do.

When a step only shows something, a short noun phrase is fine: “Your activity this month”. Stepsome already tells these apart when you add steps: buttons and links become a step the visitor clicks, fields become a “Fill in” step, and text or images become a “Take a look” step. Let the copy follow the same split.

Name the next thing on the button

“Next” is fine for most steps. It tells the user nothing, but it does not need to. The buttons that deserve attention are the first and the last:

  • The welcome popup: “Show me around” or “Take the two-minute tour” beats “Start”. Mention how long it takes if it is short; that is the main thing people want to know.
  • The last step: “Done” closes the tour. If there is a natural next move, name it: “Create my project”.
  • A way out: every tour can be closed with ✕. You do not need a “Skip tour” button that sounds like a dare.

To change a label, select the step and open Content → Button. Leave it empty for “Next”.

Use the user’s words, not your internal ones

Teams name things while they build them, and those names leak into tours: “workspace entities”, “the v2 composer”, “sync jobs”. Use the label that is on the screen. If the button says “New project”, the tooltip says “project”, not “workspace item”.

A quick test: read the step aloud to someone outside the team. Any word they ask about should go.

Show when telling takes too long

Some things are faster to watch than to read: a drag and drop, a keyboard shortcut, a result that appears after a few seconds. Add an image or a short looping clip to the step instead of another sentence. A tooltip, popup or highlight can hold an image, a GIF or a video. You can record the clip in your own app; How to make a demo video of your web app shows how.

Let AI do the first pass, then edit

Writing ten tooltips in the same tone is tedious, and that is where an AI model helps. In the Stepsome editor, open the Tour tab → AI copywriter and click Polish all step texts. It rewrites every step with your own Anthropic or OpenAI key, and a toast offers Undo if you do not like the result.

Treat the output as a draft. Check it against the rules above: does each title say what to do, is each step one idea, are the words the ones on the screen? AI copy tends to be a little longer and a little more enthusiastic than it needs to be. Cut the adjectives.

The key is stored in your browser and only sent to the provider you picked. It is never part of your site file.

A checklist for every step

  1. Does the title work on its own, in under six words?
  2. Is it one idea about the one element in the spotlight?
  3. Does it say what the user gets, rather than what the feature is?
  4. Does an action step start with a verb?
  5. Do the words match the labels on the screen?
  6. Could an image say it faster?

Then preview the tour from start to finish at normal speed, as a new user would. If you catch yourself skimming a step, so will they. Cut it down, and check later where people stop: How to measure user onboarding shows how to read drop-off per step.