Questions, answered

Click Get started, then use Proto to configure Knowledge Base Builder for your business. Start with one active service, its owner, representative support cases and an article that answers a recurring question.

A Knowledge Editor drafts and maintains the answer. Each article also has a named owner, so the team knows who should check it after a service procedure changes.

An Article Reviewer reads the content and service context before the team changes the article from Review to Published. Agree this responsibility during setup.

Each feedback record links to an article. It can hold a helpfulness response, a comment and a submission date for the article owner to review.

Yes. Incidents, incident updates, problems and service requests hold their own case information. Editors can use those records to understand a question before writing reusable guidance.

An incident can refer to a service and an asset. A service has its own owner and status; an asset records its service, location and operating status.

Review the scheduled change and its recorded outcome with the service owner. The article owner can then revise affected instructions and send a material edit for another publication decision.

The article review queue and workboard show publication status. Feedback reports help the owner find comments that call for clearer wording.

Integration receipts record the provider, external event ID, received date, payload hash and result. Agree the connection and retry policy with the provider owner during implementation.