# Zendesk AI: Connect Help Center Articles as Knowledge *How-to — 2026-10-17 — by Mahmoud Zalt* How to connect your help center and outside content as knowledge sources so a Zendesk AI agent can generate answers, plus the limits nobody mentions. **Short answer.** **A Zendesk AI agent cannot generate an answer until you connect at least one knowledge source to it.** You do this from the AI agents workspace: open the agent, go to its content area, find Knowledge sources, and edit the sources. You can connect Zendesk help centers, content pulled in from outside Zendesk, or a combination of both. **About this guide.** This guide is based on publicly available information and Zendesk's own documentation, checked on 17 August 2026. Sistava is not affiliated with Zendesk. Interfaces and pricing change often, so confirm the current steps in their documentation before you rely on them. Teams usually arrive at this page after the same disappointment. The AI agent is live, a customer asks a question the help center clearly answers, and the agent says nothing useful. Nine times out of ten the reason is not the model. It is that no knowledge source is connected, or the wrong one is. Zendesk states this plainly in their documentation: connecting one or more knowledge sources is required for an AI agent to create an AI generated answer. There is no default. An agent with no source is an agent that can greet people and hand them to a human, and nothing more. ## What counts as a knowledge source in Zendesk? Zendesk's documentation splits sources into two families. The first is Zendesk help centers, either the one attached to your account or one attached to a specific brand. The second is external knowledge sources, meaning content that lives somewhere else and is brought into your Zendesk account first. That second family matters more than it sounds. External content is not connected directly to the agent. It has to be imported into Zendesk before the agent can use it, which adds a step people do not expect. - **Zendesk help centers: **the help center for your account, or for a particular brand if you run several. - **Web crawlers: **external website content indexed into Zendesk, set up before you can attach it to an agent. - **Knowledge connectors: **outside knowledge systems brought into Zendesk, with Confluence spaces named in their documentation. - **External records: **content ingested through the Federated Search API, for teams with content in a system that has no ready made connector. Their documentation on external content puts a ceiling on this: up to 50 external sources per account. That is generous for most teams and worth knowing about if you are planning to crawl a large documentation estate site by site. ## How do you connect your help center to an AI agent? You do it from the AI agents workspace rather than from a global setting. Open the agent you want to change, go to its content area, find Knowledge sources, and use the option to edit sources. The path Zendesk documents runs through the agent itself, which means each agent carries its own set of sources. 1. **Confirm the help center is live** — The brand's help center has to be active. If it is not, Zendesk raises an error earlier in the process, when you attach the brand to the agent. 2. **Open the agent in the AI agents workspace** — Select the specific AI agent you want to give knowledge to, rather than looking for an account wide setting. 3. **Go to Knowledge sources** — Open the agent's content area and find the Knowledge sources section. 4. **Edit sources and select your help center** — Use the edit sources control and pick the help center you want the agent to draw on. Add more than one if the agent covers more than one brand. 5. **Test with a question you know is documented** — Pick an article you can see in the help center and ask the question it answers. If the agent still cannot answer, the problem is the connection, not the writing. 6. **Publish before you celebrate** — Changes to an agent do not reach customers until the agent is published, so a working test is not the same as a working widget. **The other way to get this done.** Importing content into one system so a second system can read it is exactly the plumbing we removed at Sistava. Rather than wiring sources to an agent, you hire an AI Employee, point it at what it should know, and tell it in plain English what you want handled. Its tools are connected already and it asks you when it is unsure. There is no import step and nothing to keep in sync. ## How do you add content that lives outside Zendesk? In two stages, and the order is fixed. First you set up the import in Zendesk, meaning a web crawler, a Confluence connection or a Federated Search API call. Only then can you attach that source to an AI agent. Zendesk's documentation is clear that the import has to exist before the connection step is available. The timing detail is the one that catches people out. Zendesk's documentation says that when an AI agent searches a connected external knowledge source, it searches the information as of the last sync, which usually happens every 24 hours. So if you publish a fix on your marketing site this morning, the agent may still be answering from yesterday's copy this afternoon. That is worth planning around during an incident. If something changes that customers will ask about immediately, a help center article is the faster route, because your Zendesk help center is native content rather than imported content waiting on a sync. ## What happens to restricted or internal articles? Zendesk's documentation says the agent respects your help center permissions, and it splits behaviour by whether the customer is signed in. For authenticated customers, the agent can use relevant restricted articles. For unauthenticated customers, it can only use public ones. There is also a related option in the agent's brand and channels settings, described as always showing the title and preview for restricted articles. Read that one carefully before you switch it on, because titles alone can reveal more than you intend. An article titled with an unreleased product name is a leak even if nobody can open it. The practical habit here is to audit what is public before you connect anything. Most help centers accumulate articles written for a previous version of the product, and an AI agent will happily surface a two year old workaround because nothing about it says expired. ## How many knowledge sources should you connect? Fewer than you are tempted to. Zendesk allows multiple sources on a single agent, including several help centers, several external sources, or a mix, but their own documentation adds a caution: too many sources can in some cases reduce accuracy and increase latency. There is no hard number given. That trade off is real for any system that answers from documents, ours included. At Sistava we found the same thing: a small, current, well written set beats a large one every time, because contradiction is what produces a confident wrong answer. If two sources disagree, the reader gets a coin flip, and neither result is one you would have approved. So start with one help center. Add a second source only after you have watched real conversations and found a category of question the first source genuinely cannot answer. That gives you a reason for each addition and a way to tell whether it helped. **The things the setup screen does not tell you.** Imported external content answers from its last sync, which their documentation puts at roughly every 24 hours, so it is not the right home for anything urgent. Restricted articles behave differently for signed in and signed out customers. And a stale help center is the single most common cause of a confidently wrong answer, because nothing in an old article announces that it is out of date. ## Does the language of your articles matter? Less than you would expect. Zendesk's FAQ on generative replies states that they are fully multilingual, can converse in over 100 languages, and can read knowledge sources written in any language. That means a single English help center can serve customers writing in other languages. The same FAQ notes that generative replies work on messaging and email channels, and that the number of tickets you have does not influence them. That second point is useful for smaller teams, since there is no volume threshold to cross before the feature does anything. ## FAQ ### Why is my Zendesk AI agent not using my help center articles? The most likely reason is that no knowledge source is connected to that particular agent. Sources are set on the agent itself, in its content area under Knowledge sources, not as an account wide default. Check the connection first, then check that the article is public and that the agent has been published since you made the change. ### Can a Zendesk AI agent use content from outside Zendesk? Yes, but the content has to be brought into Zendesk first. Their documentation names web crawlers for websites, knowledge connectors including Confluence spaces, and external records ingested through the Federated Search API. You set the import up before you can attach it to an agent, and the account limit is 50 external sources. ### How often does Zendesk sync external knowledge sources? Zendesk's documentation says that when an AI agent searches a connected external knowledge source, it searches the information available as of the last sync, which usually happens every 24 hours. Plan around that for anything time sensitive, and use a native help center article when customers need the current answer today. ### Will a Zendesk AI agent show restricted help center articles to customers? It depends on whether the customer is signed in. Zendesk's documentation says that for authenticated customers the agent can use relevant restricted articles, and for unauthenticated customers it can only use public ones. There is also a separate setting about always showing titles and previews for restricted articles, which is worth reading carefully. ### How many knowledge sources can one Zendesk AI agent have? Their documentation does not give a hard number for sources on a single agent, and says you can connect multiple help centers, multiple external sources, or a combination. It does warn that too many sources can in some cases reduce accuracy and increase latency. The account level ceiling for external sources is 50. ### Do help center articles need rewriting for a Zendesk AI agent? Not rewriting, but pruning helps. The agent reads what is there, so contradictory or outdated articles produce contradictory or outdated answers. Retiring articles that describe a previous version of your product does more for answer quality than reformatting the ones that are still correct. ## Sources - [Zendesk help, ](https://support.zendesk.com/hc/en-us/articles/8357749301658-Connecting-knowledge-sources-to-power-generative-replies-in-AI-agents)Connecting knowledge sources to power generative replies in AI agents - [Zendesk help, ](https://support.zendesk.com/hc/en-us/articles/8357756420506-Generative-replies-in-AI-agents-FAQs)Generative replies in AI agents FAQs - [Zendesk help, ](https://support.zendesk.com/hc/en-us/articles/9822956298010-About-connecting-external-content-to-Zendesk-for-use-across-knowledge-experiences)About connecting external content to Zendesk for use across knowledge experiences - [Zendesk help, ](https://support.zendesk.com/hc/en-us/articles/9543022336794-Configuring-an-AI-agent-s-brand-and-channels)Configuring an AI agent's brand and channels - [Zendesk help, ](https://support.zendesk.com/hc/en-us/articles/4408824263578-Creating-an-AI-agent-to-automatically-resolve-customer-issues)Creating an AI agent to automatically resolve customer issues **Tags:** zendesk, generative-replies, knowledge-base, customer-support-automation, help-center