Chatwoot vs Zendesk
Chatwoot and Zendesk score alike on the AgentReady. They differ on 3 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.
What each one is
Chatwoot. The modern customer support tool for your business.
Zendesk. AI-powered service platform that delivers faster, higher quality resolutions with self-improving AI agents that learn, adapt, and outperform on every channel and platform.
Where Chatwoot is ahead
Chatwoot passes public docs discoverable, and Zendesk does not. That is discover, whether an agent can find the product at all without being told it exists.
Where Zendesk is ahead
Zendesk passes fast time to first request and copyable quickstart, and Chatwoot does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.
What neither does
Both fail llms-full.txt / full agent docs, mcp discoverable, structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, mcp integration available, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. If your agent needs any of those, you will be building it yourself either way.
Score, pillar by pillar
The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.
Discover is whether an agent can find the product at all without being told it exists. Chatwoot leads 80 to 67. Chatwoot misses llms-full.txt / full agent docs, mcp discoverable; Zendesk misses public docs discoverable, llms-full.txt / full agent docs, mcp discoverable.
Understand. Both sit at 23/100 here. Chatwoot misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Zendesk misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt. Zendesk leads 65 to 55. Chatwoot misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, mcp integration available; Zendesk misses no mandatory sales call, programmatic credential creation, mcp integration available.
Operate. Both sit at 35/100 here. Chatwoot misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Zendesk misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.
Pricing
Chatwoot starts at $0/agent/month and has a free tier. Zendesk does not publish one with no free tier.
| Chatwoot plans | Zendesk plans |
|---|---|
| Hacker $0/agent/month | - |
| Startups $19/agent/month billed annually | - |
| Business $39/agent/month billed annually | - |
Signal by signal
| Signal | Chatwoot | Zendesk |
|---|---|---|
| AgentReady | 48 | 48 |
| Discovery | 80 | 67 |
| Understanding | 23 | 23 |
| Adoption | 55 | 65 |
| Operability | 35 | 35 |
| Public API | Yes | Yes |
| MCP server | No | Unknown |
| OpenAPI spec | Unknown | Unknown |
| CLI | Yes | Yes |
| llms.txt | Yes | Yes |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | No |
Which to pick
Zendesk clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Chatwoot and Zendesk. Alternatives to each: Chatwoot, Zendesk.
An agent can fetch this as data: POST /v1/compare {"slugs": ["chatwoot", "zendesk"]}