Documentation gaps

What is a gap

A gap is a topic that generates real support volume but has no dedicated article in your Help Center. ResponZ identifies them by cross-referencing the conversation clusters (Top Questions) with the index of your existing Help Center.

A gap is not the same as a long-tail question. We only surface topics with enough recurrence to be worth a dedicated article.

How gaps are ranked

Each gap gets an impact score from three factors:

• Volume — how many conversations the gap accounts for in the window.
• Negative sentiment share — how often customers ended up frustrated when they hit this topic.
• Deflection potential — how answerable the question is with a self-serve article (a how-to deflects well, a pricing dispute does not).

Suggested article drafts

For every gap, ResponZ generates a draft article from the actual conversations on the topic: title, intended audience, table of contents, and a 200–400 word body. Open the draft, edit, paste into Intercom Articles. The goal is to remove the blank-page friction — not to ship the article as-is.

False positives

Sometimes a gap exists because your customers don't findthe article, not because it's missing. Two signals to look for:

• The cluster sits on a topic where you know the article exists. The fix is SEO / cross-linking inside the Help Center, not a new article.
• The cluster is dominated by Fin Agent failures. The article may exist but Fin isn't retrieving it. Check your scoring policy and the article's metadata.

Both cases can be marked as Not a gap from the gap detail view. The cluster stays visible in Top Questions but no longer counts as missing documentation.

Workflows

Monthly content sprint

Sort gaps by impact score, take the top 5, push them to the Sprint board as Write article tasks. One sprint of focused content writing typically eliminates 15–25% of the volume on the targeted topics within 6 weeks.

Cross-team handoff

Use the Export to CSV button to send the gap list to the content team or external writers, with the conversation samples attached.

Measuring impact

Once you publish an article, the gap is automatically reconciled on the next clustering run (within 24h). The volume on that cluster starts dropping as Fin Agent picks up the new content. Look at the 30-day delta column to see which closed gaps are actually deflecting traffic.