In-app onboarding examples: 7 patterns with sample copy
In-app onboarding is the set of screens, tips and prompts that guide a new user inside your product. The seven patterns below cover most SaaS products: a welcome message, a short tour, a checklist, an empty state with one action, a tooltip on a new feature, a contextual prompt, and a check-in survey. Each has sample copy you can adapt, when it fits, and what to measure.
These are patterns, not teardowns of other companies' screens. The sample copy is written for a made-up project tool called "Plan" so you can see the tone. I build JustOneCX (disclosure), and I note where the tours, checklists, announcements and surveys modules cover a pattern. The patterns apply to any stack.
What do good in-app onboarding examples have in common?
- One goal. Each pattern moves a person toward your activation event, the first action that shows value.
- Short copy. One idea per message, in the user's words.
- Right moment. The prompt appears when it helps, not on first load for everyone.
- A way out. People can skip or dismiss without losing their place.
Pattern 1: the welcome message
What it is: one short message right after first sign-in.
Sample copy:
Welcome to Plan, {first_name}. Create your first project and invite a teammate. It takes about two minutes. [Create a project]
Use it when: your product needs one clear first step. Skip it when: the screen already has an obvious first action. Do not add a message just to have one. Measure: the share of people who click the button and then complete the first step.
Pattern 2: the short tour
What it is: three to five tooltips that point at real parts of the screen.
Sample copy for step 2 of 4:
Add tasks here. Type a task and press Enter. You can add dates later. [Next]
Use it when: the main screen has a few controls people must find. Skip it when: you need more than five steps. Split it into two tours, or cut steps. See product tour best practices. Measure: how many people start, finish and skip, and the step where most people stop. The tour results in JustOneCX show started, finished, skipped and abandoned, with a per-step table.
Pattern 3: the checklist
What it is: a small progress list that stays in the corner and ticks off as people do the work.
Sample copy:
Get set up (1 of 4 done) ☑ Create a project ☐ Add three tasks ☐ Invite a teammate ☐ Set a due date
Use it when: reaching value takes several separate steps, and people can do them in any order. Skip it when: the path is one step. A checklist of one item is just a button. Measure: which task people stop at, and whether people who finish the list activate more than people who do not. Tasks can complete from a click or from an event your code sends. The full setup is in SaaS onboarding checklist.
Pattern 4: the empty state with one action
What it is: the screen a new user sees before they have any data, turned into a prompt instead of a blank page.
Sample copy:
No projects yet. A project holds your tasks and your team. Start with one. [Create your first project]
Use it when: a main screen is empty on day one. This is the cheapest pattern, because it is part of your UI, not an overlay. Measure: the share of people who leave the empty screen by clicking the action.
Pattern 5: the tooltip on a new feature
What it is: a small hint pointing at a feature, shown only to people who have not tried it.
Sample copy:
New: recurring tasks. Repeat a task daily, weekly or monthly. [Got it]
Use it when: you ship something a subset of users will want. Target the people who use the related area, not everyone. Skip it when: a feature is relevant to everyone and needs a longer explanation. Use an announcement instead. See in-app announcement best practices. Measure: how many people who saw the hint then used the feature. See measure feature adoption.
Pattern 6: the contextual prompt
What it is: a message triggered by what the user just did, not by time.
Sample copy, after the user adds a fifth task:
Working with others? Invite a teammate and assign tasks to them. [Invite a teammate]
Use it when: an action signals a next step. The trigger should be an event your app sends. Segments help here: show it only to people who have not invited anyone yet. Skip it when: you cannot say what the person is trying to do. A prompt at the wrong moment is noise. Measure: the share who take the suggested action within a day.
Pattern 7: the check-in survey
What it is: one short question after a task, so you hear what was hard while it is fresh.
Sample copy:
How easy was it to set up your first project? 1 (very hard) to 5 (very easy) What made it hard? (optional)
Use it when: you want to find friction in onboarding. Show it once, right after the task ends. Customer effort score questions covers the wording. Measure: the average score and the comments, split by new and returning users.
How do you choose which patterns to use?
Start with the cheapest and work up.
- Fix your empty states (pattern 4). No tool needed.
- Add a welcome message (pattern 1) only if the first step is not obvious.
- Add a checklist (pattern 3) or a short tour (pattern 2), one of them.
- Add contextual prompts (pattern 6) once you know your activation event and where people stall.
- Add a check-in survey (pattern 7) to find out what is still hard.
Do not use all seven on day one. Too many overlays teach people to dismiss everything.
How do you build these in JustOneCX?
- Tours cover patterns 2, 3 and 5: steps that point at your page, a checklist whose tasks complete on a click or an event, and a preview that plays the draft on your live page.
- Announcements cover patterns 1 and 5 as a modal, slide-out or banner, with targeting by segment.
- Surveys cover pattern 7 with a rating question and an optional follow-up.
- Analytics gives the activation rate to check whether any of it helped.
Targeting needs identify() after sign-in so segments know who is new. See the product pages for Product tours, Announcements and Surveys. If you are comparing tools first, read best user onboarding tools.
How do you know it worked?
Judge onboarding by activation, not by how many people saw a message.
- Pick one activation event.
- Note the activation rate before the change.
- Change one pattern.
- Compare the rate after enough new users have come through.
A few users tells you nothing. Wait for enough signups before you decide.
Frequently asked questions
What is in-app onboarding?
It is the guidance a new user sees inside the product: welcome messages, tours, checklists, tooltips, empty states and prompts. It differs from onboarding emails, which reach people outside the product.
How many steps should an onboarding tour have?
Three to five. Longer tours lose people. If you need more, split into two tours that show at different moments.
Should I show onboarding to every user?
No. Show it to new users, and show feature hints only to people who need them. A returning customer does not need a getting-started list.
What is the best in-app onboarding pattern?
The one that moves people to your activation event. For most products, a fixed empty state plus a checklist or a short tour gives the most for the least work.
Do I need an onboarding tool?
Not for empty states, which are part of your UI. A tool helps for tours, checklists, targeted prompts and measuring results without a release for each change.