Amalgamation · Part 2 — Same Question, Five Answers

A fast way to measure trust in your help system is brutally simple: take one common question and count how many versions of the answer exist across your surfaces. If you get five, you don’t have “coverage”; you have confusion. Customers hesitate. Your AI bot tries to average contradictions. Teams fix one copy and miss the others. The result is slower time-to-value and preventable tickets.

This pattern usually appears for good reasons. Support writes an FAQ to stop an escalation. Training builds a short course for onboarding. Product adds a tooltip to reduce clicks. Docs creates a page for a specific scenario. All of that is understandable—taken alone. Together, it fragments truth. And when truth fragments, customers stop trusting any single answer.

The better pattern: one canonical answer with many doors

You don’t need a new platform to fix this; you need a contract.

1. Choose the canonical page. It holds the current, complete answer. It’s short, visual, and practical: a tight overview, 3–7 steps, one or two screenshots or a 90-second clip, and a small box for common gotchas.

2. Link other surfaces to it. FAQ, course, tooltip, and bot answer all point back to that page. They can add context, but not divergent steps.

3. Stamp it. Put “Last reviewed: <date> • Owner: <name>” at the top so everyone knows where to send changes.

4. Keep titles identical. The same title and first sentence wherever an answer appears. Search results and previews should look like the same thing—because they are.

How to pick the canonical page (and avoid debates)

• Go where customers land. If most people already arrive via search, make the doc page canonical. If most people arrive via product, consider a lightweight in-app hub with a deeper link.

• Prefer the smallest path. The canonical answer is the one with the fewest clicks to apply.

• Choose what’s easiest to keep accurate. If one team already updates weekly, make that page the home and link others to it.

A small illustrative example

Your top question is “How do I connect our CRM?” Today you have: a three-paragraph support FAQ, a 15-minute training module, an empty-state button in-product, and two doc pages because the menu moved last quarter. The fix is one canonical page titled “Connect Your CRM (3 Steps).” The page has the exact navigation, a pair of screenshots, and a 60-second clip. The support FAQ becomes: “Looking for steps? See: Connect Your CRM (3 Steps).” The training module opens with the same title and links to the page. The empty state button points to it. The older doc page gets a bold banner: “Looking for the current steps? See: Connect Your CRM (3 Steps).” When the UI changes, you update one place and every door still leads there.

Common pushbacks (and simple answers)

• “Our audiences are different.” Great—add short context up front. The steps still live in one place.

• “Marketing wants a prettier version.” Fine—style the wrapper. Link to the canonical steps.

• “Legal needs a special note.” Add a “Notes” box with a clearly labeled legal blurb. Don’t fork the steps.

Signals you’re winning

People share links, not screenshots of partial steps.

AI answers improve because retrieval points to one authoritative source.

Updates shrink from hours to minutes because you’re changing one page with clear ownership.

Metrics to watch

Share of topic traffic that lands on the canonical page (it should rise).

Bot miss rate for the topic (should fall as retrieval simplifies).

Time to update when something changes (should shrink).

Cheat out (doable today in your lane)

Grab one high-volume question from the last 30 days of tickets. Make or pick the canonical page. Add the review stamp. Replace two local answers with a link to that page. Standardize the title and first sentence everywhere that points to it.

Two moves this week

Title discipline. Use the same title and first sentence across all places that point to the canonical answer. Consistency here does most of the work in search and previews.

Redirects that teach. At the top of older/duplicate pages you can’t retire yet, add: “Looking for the current steps? See: <canonical title>.”