Most SaaS teams start teaching users the same way: a kickoff call, a recorded walkthrough and a help center. It works for the first ten customers. Then the calls stop scaling, the videos go out of date with every release, and people forget what they saw by the time they need it.
In-app training moves the teaching into the product. Instead of explaining everything up front, you show people how to do a task when they are about to do it, on the screen where they do it. It is user education that happens during the work, not before it.
Teach the job, not the interface
The most common mistake is a tour of the screen: "This is the sidebar. This is search. This is your profile." Nobody remembers it, because nobody needed it yet. People learn when they have a goal, so build training around jobs: "send your first invoice", "invite your team", "set up a weekly report". Each job gets its own short piece of guidance, shown to the people who have that job in front of them.
Match the format to the moment
- First session: a short welcome and an onboarding checklist of four to six jobs, starting with the one that shows value fastest.
- A whole workflow: a tour of three to seven steps that points at the real buttons as people use them.
- One control that confuses people: a tooltip on that control, nothing more.
- Something that changed: an announcement in a What's new feed, with a tooltip on whatever moved.
- Questions nobody predicted: an AI assistant that answers from your help docs and your real interface.
- Reference material: help articles people can search without leaving the page.
Checklist items can start tours, so the checklist becomes the course and each tour a lesson. In Cueston, the help hub keeps checklists, What's new, help articles and the AI assistant behind one launcher, so people always know where to look.
Build a path for each role
An admin setting up the account needs to learn billing, permissions and integrations. The colleagues they invite need the two workflows they will use every day. Giving everyone the same training wastes everyone's time.
Use audience rules to split them: by role or plan, by how new someone is (first seen in the last week, say), or by what they have and haven't done. A saved segment such as "Invited members, week one" can be reused across every piece of training for that group.
Train existing users on new features
Training isn't only for new signups. Every release teaches your existing users something, whether you plan it or not. Post the change in What's new with a button that starts a short tour of it. Then show the tour only to people likely to use the feature who haven't tried it yet, with an audience rule on the feature's event.
Don't turn training into interruptions
Ten helpful pop-ups in one visit are not helpful. Cap them. In Cueston, the workspace limits set the most pop-ups per visit, the most per day and how many minutes to wait between them. When more items qualify, the highest priority shows first and the rest wait for a later visit. Set tours to show once, and let people reopen them from the checklist.
Teach in their language
If your customers work in several languages, train them in theirs. People see guidance in their browser's language when a translation exists. Cueston supports 11 languages, fills in machine translations as a first draft for you to check, and exports everything as CSV or XLIFF for your translators.
Check that people learned
- Funnels show where people leave a tour and which checklist item they never finish. A big drop after one step usually means that step asks too much or points at the wrong thing.
- Goals show whether people go on to do the job the training was about. With a control group, you see whether the training caused it.
- A one-question survey after a key workflow, such as a star rating with a follow-up when the score is low, tells you what was still unclear.
- The AI assistant's low-confidence questions show which jobs your training and docs don't cover yet.
A starter plan for your first week
- Day 1: write down the three jobs a new user must do to get value, in order.
- Day 2: build a checklist of those jobs, with each item starting a short tour.
- Day 3: add tooltips to the two controls support gets asked about most.
- Day 4: add your help articles and turn on the AI assistant for everything else.
- Day 5: set a goal on the main tour, hold back a control group and publish.
Once the snippet is on your site, your team can build all of this in Cueston without a developer. See Cueston pricing, or read how onboarding checklists work first.
Frequently asked questions
What is in-app training?▾
In-app training teaches people how to use software inside the software itself, with tours, tooltips, checklists, announcements, help articles and AI assistants that appear when someone needs them.
Is in-app training the same as a customer education platform?▾
Not quite. Customer education platforms, often learning management systems, host courses and certifications outside your product. In-app training teaches tasks inside the product while people do them. Many teams use both: courses for deep learning, in-app guidance for getting the work done.
How do I train users on a new feature?▾
Announce it in your What's new feed with a button that starts a short tour, and show the tour only to people likely to use the feature who haven't tried it yet.
Do I need a developer for in-app training?▾
Only to add the Cueston snippet once. After that, your team builds and publishes training in the dashboard and picks elements on your site with the Chrome extension.