ServiceNow Knowledge management
Capture answers once so users and agents can self-serve.
ServiceNow Knowledge Management organises articles into knowledge bases, IT, HR, Facilities, each with owners, categories and a publish workflow that moves articles from Draft through Review to Published. Knowledge-Centred Service turns a resolved incident into a draft article in one click. User criteria control who reads what, and articles deflect tickets at the portal.
- Knowledge bases & articles
- KCS: knowledge in the flow of work
- Access and feedback
- How it connects
- Common mistakes
Knowledge Management captures what the organisation knows, fixes, how-tos, policies, so users self-serve and agents stop solving the same thing twice. Done well it is the single biggest lever on ticket deflection.
Knowledge bases & articles
Content is organised into knowledge bases (IT, HR, Facilities), each with its own owners, categories, workflow and access. Articles move through a lifecycle:
KCS: knowledge in the flow of work
Access and feedback
How it connects
Articles deflect incidents at the portal, publish problem workarounds, and increasingly feed AI search and Now Assist answers, which are only ever as good as the underlying knowledge.
Common mistakes
- No review lifecycle, so articles go stale and lose trust.
- Ignoring user criteria and leaking internal content to end users.
- Treating authoring as a side project rather than part of resolution (KCS).
- No feedback loop, so bad articles are never found and fixed.