A new user signs up, skips the welcome tour and opens the reports page. They want a weekly report that shows one team only. Your tour covered creating a report, not filtering one. So they look for a help link, don't find the answer in the first article, and leave the tab open until they forget about it.
That is the gap AI user onboarding fills. Tours, tooltips and checklists teach the paths you planned. An in-app AI assistant handles the questions you didn't plan for, at the moment someone has them, on the page they are on.
What AI onboarding should do
Strip away the marketing and an AI onboarding assistant has three jobs:
- Answer "how do I…" questions inside your product, in your product's own words, without sending people off to a help center tab.
- Show where, not just say where. "Click Filters, then Team" is fine. Highlighting the Filters button on the page is better.
- Notice when someone is stuck before they ask: clicking the same spot again and again, clicking something that does nothing, or sitting on one page for a long time.
It does not replace your onboarding. The welcome tour and the checklist still set the path to the first result. The assistant catches the people who step off that path.
Why a generic chatbot is not enough
Put a general-purpose chatbot on your site and it will answer confidently from whatever it was trained on. It doesn't know that your settings menu is called Workspace, that the export button only appears for admins, or that you renamed Projects to Spaces last month. It can't point at anything, because it has never seen your interface.
Good answers need two kinds of context. Your help content tells the assistant how things are supposed to work. Your real interface tells it what is on the screen, so it can point at it. Without the second, you have a search box with better grammar.
What to give the assistant
- Your interface. In Cueston, the Chrome extension's Scan page adds a page's buttons, fields and menus to the assistant's UI elements, and the snippet learns more of them from what people click.
- Your help docs. Add the articles you already have. They ground the answers in how your product is meant to work. With the help hub on, they also become searchable help articles on your site.
- Guides. Cueston turns the questions your users ask into step-by-step guides. Publish the ones you agree with, and the assistant uses them in later answers.
Start with the three or four pages where new users spend their first session. Scan those, add the help articles that cover them, and most early questions are covered.
Catch people before they ask
Most people who are stuck never type a question. Friction detection watches for the signs instead: rage clicks (fast, repeated clicks on one spot), dead clicks (clicks on something that does nothing) and long pauses on a page. When it sees them, it offers help right there. Someone who was about to give up gets an answer without having to put the problem into words.
Where it fits next to tours and checklists
- Welcome and first result: a short tour and an onboarding checklist. You know the path, so lead people down it.
- One confusing control: a tooltip on that control.
- Something new: an announcement in What's new, with a tooltip on the new button.
- Everything else: the assistant. It handles the long tail of questions no tour will ever cover.
In Cueston these all sit behind one launcher, the help hub. It has tabs for the assistant, each person's checklists, What's new and help articles, and each tab only shows when it has something for that visitor.
Use the questions as onboarding research
Every question people ask is a note about where your product or your onboarding is unclear, so read them every week. Cueston's Quality page shows the assistant's confidence, how it responded and the questions it wasn't sure about, plus the pages that have no scanned elements or docs yet. A low-confidence question usually means the page hasn't been scanned or no help doc answers it. Fix whichever it is.
When the same question keeps coming up on one page, the page needs a tooltip or a tour step, not just a better answer. Set a goal and a control group on the new guidance to see whether it changes what people do.
Set it up in Cueston
- Open AI guidance in the side menu and work through the setup checklist in AI config.
- Connect the Chrome extension and use Scan page on the pages new users see first.
- Add your help docs.
- Turn on AI guidance chat, and friction detection if you want the assistant to offer help on its own. Both are switched on from Cueston, so once the snippet is installed your site needs no new code.
- Optional: turn on the help hub and give the assistant its own tab.
AI guidance and friction detection are included in every paid plan. See Cueston pricing, or read the AI guidance help article for each setting.
Frequently asked questions
What is AI user onboarding?▾
AI user onboarding puts an AI assistant inside your product that answers new users' questions in context, points at the right part of the interface and offers help when someone seems stuck. It works alongside product tours and checklists, not instead of them.
Does an AI assistant replace product tours?▾
No. A tour is still the fastest way to walk someone through a path you know they need. The assistant covers the questions a tour cannot predict.
How do I stop the assistant giving wrong answers?▾
Give it your real interface and your help docs, then review the questions it wasn't sure about. In Cueston, the Quality page lists low-confidence questions and the pages missing elements or docs, so you can fill the gaps.
Do I need a developer to add AI onboarding?▾
Only to install the Cueston snippet once, if it isn't on your site already. Scanning pages, adding docs and turning the assistant on happen in the dashboard and the Chrome extension.