Onboarding, API keys, integrations, billing. The same questions arrive every week, and the answer is usually in documentation you have already written. MotherX answers from your own docs, help articles and release notes, in the language the user writes in.
The documentation is usually good. The problem is that the user is mid-task with an error on screen and two minutes to spare, and will not search a docs portal. She opens the support form. Then the team spends the afternoon pasting links to pages that already existed.
Eight categories account for most of the volume in typical SaaS support, and every one of them is documented somewhere already.
First setup, inviting users and what has to be in place before anything works.
Keys, tokens, scopes and why the call returns 401 or 403.
What connects to what, and which fields sync in which direction.
What the code means, and what the user should do next.
What is counted, when it is counted, and what happens on a mid-period upgrade.
Roles, who can see what, and how access is revoked.
Which formats exist, and how to take the data with you.
Deadlines, what happens to the data, and how long it stays available.
Point at the docs portal or sitemap. The AI reads the pages and builds a searchable model of them.
Internal guides, PDFs and help articles only support has had access to.
A small script in the app or on the docs pages, so the answer is where the user is stuck.
Every question is logged, so you see which parts of the documentation fall short.
A topic that triggers many questions is usually a docs page missing a step. The dashboard ranks them, so you know which article to rewrite first instead of guessing from whichever tickets someone happens to remember.
It takes the repetitive part, meaning the questions that are already documented. Anything that needs an account check, judgement or a decision is handed over. The point is to clear lookups out of the queue, not to remove people from support.
Yes. Sitemaps and page links are described as sources, along with PDF, Word, Excel and PowerPoint. If the documentation sits behind a login, access has to be sorted out first.
Yes. The product pages list Norwegian and more than 90 other languages, and it normally answers in the language the user writes in, regardless of the language of the source.
Sources can be set up with scheduled crawling, so updated docs are picked up on their own. How often depends on the plan, so it should be confirmed specifically before you build it into a routine.
Conversations can be logged in the dashboard and deleted. If you turn on lead capture, the chat can ask for name and email, and you configure the purpose, consent and storage yourselves. Customer data is not used to train public foundation models.
Connect the docs and help articles, and see what the queue is actually made of. No card required. Setup included.
Try for free →