← Back to blog/Guides

How to Keep Your Help Center Up to Date After Every Release

Use release notes and recent support chats to find stale articles, update saved replies, and check that your chatbot gives the new answer.

F
Faizan Khan
2026-11-09 • 5 min read

When a release moves the billing menu, your support lead doesn't need the code diff. They need to know which customers see the new menu, when they see it, and which instructions still send them to the old one. Use the release note to find what changed and recent chats to find where an old answer is already causing trouble.

The release checklist

  • Ask the release owner what changed, who gets it, and when. Note whether the old and new experiences will run in parallel.
  • Search the help center for the old menu label, feature name, permission, or error message. Check the main article, onboarding guides, and saved replies that link to it.
  • Read a handful of recent chats on the same task. Record where customers got stuck, without copying names, account details, or raw transcripts into drafts.
  • Give each affected article one owner and one reviewer. Update the page that should be the source of truth before editing pages that link to it.
  • Verify the instructions with a test account on the right plan, role, and rollout cohort. Refresh screenshots only where they show a step that changed.
  • Publish for the appropriate audience. Test the public article, saved reply, and chatbot answer separately.
  • Review the next few chats on the topic. Fix any stale links, wrong answers, or missing handoffs while the release is still fresh.

Find the pages that need attention first

Look for three signals: customers say a button isn't there, agents paste a workaround instead of linking the article, or the chatbot cites instructions that only apply to the old experience. Prioritize inaccurate billing, access, or security guidance first. Then handle high-volume tasks and cosmetic updates in that order.

Imagine the invoice download moved from Settings to Billing, but only for workspace owners in the new layout. Update the invoice article first. If the old layout is still live, keep both paths with a clear cue for telling them apart. Update the saved reply to link to that article instead of maintaining a separate set of steps in the inbox.

Copy this change brief into your release tracker

Text
1Release and rollout date:
2Who gets the change (plan, role, region, rollout group):
3Old behavior -> new behavior:
4Customer wording from recent chats (sanitized):
5Canonical article and related pages or saved replies:
6Article owner / reviewer / publish date:
7Chat test question, expected answer and source URL:
8When to remove the old instructions:

You can automate reminders or ask AI for a first draft from that brief. Keep a person responsible for checking who actually gets the change, whether the instructions work, and when the draft should go live.

Check the answer, not just the publish date

Ask the chatbot the question a customer would ask: “Where do I get last month's invoice?” Open the source it cites and check the steps. Try the same question as someone without billing access. If the bot still uses the old article, check whether the index has refreshed and whether a duplicate source is still enabled.

Use the knowledge base article templates for the rewrite and the chatbot testing checklist for the release check. If you're setting up the broader workflow, start with customer support automation without replacing your helpdesk.

Continue This Guide