These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Knowledge Base Builder
- Who it's for
- Service operations groups
Service operations groups
A service operations group may know a problem's root cause before its frontline team has a clear answer to use. Problem records hold the statement, owner, root cause and status. Change records hold planned work, risk, dates and rollback information. The article owner can use both records to keep published guidance aligned with the service's actual operating state.
How Knowledge Base Builder is set up for you
Known errors
Compare the problem finding with the current article body. An old workaround may need a clearer condition or a new instruction.
Planned changes
Check the scheduled start and end before changing the answer. A planned window alone is not the final service state.
Rollback
Read the change outcome after the window. If the change was rolled back, check whether the published article needs its prior instructions.
Service ownership
Keep the service owner and article owner visible so factual changes reach the person responsible for wording.
A service operations group may know a problem's root cause before its frontline team has a clear answer to use. Problem records hold the statement, owner, root cause and status. Change records hold planned work, risk, dates and rollback information. The article owner can use both records to keep published guidance aligned with the service's actual operating state.
Start with a service that has an open problem and an upcoming change. Agree who owns the service facts and who owns its articles. Review one published answer against the problem's root-cause text. Draft the correction and have the Article Reviewer test it with a service desk agent. Before the change window, identify which sentence may need updating. After the work, inspect the recorded change status and make the final article decision from that outcome.
The group can expand by service, using the same handoff each time. Feedback comments point to instructions that need another pass, while incident updates show how the answer worked in a particular case. Keep those sources distinct when deciding what to publish.
Features to start with
Roles on the team
- Admin
- Owns access setup and the operating rules for article and service records.
- Knowledge Editor
- Drafts and maintains assigned articles and reviews reader comments.
- Article Reviewer
- Checks article content and makes the publication decision.
- Service Desk Agent
- Records incidents and updates and uses article content to answer service questions.
- Service Manager
- Oversees service records and investigates recurring support issues.
Set up Knowledge Base Builder your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.