Grow and improve your knowledge base from what customers actually asked. Plain now records every question our Customer Agent (Ari) couldn't answer, groups them by topic, and turns each one into a task that our Internal Agent (Sidekick) can write the article for. 

Our Customer Agent (Ari) records what it couldn't answer.

When the agent searches your knowledge and can’t find a match, it hands the thread to your team and records the question. We keep only the general product questions your documentation should answer, filtering out account-specific and out-of-scope ones, then groups similar questions into a single gap per topic.

Every gap is a task, sorted by how often it comes up.

Find them at Ari → Knowledge → Knowledge gaps, with the thread count and how recently each was asked. The most common questions sit at the top, so the first article you write is the one that pays off most. Each gap is a normal task, so Todo, Done, and Cancelled work the way they do everywhere else in Plain.

Our Internal Agent (Sidekick) writes the first draft.

Run the /fill-knowledge-gap skill, the agent researches the gap, links threads across your knowledge sources, drafts an article with citations, and saves it as a draft for you to review and publish. Closing it out closes the task. The session stays open, so you can add context, pull in another tool, or send the customer their answer while you're there.

Find the gaps proactively.

Gaps are detected in Shadow Mode too. You can run our Customer Agent against real threads without it sending anything, collect the questions your knowledge doesn't cover yet, fill them, and turn the agent on with the documentation already in place.

Knowledge gaps, tasks, and task webhooks are all available through the API if you want them in your own tooling.

Learn more →