Use case · Implementation and customer success
A knowledge base for every rollout
B2B implementations generate a pile of documents: the statement of work, the integration runbook, the training deck, the admin guide. Put them in a knowledge base the customer team can ask, so your CSM stops being the search engine.
The problem
Your CSM is answering from memory
The customer’s new admin asks how SSO was configured. The answer is in a runbook from eight months ago, and the person who wrote it has moved on.
How PageTruth handles it
What changes
One knowledge base per account
Separate indexes keep each customer’s documents apart. Invite their team by email.
Private by default
Members-only access, or a help center on your domain for the whole customer org.
Answers that point at the contract
When a question touches scope or SLAs, the answer cites the clause, not a paraphrase.
What to put in the knowledge base
- Statements of work and SLAs
- Integration runbooks
- Training decks and recordings’ transcripts
- Admin guides
What to watch in insights
- Questions per account
- Which customers are struggling, before it shows up in a renewal call.
- Recurring topics
- The parts of your product every rollout asks about, for your onboarding playbook.
- Ratings
- Thumbs up and down on answers, per account.
Other ways teams use it
- Support deflectionAnswer the repeat questions before they become tickets, and hand the rest to your team with context.
- In-app onboarding helpA side panel inside your product that explains the screen a new user is stuck on.
- Developer and API docsLet engineers ask your API reference a question and get the endpoint, the parameter and the example.
Give your customers answers, not a ticket number
Point PageTruth at your docs, publish a help center and drop the widget into your app. The free plan is enough to see it answer your own questions.