AI-ready knowledge is becoming one of the biggest tests of whether customer service teams can scale AI safely.\u00a0Many organizations\u00a0are\u00a0still\u00a0most interested in\u00a0comparing\u00a0models. They ask which large language model is fastest, smartest, or most flexible. Yet for service teams, that may be the wrong starting point.\u00a0<\/p>\n
AI cannot resolve issues confidently if it does not understand the company it is serving. It needs product policies, processes, business rules, customer context, escalation logic, and the authority to act.\u00a0For\u00a0Hannah Deveney, Senior Director, Product Management at Zendesk, that makes knowledge a foundation for AI-led service:\u00a0<\/p>\n
\u201cThe model provides the reasoning, but the knowledge dictates the outcome.\u201d\u00a0<\/p>\n
That distinction matters as customer service moves beyond AI assistants and toward more autonomous agents.\u00a0<\/p>\n
This is where the AI conversation becomes less glamorous but more useful. Service leaders can choose impressive models and launch polished pilots, but the outcome still depends on the knowledge those systems can reach. If that knowledge is fragmented, outdated, or difficult to access, AI may simply reproduce the gaps already inside the operation.\u00a0<\/p>\n
Why AI-Ready Knowledge Comes First\u00a0<\/p>\n
The pressure on service teams is easy to understand.\u00a0Customers want quick answers, and they expect every interaction to\u00a0carry\u00a0context. Zendesk\u2019s CX statistics show that 70% of customers expect anyone they interact with to have the full context of their situation.\u00a0<\/p>\n
That expectation applies whether the customer reaches a human agent, a self-service journey, or an AI agent.\u00a0Yet many service organizations still manage knowledge as a static resource. Policies live in PDFs. Process updates sit in shared drives. Product details sit with veteran agents. Internal exceptions live in Slack or Teams.\u00a0<\/p>\n
That may work in a human-only\u00a0environment, because\u00a0experienced agents can fill in the gaps. It does not work as well when AI agents are expected to resolve issues on their own.\u00a0Deveney compared it to hiring a strong employee and withholding the training:\u00a0<\/p>\n
\u201cYou\u00a0wouldn\u2019t\u00a0hire a brilliant new\u00a0employee,\u00a0and\u00a0then refuse to train them on your products. But\u00a0that\u2019s\u00a0exactly what happens when companies deploy AI without a strong knowledge foundation.\u201d\u00a0<\/p>\n
This is where many AI programs run into early friction. The model may be strong, but the business knowledge around it is not ready.\u00a0That can lead to confident wrong answers, failed actions, and escalations that create more work for human agents.\u00a0<\/p>\n
Fragmented Knowledge Creates Confident Errors\u00a0<\/p>\n
One of the biggest risks is an AI agent delivering a confident but incorrect answer.\u00a0\u00a0<\/p>\n
If a company\u2019s return policies are split across multiple systems, with one version in a PDF, another in an internal wiki, and another inside a legacy tool, an AI agent may find the wrong answer and present it clearly.\u00a0<\/p>\n
That creates a new problem for the human team.\u00a0Instead of simply handling the customer\u2019s original issue, an agent now\u00a0has to\u00a0explain the mistake, rebuild trust, and correct the action.\u00a0Deveney warned that poor knowledge can turn AI from a resolution engine into a source of extra effort:\u00a0<\/p>\n
\u201cIf you have your return policies split across three different systems with outdated PDFs, AI is going to pull the wrong answer.\u00a0Instead of reducing ticket volume,\u00a0you\u2019ve\u00a0increased your handle time and eroded trust.\u201d\u00a0<\/p>\n
The lesson for CX leaders is direct. AI performance cannot be separated from the quality of the knowledge it can access.\u00a0A weak knowledge base does not simply limit self-service. It limits agent\u00a0assistance, automation, and the quality of AI-led resolutions.\u00a0<\/p>\n
Knowledge Has\u00a0To\u00a0Support Action\u00a0<\/p>\n
Modern service knowledge is no longer only about answering questions.\u00a0In an agentic AI environment, knowledge also\u00a0has to\u00a0support action. An AI agent may need to process a refund, update an address, change a booking, check eligibility, or trigger a workflow.\u00a0<\/p>\n
That requires more than an article.\u00a0It requires structured rules, clean permissions, reliable workflows, and system access that lets the AI complete work safely.\u00a0<\/p>\n
Zendesk\u2019s own knowledge positioning reflects this shift. The company describes Zendesk Knowledge as a platform to build, connect, and surface knowledge across agents, AI, and self-service. It also highlights the ability to bring knowledge from multiple sources into a single platform, surface the right information in every interaction, and continuously\u00a0identify\u00a0content gaps.\u00a0<\/p>\n
That matters because human agents and AI agents use knowledge differently.\u00a0A human agent may need a clear explanation of a policy. An AI agent may need the same policy in a structured format, with the relevant business rules and action paths attached.\u00a0Deveney explained the difference:\u00a0<\/p>\n
\u201cFor a human agent, knowledge might be a really well-written paragraph explaining a policy, but for that AI agent, knowledge also includes business rules, API endpoints, and structured data that gives it permission to take action.\u201d\u00a0<\/p>\n
That is a useful distinction for service leaders. AI readiness is not only about whether the right information exists somewhere. It is about whether that information is usable by both people and machines.\u00a0<\/p>\n
Human Agents Are\u00a0The\u00a0Knowledge Litmus Test\u00a0<\/p>\n
Service leaders do not need to start with a large technical audit to find early warning signs.\u00a0The first clues often sit with human agents.\u00a0\u00a0<\/p>\n
If agents regularly bypass the knowledge base and ask questions in Slack, Teams, or informal group chats, the knowledge environment is\u00a0probably not\u00a0trusted. If newer agents cannot find the right answer without tapping a veteran colleague on the shoulder, that is another warning sign.\u00a0Deveney framed those behaviors as a simple test of knowledge health:\u00a0<\/p>\n
\u201cIf your people can\u2019t find the right answer, AI won\u2019t be able to either.\u201d\u00a0<\/p>\n
That line should\u00a0sit\u00a0close to any AI planning process.\u00a0Human workarounds are often treated as cultural habits, but they may point to deeper operational problems. They show where knowledge is missing, stale, hard to navigate, or written in a way that does not reflect real service work.\u00a0<\/p>\n
AI makes those gaps harder to ignore.\u00a0When a human agent cannot find an answer, they may improvise. When an AI agent cannot find the right answer, it may escalate, stall, or act on the\u00a0wrong information.\u00a0None of those outcomes\u00a0helps\u00a0the customer.\u00a0<\/p>\n
From Static Articles\u00a0To\u00a0Dynamic Knowledge\u00a0<\/p>\n
The role of knowledge is also becoming more strategic.\u00a0For years, many organizations treated the knowledge base as a publishing project. Teams created articles, reviewed them occasionally, and hoped agents or customers could find them when needed.\u00a0<\/p>\n
That approach is unlikely to support AI-led\u00a0service at\u00a0scale.\u00a0Deveney argued that companies need to stop thinking of knowledge as static content and start treating it as a live operational asset:\u00a0<\/p>\n
\u201cKnowledge has to become like a dynamic operational asset for them both.\u201d\u00a0<\/p>\n
The \u201cboth\u201d is important.\u00a0Knowledge now\u00a0has to\u00a0serve human agents and AI agents in the same service system.\u00a0<\/p>\n
That means updates cannot sit in one part of the business while another team works from older information. If an AI agent learns from a new resolution pattern, that insight should be available to humans too. If a human agent\u00a0identifies\u00a0a process issue, that feedback should improve what AI can access.\u00a0<\/p>\n
That is also why new roles are beginning to\u00a0emerge.\u00a0<\/p>\n
In\u00a0an\u00a0earlier video interview\u00a0with CX Today, Deveney pointed to the rise of knowledge engineers. These roles move beyond documentation writing and focus on structuring data, processes, and tools so AI agents can act\u00a0safely\u00a0and human agents can work from the same source of truth.\u00a0<\/p>\n
That is a practical evolution. As service teams become systems of human and digital agents, someone\u00a0has to\u00a0design and\u00a0maintain\u00a0the knowledge layer that supports them.\u00a0<\/p>\n
What CX Leaders Should Check First\u00a0<\/p>\n
Before scaling AI, service leaders can ask a few simple questions.\u00a0<\/p>\n
Can frontline agents find the right answer quickly? Are policies current across every channel? Do AI agents and human agents use the same knowledge core? Are process rules structured enough for AI to act on them? Is knowledge updated continuously, or treated as a yearly cleanup project?\u00a0<\/p>\n
If the answers are uncomfortable, that does not mean AI\u00a0rollout\u00a0should stop. It means the\u00a0knowledge\u00a0work\u00a0has to\u00a0move up the priority list.\u00a0The wider AI conversation often focuses on capability. The service conversation needs to focus on readiness too.\u00a0<\/p>\n
The most advanced model in the world cannot compensate for messy business knowledge. It may even expose the problem faster.\u00a0<\/p>\n
For service leaders, that is the real opportunity. Build the knowledge foundation well, and AI can help customers resolve issues faster, support agents with better context, and turn service operations into something more consistent and scalable.\u00a0Ignore it, and AI may simply automate the confusion that already exists.<\/p>\n","protected":false},"excerpt":{"rendered":"AI-ready knowledge is becoming one of the biggest tests of whether customer service teams can scale AI safely.\u00a0Many…\n","protected":false},"author":2,"featured_media":137123,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[179,509,7493,405,67879,45526,11178,28288],"class_list":["post-137122","post","type-post","status-publish","format-standard","has-post-thumbnail","category-agentic-ai","tag-agentic-ai","tag-agentic-ai-in-customer-service","tag-agentic-artificial-intelligence","tag-ai-agents","tag-knowledge-base-software","tag-knowledge-for-agents","tag-knowledge-management","tag-self-service"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/137122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=137122"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/137122\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/137123"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=137122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=137122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=137122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}