Partner Portal Knowledge Assistant
Vehicle Services · 2026 · Customer Support Automation
Partners get the specific answer inside the portal, scoped to who they are, from documentation the client updates whenever the platform changes.
The challenge
A vehicle services company runs a custom platform its partners log into. Everything a partner needs to know about using it sits in one place: the platform manual, a PDF hundreds of pages long.
Nobody reads a manual that long. Partners asked instead, and every question landed on the same operator. To answer precisely she kept her own index by hand — a document tracking where inside the PDF each answer lived — because writing an answer from scratch every time was not possible.
It worked, and it had a ceiling. The index was hers, maintained by her, and a partner got the answer when she was at her desk.
What we built
The second deployment of an engine the client already had. The same retrieval assistant that answers the public was deployed again inside the portal, this time behind the login.
- It answers from the platform manual, hundreds of pages of it, and returns the steps for the exact question — "how do I do this specific thing" — instead of a general reply.
- It knows it is running inside an authenticated platform, so answers are scoped to the user who is logged in.
- The documentation stays the client's. They update the manual when the platform changes and the assistant answers from the updated version. Nothing comes back to us to be rebuilt.
- It runs in the client's own cloud account, next to the platform it documents.
One engine, two portals. Outside, it answers the public and queries the client's network live. Inside, it answers specific questions for someone the platform already knows. One build, pointed twice — the second deployment cost a deployment, not a project.
The perimeter is stated rather than implied: the assistant answers from the documentation. What the manual does not cover goes to a person, with the conversation attached.
The results
The hand-written index is gone. The operator is not — she stopped being the index.
Partners get the answer inside the platform, at the moment they are stuck in it, without waiting for someone to be at a desk. And because the client controls the manual, the assistant follows the platform: a documentation update is the whole change process.
| Number | What it measures |
|---|---|
| 100s | pages of platform manual the answers are drawn from |
| Logged in | every answer scoped to the authenticated user |
| 1 engine | two deployments: public site and partner portal |
| Client-updated | the client changes the manual, answers change with it |
What you get
The assistant deployed inside your portal, behind your login, answering from documentation you keep control of, in your own cloud account. Process audit first, scope in writing, and 30 days of support. The same engine pointed at your own employees is Employee & IT Support Automation; pointed at the open web, it is the 24/7 customer assistant.
Sitting on a manual nobody reads and one person who knows where everything is? Start with the free AI Audit, or book a call.