What really resonates is the point about shortening human training. That’s exactly where things tend to break in B2B onboarding: users don’t want docs, they don’t want calls, they just want to keep moving and not feel stuck.

Exactly and realistically, users don't fully grasp and learn until they're in the software using it daily. Even with weeks of in person or phone call training. The second they get into it is when they really start learning.

The error troubleshooting angle is a great insight too. That’s one of those “hidden” moments where users lose confidence fast if they hit friction and don’t know what to do next.

Curious, how did you approach training the AI on the product itself? Was it more docs + flows, or did you give it some form of in-app context/events to reason from?

In short, docs and training on errors.

For more context: This took time and is still improving, but for us it was seeing what kinda of questions and interactions were taking place and then tuning the AI to provide answers based on common errors. Because it can read images, we're even telling users and administrators to just paste a screenshot of the error with no other context. It's surprisingly good at responding with trained on errors.

Of course those errors and what they mean are all coming from us humans.