Zendesk Open Service Directory Routes AI Assistants to Real Support

Your company's next support request may not come from a person at all — it may come from a personal AI assistant acting on that person's behalf. That is the premise behind the Zendesk Open Service Directory, a new draft specification and public registry that aims to give AI assistants a trusted way to find and connect to a brand's official customer support, announced this week by Zendesk.

According to Zendesk's announcement, customers have begun asking AI assistants to move appointments, request replacements, and follow up on service issues. The assistant typically understands the request, but knowing where to send it is the harder part. As reported by e-commerce.news, assistants have lacked a shared, trusted way to verify that they are reaching a brand's official support — a gap that can produce wrong answers, dead ends, and customers forced to start over.

The Zendesk Open Service Directory is designed to close that gap by functioning as a phone book of verified support destinations for the agentic web.

How the directory works

The mechanism has three stages. First, a brand opts in through its service platform — which, notably, does not have to be Zendesk — and approves a support listing. According to Zendesk, Each listing is checked against the business's own domain and screened for impersonation before it enters the Zendesk Open Service Directory. Second, a personal AI assistant searches participating registries, confirms the match, and routes the request to the brand's approved support destination. Third, the customer connects to the brand's own support experience, which is usually its AI agent, with the customer's permission. If the job turns out to need a person, the thread passes to the support team with the conversation history attached.

The approach complements other trust infrastructure for agents: Opsin's governance platform watches for misbehaving agents, while Apate sends agents undercover to catch scammers. The directory, by contrast, solves the directory problem — making sure the agent shows up at the real front desk in the first place.

Crucially, the directory itself never touches private customer data or performs support tasks. Once the assistant is connected via the Zendesk Open Service Directory, it operates under the brand's own rules on authentication, data access, and escalation. Zendesk says it is building controls to identify both the assistant and the customer behind it.

Seven launch partners are helping shape the Zendesk Open Service Directory: Betterment, ElevenLabs, Flex, TeamSystem, TBAuctions, Telekom Payment, and Wireless Logic. Zendesk lists ChatGPT, Claude, and Gemini among compatible assistants. The specification extends the Agentic Resource Discovery (ARD) protocol, whose working group includes Microsoft, Google, and Hugging Face — a signal that Zendesk wants this to be shared infrastructure rather than a walled garden.

A crowded month for agent standards

The Zendesk Open Service Directory arrives in the middle of a rush to define how agents find, verify, and transact with services. Earlier this month, Meta and Sierra unveiled the Personal Agent Protocol with backing from Genesys, Shopify, Stripe, and Walmart. Decagon open-sourced PACT, which uses OAuth 2.0 to let a business check who a personal agent represents and what it may do. And identity infrastructure company Proof launched x401, an open protocol for requesting proof of who an agent acts for and what the person approved, designed to work alongside the x402 payment protocol.

Zendesk says it will adopt both the Personal Agent Protocol and PACT, casting the directory as the step that comes first: it finds the right door before anyone knocks. According to a Futurum Group analysis by Keith Kirkpatrick, the design choice to open the registry to brands on any service platform was the right one — a directory confined to Zendesk's own clients would be of little use to assistant builders.

Kirkpatrick's analysis also offers a pointed caveat: compatibility means an assistant could use the Zendesk Open Service Directory, not that OpenAI, Anthropic, or Google will query it by default. The directory's success depends on assistant providers actually adopting it, and rival CX platforms such as Salesforce and ServiceNow have their own reasons to go their own way. Reported by CXM World, the analyst's assessment frames the launch as genuinely useful infrastructure whose network effects remain an open question.

What agent-led service means for customer teams

The timing reflects a shift in who initiates service interactions. According to Zendesk's framing, 2025 research from Gartner found that 51% of customers said they would be willing to use a GenAI assistant for service interactions on their behalf. Those requests will land somewhere — and a front desk beats a fake one.

For customer service leaders, the Zendesk Open Service Directory raises a set of practical questions. Brands arguably need to audit where their support can currently be found online, decide how they will verify an assistant and the person it acts for, and settle which tasks a machine may complete alone. Measurement is another open problem: vendor contracts increasingly bill by resolution, yet the industry has never agreed on what a resolution is — and inserting a customer's assistant into the middle makes credit and invoicing murkier still.

Open items remain on Zendesk's side as well. The company has not published pricing or a general-availability date for the Zendesk Open Service Directory, and says it will share more at its AI Summit on November 12. In the meantime, the specification is in draft and open to participation: Zendesk has invited CX platforms, AI agent builders, and brands to help build the directory as a shared foundation for verified support.

Whether the directory becomes the default first step of agent-led customer service will depend on adoption — but the premise is difficult to argue with. As agents take on more of the errands, the web needs a way for them to find the real front desk — and the Zendesk Open Service Directory wants to be that map.

Related reading: Zendesk's announcement of the Open Service Directory, CXM World's coverage of the launch, and the Futurum Group analysis of whether assistants will actually use it.