AI support that answers from your help center
Build a support pilot on help articles you trust, useful follow-up questions and a clear path to a person when an answer needs a closer look.

The Aivah app today.
Choose a support problem that repeats
Start with a small set of questions that already have written answers. Setting up a workspace or finding a setting are good examples. Don’t use your first pilot to settle account disputes or bend your policies.
Write down what a good answer includes: the right step, anything needed first and what to do if it doesn’t work. Reviewers then have a clear standard, instead of asking whether a reply sounds helpful.
Give it a help source someone looks after
Use current help articles with clear headings and a named owner. Remove old versions that disagree before you add them. In Aivah, follow the Help Center guide on adding knowledge, then check the source status on the saved employee.
Keep a reference copy for testing. Ask the same question in a few everyday ways and check each answer against it. A source that finished loading is one check. A correct answer is another.
Make follow-up questions useful
For a setup problem, ask which step failed and what error the customer sees. Never ask for passwords, secret keys or private details you don’t need. If your help articles don’t cover the issue, say so.
Here is an example. The customer says setup is stuck. The employee asks for the step and the error message, and the customer shares them. The employee gives the documented fix, or passes the details to a specialist. The order matters, because a general fix may not fit the problem.
Plan the handover to a person before launch
Decide who owns the questions your AI employee can’t solve, and how customers reach them. A good handover includes the customer’s goal, the steps they already tried, the exact error if there is one and the question still open.
If you’ve connected an app that creates tickets, run a controlled test and check the record it makes. If the action isn’t available, give the approved support contact instead. Never say a ticket was created when it wasn’t.
- Check you’re allowed to share the details the next person needs.
- Don’t copy unrelated parts of the conversation.
- Make sure the right team can see the record.
- Explain what happens next without promising a response time you haven’t set.
Measure solved problems and customer effort together
Check whether answers are right, whether customers repeat themselves and whether cases come back. A low handover count can hide customers giving up. A high one can be right for hard problems.
Start with a reviewed sample and a small rollout. Keep a record of questions, answers, source versions and fixes. Then progress means fewer repeated mistakes, not just more chats.

















