Assisted onboarding
Guide new users to their first completed task.
The agent explains the next step, asks for the information it needs and helps users make progress in your app.
The first result matters more than the guided tour
Classic onboarding shows the interface: here is the menu, here is the button. It explains where things are, not how to get what the user came for.
An agent can do the opposite: start from the person's goal and support them to a real result in the application. What they remember then is not where a button sits, but that they succeeded at something.
What guidance changes
Situated help
The agent knows which screen and which record the user is working on. Its help addresses the situation, not a generic documentation article.
Information asked at the right moment
Rather than a long form up front, the agent asks for what it needs when it needs it, and explains why.
Resuming after interruption
An interrupted user finds their place again. Task context is retained, so nothing has to be redone.
A useful reminder, not a chase
Offering to resume a started task is not the same as chasing someone who asked for nothing. That distinction is configurable.
Difficulties encountered during onboarding surface through Vigie: they often reveal as much about the application itself as about the agent.
Frequently asked questions
How do we measure whether it works?
By the real result: is the task completed, and in the application? A click on a help button or a tour displayed proves nothing. We present no conversion figures: that is measured at your site, during the pilot.
Does the agent replace our documentation?
No, and it can draw on it. Documentation stays useful for depth; the agent handles the immediate need in the context of the screen.
What if the user is genuinely stuck?
The agent must be able to say it cannot help and point to a human. Help that persists without resolving is worse than no help.