Plain integration guide

How to keep Plain up to date

Find the Plain help center articles that recent changes to your product made incorrect, before customers or your AI agent answer from them.

Book a demo Audit your help center for free →

Keeping help centers accurate at

The short answer

What Plain offers: Plain has features like Knowledge gaps, Ask AI conversation logs and article generation from threads to find and fill holes in your knowledge base.
Where it stops: All three start from a customer question or a support thread, so none can proactively catch that your product changed and an article is now wrong.
Where Solo fits: Solo compares your code and feature flags with your articles, flags the ones a change made wrong, and drafts fixes that a person approves.

On this pageShort answer

Why it matters

Why an accurate help center matters

Your product ships quickly, and the people who write articles hear about a change late or not at all. Meanwhile customers can't self-serve, Ari answers from stale text, and search results quote articles that are no longer true.

Reduce tickets with self-serve support

A customer who finds the right article, or gets the right answer from Ask AI, never opens a thread. A wrong article sends them to your team, and the conversation arrives as a new thread.

Ari resolves more threads

Ari answers from your knowledge sources, including your published articles, and hands off to your team when unsure. A wrong article means a wrong answer or a handoff someone has to pick up.

Public articles show up correctly in search

Search engines index public articles, and Plain also publishes an llms.txt listing every published article for AI answer engines. A wrong article can be quoted back to people before they reach you.

Built-in tools

What Plain already offers for keeping help center articles current

Plain has good tools for finding the questions your articles don't answer and for drafting new ones. Each starts from a customer or a thread, though, and none can see that your product changed, so wrong articles can pile up unnoticed.

Stage	Plain's features	Missing features
01Know upcoming changes	Plain has no feature for this stage, so notice of a change to your product has to come from outside the platform, like a product manager or a developer.	Nothing warns you that an article is about to become out of date. Plain doesn't read your code or feature flags, so a change reaches support only if someone mentions it.
02Identify outdated articles	Knowledge gaps groups the questions your AI agent handed off because it found no trustworthy answer, and every conversation with the help center's AI assistant is logged for your team to read.	Both show a gap after customers have already asked. Neither compares an article with your product, so a wrong article that still reads well goes unnoticed.
03Draft updated copy	The knowledge base editor's AI refinement offers Tidy up, Shorten, Simplify, Fix tone and custom prompts on selected text, and Generate Help Center article turns a solved thread into a draft.	Drafts come from past threads and your own instructions, not from what your product does now, so a fix is only as correct as its source.
04Collaborate on updates	Articles stay in Draft, visible only in the Plain app, until someone sets them to Published, and drafts from the fill-knowledge-gap skill are saved for review. Gap tasks arrive unassigned for your team to pick up.	The docs describe no review step beyond Draft and Published, and nothing shows a reviewer which change to your product an article needs a look for.
05Publish changes	Setting an article to Published puts it live, the help center's AI assistant reads only published articles, and the GraphQL API's upsertHelpCenterArticle mutation can create or update articles in place.	Publishing is a manual step. Nothing publishes an update when a feature flag turns on, so an article goes live on someone's schedule, not when your product changes.

With Solo

Managing your Plain help center with Solo

Plain can tell you which questions your articles failed to answer, but it can't see that your product changed. Solo reads both your code and your help center, flags the articles a change made wrong, and drafts the fix. Your team reviews each one before it goes live in Plain.

What Solo adds to Plain's built-in tools

Stage	Plain without Solo	Plain with Solo
01Know upcoming changes	Plain has no feature for this stage, so notice of a change to your product has to come from outside the platform, like a product manager or a developer.	Solo reads your code changes and the feature flags tied to them, and warns you which articles are about to go out of date, so support hears what changed before customers ask.
02Identify outdated articles	Knowledge gaps groups the questions your AI agent handed off because it found no trustworthy answer, and every conversation with the help center's AI assistant is logged for your team to read.	Solo compares every change to your product with your articles and flags the wrong ones with the affected text highlighted, before a customer asks about them, even when the article still reads well.
03Draft updated copy	The knowledge base editor's AI refinement offers Tidy up, Shorten, Simplify, Fix tone and custom prompts on selected text, and Generate Help Center article turns a solved thread into a draft.	Solo drafts the replacement from your code change itself, so the fix reflects what your product does now, and shows it next to the current wording.
04Collaborate on updates	Articles stay in Draft, visible only in the Plain app, until someone sets them to Published, and drafts from the fill-knowledge-gap skill are saved for review. Gap tasks arrive unassigned for your team to pick up.	Each fix lands in a review queue with your product change behind it, so your team can accept, edit, add it to a draft or reject it knowing what changed.
05Publish changes	Setting an article to Published puts it live, the help center's AI assistant reads only published articles, and the GraphQL API's upsertHelpCenterArticle mutation can create or update articles in place.	Once a person approves a fix, Solo can hold it until the feature flag is enabled, then publish it, so the article changes when your product does and the AI agent answers from the corrected text.

Questions

Questions about keeping your help center current

What support and docs leads on Plain ask before connecting Solo.

How do I find which Plain articles a change to my product made wrong?

Knowledge gaps and AI conversation logs show you questions customers have already asked, not changes your code made. Solo reads your code changes and flags the articles that no longer match, before anyone asks. Your team reviews each flag.

Does Plain's AI read draft articles?

No. Ask AI and Ari read published articles only, so a draft stays invisible to them until you publish it. Plain AI keeps answering from the old published text while a fix sits in draft.

Does Solo replace Plain?

No. Your articles stay in Plain, where customers read them and where its AI assistant finds them. Solo suggests changes, and your team approves the ones that are published back to Plain.

Will Solo publish to Plain without a review?

No. Solo flags the articles a change to your product made wrong and drafts a fix, and a person accepts each one before anything is published. You can also add a fix to a draft and publish it later.

What about features in my product that are behind a feature flag?

A feature behind a flag can make an article wrong for some customers and not others. Where the information is available, Solo shows the flag and its rollout status on the review item, and can snooze the item until the flag changes.