KCS (Knowledge-Centered Service)
A methodology where solving a customer issue and capturing the knowledge are the same act.
You want solved cases to improve the next answer instead of disappearing into the queue.
An agent resolves a new edge case, improves the shared article in the workflow, and the next agent reuses the verified answer.
Treating KCS as a documentation project owned outside the resolution workflow.
KCS is a discipline for building a knowledge base as a byproduct of doing support, rather than as a separate documentation project nobody has time for. The core loop: reuse what exists, improve it as you use it, and create an article the moment you answer something new.
It is a method, not a metric, though maturity is often tracked via reuse and article-health measures.
What it hides: KCS lives or dies on culture and workflow integration. Bolt it on without protecting the time to capture and review, and you get a graveyard of stale, half-written articles that erode trust in the whole knowledge base. The methodology is sound; the failure mode is treating it as a tooling purchase.