Keep help articles current after a release
After each release, find help articles that no longer match the product and draft fixes.
Customer support · Software · When something happens · Updated
Works with
- Slack
- Intercom
- Notion
Slack
Intercom
NotionHow do you keep knowledge base articles current after a release?
To keep knowledge base articles current after a release, point Maito at the release notes. It reads the changelog and the code changes, finds help articles that describe the old behavior, and drafts a rewrite for each. You get a list of affected articles and drafts ready to review.
How it's done today
Help center drifts until customers complain.
What Maito does
- Read what changed in the release
- Find articles that mention it
- Draft updated text and new screenshots
Example
Loop run: Release 2.41 published
Release 2.41 changed 3 things that help articles describe. Drafts are ready. 1. Export reports: the "Export all" button is now "Export" with a format menu. Steps rewritten. 2. Invite teammates: invites now expire after 7 days, not 30. 3. Connect Slack: the permissions screen has a new step. Missed by the changelog: "Reset your password" also names the old "Export all" menu in a screenshot caption. I fixed the caption too. I checked the help center in Intercom and the 2.41 changelog in the repository. Screenshots in 1 and 3 need retaking once you approve.
@Maito approve 1 and 2. Hold 3 until Leo confirms the Slack step stays.
Published 1 and 2. Article 3 stays a draft. I'll ask Leo in this thread and tell you what he says.
Maito (11:40 AM):
Release 2.41 changed 3 things that help articles describe. Drafts are ready.
1. Export reports: the "Export all" button is now "Export" with a format menu. Steps rewritten.
2. Invite teammates: invites now expire after 7 days, not 30.
3. Connect Slack: the permissions screen has a new step.
Missed by the changelog: "Reset your password" also names the old "Export all" menu in a screenshot caption. I fixed the caption too.
I checked the help center in Intercom and the 2.41 changelog in the repository. Screenshots in 1 and 3 need retaking once you approve.
Sam (12:05 PM):
approve 1 and 2. Hold 3 until Leo confirms the Slack step stays.
Maito (12:06 PM):
Published 1 and 2. Article 3 stays a draft. I'll ask Leo in this thread and tell you what he says.
How to set it up
- Ask your agent
“After each release, read the changelog, find help articles that no longer match, and draft the fixes. Post them in #support-docs and wait for my approval before anything is published.”
- Connect help center
- Intercom
- Notion
Not connected yet? Your agent sends you a link to sign in.
What it won't do
It can't see updates to product screenshots, so image changes are listed for a person to redo. It drafts text only for changes it can confirm.
Questions
Your help center in Intercom or Notion.
No. It drafts edits for review, and a person publishes them.
No. It also checks screenshots and captions in other articles, because changelogs often miss them.
