Start free
Help center articles flowing into an AI support agent that answers customer questions

How to Turn Your Existing Help Center Into an AI Support Agent

Published on byAntoniAntoni

Most teams that think they need to "write content for AI" already have it. It sits in a help center: dozens or hundreds of articles, each answering a real question somebody once asked. The knowledge is not the problem. The problem is that a help center asks the customer to do the finding, the reading and the interpreting, and many give up halfway and email you anyway. This guide covers turning that library into an AI support agent: importing it, connecting the rest of your docs, auditing it against real questions, rewriting what confuses an agent, keeping it in sync, and measuring the result.

Key Takeaways


Why a help center alone deflects less than you think

A help center is a library. It works for people who know what they are looking for, what it is called, and have time to read. Customers with a problem are rarely in that state. Three things go wrong:

FailureWhat the customer experiencesWhat an agent does instead
SearchTypes "money back", gets nothing, because the article is titled "Refund policy"Understands "money back" means a refund and answers from the policy
NavigationCategories mirror your org chart (Billing, Account), not their situation ("I was charged twice")Needs no categories; it reasons over all of the content
LengthThe answer is in paragraph four of a 1,200-word article, after three cases that do not applyPulls out the one case that applies and states it in two sentences

The article was correct. It still produced a ticket. This is where the Bot usually gets bolted on: a scripted widget that matches a keyword and pastes a link to the article the customer already failed to read. That is a shortcut to the dead end. An agent reads the article for them, applies it to their case, and answers.

What a good import looks like

A bad import quietly caps everything that follows. A good one:

FutureBase reads Zendesk Guide, Intercom Articles, Help Scout Docs, Mintlify, GitBook and Freshdesk help centers this way, plus help centers on your own address such as help.yoursite.com. Details are in the help center import docs.

Step 1: Import the public help center

This is the shortest step and where most of the value comes from.

  1. Open your agent's Knowledge page, go to the Sources tab, and paste your help center's address in the Add box, for example yourcompany.zendesk.com/hc/en-us.
  2. When it is recognized, the first option is Import help center. Choose it. The agent can answer from each article as soon as it is read; large help centers take a few minutes.
  3. Open the new Help center source and review the list. Each article shows its status and where it syncs from; open a few you know well and check that what the agent reads is what you expect.

