Building a Single Source of Truth for Customer Support
Ask where the definitive answer to a common question lives and you'll often get a pause, then a qualified answer: it's in the help center, but the exceptions are in the macro library, and the team actually follows what's in a pinned Slack message. That's four sources, and three of them are wrong at any given moment.
Consolidating sounds like a large project, and it can be. It doesn't have to be — provided you resist the urge to migrate everything.
Why duplication happens
- Tooling gaps. The help center couldn't hold internal-only detail, so a second copy appeared.
- Speed. Writing a macro takes two minutes; updating the canonical article requires review.
- Ownership vacuum. No named owner means no one to say “that belongs in the article.”
- Audience confusion. Customer-facing and agent-facing content are genuinely different, and teams solve it by duplicating rather than layering.
It's one *owner and one canonical statement* per fact. Multiple renderings for different audiences are fine — provided they all derive from the same source rather than paraphrasing it independently.
A consolidation that finishes
Step 1: Consolidate by demand, not by inventory
Don't start with a content audit of everything you own — that's how these projects die. Start with your top 50 questions by volume. Those are where contradictions actually cost you.
Step 2: For each, find every version
Search all sources for the topic. Expect surprises: the help center article, two macros that disagree, a slide from onboarding, and a Slack thread that contains the real current answer.
Step 3: Pick a winner and name an owner
Decide the canonical statement — which often requires an actual decision, not just editorial selection. Assign a named owner. This step is where the real value is created, and it's why consolidation is a governance exercise wearing a content costume.
Step 4: Redirect or delete the others
Not “mark as outdated.” Delete or redirect. Anything left retrievable will be retrieved, by an agent or a search index, at the worst possible time.
Step 5: Close the path that created the duplicate
If macros exist because updating articles is slow, consolidation will silently reverse within a quarter unless you fix the speed. This step is skipped constantly and is the reason these projects have to be repeated.
“Consolidation without fixing why people duplicated is a cleanup, not a solution. The second copy comes back because the reason for it never went away.”— Knowledge Agents
Layering instead of duplicating
The legitimate need behind most duplication is audience difference. Handle it by layering on one source rather than forking it:
- Canonical fact — the policy statement, owned and versioned.
- Customer rendering — plain language, published publicly.
- Agent rendering — same fact plus internal context, exceptions, and authority limits.
- Agent-assist rendering — the retrieved passage surfaced in the moment.
When the fact changes, it changes once. This is the architecture behind consistent omnichannel answers.
Keeping it consolidated
- Run a contradiction check on your top questions quarterly.
- Make canonical updates fast enough that shortcuts aren't tempting.
- Give every topic area a named owner with actual authority to decide.
- Archive anything unowned rather than leaving it retrievable.
Frequently asked questions
No. It means one owner and one canonical statement per fact. Different audiences can have different renderings, as long as each derives from the same source rather than independently paraphrasing it.
Fix the reason it appeared. Duplicates are usually created because updating the canonical source is slow or because no one owns the topic. Consolidation that doesn't address those conditions reverses within a couple of quarters.