If your help center lives under your main domain, like yoursite.com/help, those pages belong to your website source: use Add everything under /help/* instead. And during sign-up, the review lists a help center your homepage links to as its own group, so you can tick it there. Each article counts as one page toward your plan's page limit.

Step 2: Connect the knowledge that never made it into the help center

Every support team has answers that live outside the help center: pricing exceptions in a spreadsheet, escalation rules in a Notion page, a policy somebody once wrote in an email. The agent cannot answer from what it cannot read. Resist connecting everything, though; internal docs are full of half-decisions and stale drafts.

Where it livesHow to connect it
Notion (playbooks, policies, specs)Connect Notion on the Sources tab, pick pages and databases. Syncs every 24 hours. Share a "Support" teamspace, not the whole workspace
Google Drive (price sheets, policies in Docs)Google Drive tile, pick folders or files. Docs, Sheets, Slides, PDF and Word, synced daily (paid plans)
Your website (pricing, features, legal)Import the whole website, then set Only import pages under and Never import rules
Files, snippets, FAQsDrop PDF, Word, Markdown, CSV, JSON or HTML files; paste text; type a question ending in ? to create an FAQ
Emails and signed-in pagesForward an email to the agent's address; add a page behind a login with the browser extension

A useful rule: if a human agent would open it to answer a ticket, connect it. If not, do not. Notion images are referenced but not stored and Drive skips images, so the screenshot caveat applies here too.

Step 3: Audit the import with real past questions

An import tells you what the agent can read, not whether it can answer. The only honest test is the questions customers already asked.

Build the test sheet from tickets, not from the help center

Export the last 60 to 90 days of conversations. Take the first message of each, group them into topics, and sort by frequency; the top 50 usually cover most of your volume. Keep the customer's phrasing, typos included: "charged twice??" is a better test than "How do I dispute a duplicate charge?".

Ask each question and classify the result

Use Ask your agent on the Knowledge page. For each question you see the answer and the knowledge items it used, which is the part that matters:

ResultFix
Correct, from the right articleNothing
Correct, from the wrong place (an old campaign page outranked a weak article)Strengthen the article, disable the noisy page
Vague or generic (the article hedges or scatters the answer)Rewrite (Step 4)
Wrong (two sources disagree, or the article is stale)Resolve the contradiction, update the article
No answer (a gap the help center never covered)Write an article or an FAQ

Let the Overview catch what you missed

The Knowledge page's Overview tab does part of this for you. Conflicting answers flags two items that state different facts, such as an article saying refunds take 30 days and a pricing page saying 14; for each pair you Trust this one, Edit the wording, or Dismiss when both are right for different cases. After launch, once the agent has had 50 conversations in 30 days, Topic coverage groups live questions into topics marked Covered, Needs fix or Gap, so the audit keeps running on real traffic.

Step 4: Rewrite what confuses an agent

Most articles need no changes; the ones that do are almost always the long ones. Edit them in the help center, not in the agent, and the sync carries the edits over. Five edits cover nearly every case; for more, see our guide to training AI on your documentation.

One topic per article. A "Billing" article that covers changing plans, updating a card, downloading invoices and refunds answers four questions badly: the agent has to find the right quarter of it every time. Split it into four short articles with specific titles.

Declarative sentences, answer first. Before: "Depending on your plan and region, you may be eligible for a refund within a certain period. Please reach out to our team for details." After: "Refunds are available within 30 days of purchase on every plan. Email [email protected] with your order number; refunds reach your original payment method within 5 to 7 business days." The first makes the agent guess; the second lets it answer.

Say the edge cases out loud. Human-written articles leave edge cases implicit because the author knows them. If annual plans are refunded pro rata, if EU customers get 14 days by law, if trials cannot be refunded, write each as its own sentence. Otherwise the agent gives the general rule to someone it does not fit, and that customer writes in.

Put screenshot-only information into text. If the button name, settings path or error message only exists in the image, write it in the sentence too.

Use FAQs for answers that must be exact. For prices, refund windows and legal wording, add an FAQ in the agent. FAQs take precedence over general content when a question closely matches, so they pin an exact answer. One intent per FAQ.

Step 5: Keep it in sync

A help center that was accurate at import and stale three months later is worse than one never imported, because the agent answers confidently from it. Syncing has to happen without anyone remembering to do it.

Help center and website sources refresh weekly on Hobby and daily on Standard and Pro (off on Free, where Check now does the job, up to six times an hour). Notion syncs every 24 hours and Google Drive daily, each re-reading only what changed, with Sync now for right away. Files and forwarded emails have no refresh: upload them again when they change.

On each check, a help center source re-reads changed articles, adds new ones within your page limit, and removes articles that are gone, so the agent stops answering from a retired article immediately (Undo brings one back within 7 days). To review new articles before the agent learns them, turn off Add new pages automatically in the source's rules.

Two habits make this stick. Add Check now to your release checklist, so an updated article is picked up the day a feature ships. And review Not used lately each quarter: after 90 days of answers, the Overview lists items no answer used, usually old campaign pages and last year's price list. Disable them.

Step 6: Measure resolution before and after

You cannot see how many customers your help center resolved, because those never wrote in. What you can measure is what it failed to resolve: the tickets. So the baseline is ticket volume by topic.

Before the agent goes live, record conversations per week in total and per topic for the audit window, plus any quality signal you have: CSAT, re-opens, replies that say "that didn't work".

After the agent is live, track the same things plus the autonomous resolution rate: conversations resolved without a human handoff, divided by all conversations. Count a conversation as resolved only when the issue was handled, not when the customer went quiet; the distinction is covered in our guide to deflection rate and how to calculate it.

Compare per topic, not globally. A global number hides that "reset my password" went to near-full resolution while "I was charged twice" barely moved because the article hedges. Per-topic numbers tell you which article to fix next. In FutureBase, the Topic coverage ring on the Overview shows the share of questions answered from your knowledge and each topic's state, so the measurement and the fix list are the same screen. Give it a full month on both sides, and keep quality signals next to the resolution number so a rising line means resolved customers, not abandoned ones.

Frequently asked questions

Do I have to rewrite my whole help center before importing it?

No. Import it as it is, run your top real questions through the agent, and rewrite only the articles that produced wrong, vague or missing answers. In most help centers that is a small minority of articles, usually the long ones that cover several topics at once.

What if my help center is behind a login?

A help center import only reads articles anyone can open, so articles limited to signed-in users are skipped. For those, export the articles and upload them as files, add them one at a time from your browser with the extension, or keep the signed-in content in a connected app like Notion or Google Drive.

Will the agent pick up changes when my team edits an article?

Yes, on the next check. A help center source refreshes weekly on Hobby and daily on Standard and Pro, reads only the articles that changed, adds new ones and drops the ones you retired. Choose Check now on the source to pick up an edit right away.

Should I delete the help center once the agent is live?

Keep it. The help center stays the place your team writes and maintains answers, and the agent reads from it. Customers who prefer to browse still can, search engines still index it, and every edit your team makes there flows into the agent on the next sync.


Your help center already did the hard part. Start free with FutureBase, paste your help center's address, and let an agent answer from every article, kept in sync as your team edits them. See how teams use it as a knowledge base agent and a self-service support portal.

Retire the Bot. Give your customers an agent.

Deploy in five minutes. No credit card required.

Trained on your website in minutes
Knowledge base & file upload
Help desk with full-context hand-off
MCP server access
GDPR compliant