Zendesk AI vs. botBrains
Attachments, setup, integrations, and pricing: what Zendesk AI can do according to its own documentation, and where botBrains goes further. Every claim sourced, as of September 2026.
Liam van der Viven
Co-Founder & CEO at botBrains
Zendesk AI and botBrains both automate customer service directly inside Zendesk. The difference lies in what the AI is allowed to read, where it can act, how quickly it becomes productive, and what ends up on your invoice at the end of the month. This comparison focuses on exactly those four points.
A word on method: every claim about Zendesk AI comes from publicly accessible Zendesk documentation or from dated, linked user reports. The full list of sources sits at the end of this article. All information is current as of September 19, 2026. Zendesk can change prices and features at any time.
The short version
- Attachments: Zendesk itself documents that AI agents process text only. Attached files and images are not analyzed. botBrains reads the complete ticket history including attachments, so screenshots and PDFs too.
- Setup: Zendesk's own getting-started guide spans six steps and begins with optimizing your help center. For complex automations, Zendesk recommends its paid AI Expert offering. With botBrains, a dedicated rollout manager guides the implementation, and many system integrations are built in a 30-minute call.
- Integrations: Zendesk routes integrations through a narrow no-code envelope with documented limits. botBrains defines actions as code and thereby reaches databases, internal tools, and unusual ERP systems as well.
- Pricing: Zendesk bills AI agents usage-based per automatically resolved request, without a published list price. botBrains starts at €1,700 per month including 3,000 answers, predictable instead of metered.
Comparison at a glance
| Zendesk AI (as of 09/2026) | botBrains | |
|---|---|---|
| Attachments in customer emails (images, PDFs) | Not analyzed; per Zendesk's own docs the AI processes text only | Reads ticket history including attachments: images, documents, voice messages |
| Acting in third-party systems | Custom actions: HTTPS with JSON only, 10-second timeout, 2 MB response limit, max 100 actions per account | Unitools: code-based read and write actions for APIs, databases, internal tools |
| Custom logic | Only JavaScript transformations without network access; anything more requires self-hosted middleware or your own MCP server | Actions contain your business logic directly as code |
| Processes | Generative procedures, one per email reply | Procedures in natural language, followed deterministically |
| Channels | One AI agent per channel, multiple agents maintained in parallel | One agent across email, chat, and voice |
| Implementation | Six-step guide, help center first; partners quote around six weeks for the first use case | Dedicated rollout manager, training on your real tickets, gradual go-live |
| Pricing model | Seats plus Copilot per agent plus a meter per "verified resolution", classified by an unpublished Zendesk model | Flat from €1,700/month including 3,000 answers (roughly 2,000 handled tickets) |
| Hosting and data protection | US vendor, data residency configurable | GDPR-compliant, EU-hosted, made in Germany |
Attachments: what the AI cannot read, it cannot resolve
Customers send screenshots of error messages, photos of damaged goods, invoices, and forms. Zendesk's own knowledge base states: "AI agents process only text in conversations and tickets. AI doesn't scan attached files and media in conversations." Attachments only become available once the ticket is escalated to a human (source 1). Intelligent triage, the automatic ticket classification, likewise considers only the subject and the first text comment according to the documentation (source 3). In Zendesk's community, a customer describes the consequence: the AI agent "sees that the file is attached but cannot read it". The corresponding feature request has been in the backlog since October 2025 and was still open in April 2026 (source 2).
In practice this means: exactly the tickets that carry the most context fall back to your team with Zendesk AI. botBrains reads the full ticket history including attachments and grounds its answers in your documents and past tickets. Image understanding, document understanding, and voice understanding have long been part of the product: your customers send PDFs, Office documents, or photos, and the AI understands the content and resolves the case with it.
Example: A furniture retailer's customer sends a photo of a damaged tabletop plus the invoice as a PDF. Zendesk AI can read neither the photo nor the PDF and escalates to the team. botBrains recognizes the damage and the order number, checks the order in the shop system, and triggers the replacement shipment.
Setup: a do-it-yourself project or a guided rollout
Zendesk advertises getting started "in minutes". Its own getting-started guide, however, shows six sequential steps, and the first one is: optimize your help center content. Teams without a well-maintained help center are told to build one first (source 4). Useful automation such as order status, returns, or cancellations only appears in step four via procedures, dialogues, and API integrations. German Zendesk partner Leafworks quotes around six weeks as a realistic timeframe for the first clearly defined use case (source 12). For complex automations, Zendesk explicitly recommends its paid "AI Expert offering" (source 6).
On top of that, 2026 brings a forced rebuild: legacy bots were frozen on August 31, 2026 and will stop working after December 10, 2026. The migration requires conceptually rebuilding your flows, and each new AI agent serves only one channel. If you automate chat and email, you maintain multiple agents in parallel (sources 5, 6). Zendesk itself warns migrating customers: "Customers may observe changes in automated resolutions and associated costs after upgrading."
With botBrains, implementation is a guided process instead of a do-it-yourself project: kickoff and system integration, training on your real tickets, then a gradual go-live from draft mode to autonomous resolution, with a dedicated rollout manager. Extensions afterwards are conversations, not projects: new actions are often built together in a 30-minute call, and the botBrains Engineer tests changes in simulations against realistic scenarios before they go live.
Integrations: form fields with limits, or code that understands your systems
Zendesk AI can connect to external systems, but only within a narrowly documented envelope. Custom actions accept HTTPS endpoints with JSON only, abort after 10 seconds, process at most 2 MB of response data, and are capped at 100 actions per account. Files and attachments are not supported in actions (sources 7, 8). Custom code exists only as a transformation step without network access (source 9). If you want to connect a database, an internal tool without an API, or a slow ERP endpoint, you have to build and operate your own middleware or an OAuth-protected MCP server (source 8). When the community asked for API access to generative search, Zendesk officially answered in August 2026: "we've decided not to prioritize this because it doesn't align with our platform strategy" (source 13).
botBrains takes the opposite path. Unitools define every action as a small piece of code that carries the business logic of your workflow directly. That way the AI speaks not only to HTTP APIs but also to SQL databases, Redis, Mongo, GraphQL, and proprietary in-house software, reading and writing: finding orders in the ERP, changing addresses, triggering refunds, initiating SMS verification. How much direct system access moves the automation rate is something Ballsportdirekt shows with 90 percent of requests automated.
Scenario: Your order status lives in a self-hosted ERP that only exposes an internal SQL database. With Zendesk, you need to build, host, and maintain your own middleware with an HTTPS API. With botBrains, it is a Unitool with a few lines of code that queries the database directly.
Pricing: a meter without a list price, or a predictable flat rate
Zendesk bills AI agents usage-based per automatically resolved request, a so-called "verified resolution". Zendesk does not publish an official list price per resolution. Zendesk Premier Partner Premium Plus quotes €1.50 per resolution as the standard rate, and a Zendesk product manager publicly pinned the pay-as-you-go price only as "definitely below $2" (sources 10, 11). Since May 2026, whether an interaction counts as a billable verified resolution is decided by a Zendesk-owned AI model whose criteria are not published (source 14). The included allowances are small: depending on the plan, 2 to 10 US dollars per agent per month, capped at 5,000 US dollars per year, with no rollover. At the limit, you either keep paying overage or the AI pauses (source 15).
What this means in practice is best shown with a sample calculation for the AI layer. It is our own arithmetic with disclosed assumptions: 10 support agents, around 2,000 automatically resolved requests per month, market rate of €1.50 per resolution. The Zendesk Suite seats are identical in both scenarios because botBrains works inside your existing Zendesk.
| Item | Zendesk AI | botBrains |
|---|---|---|
| Copilot add-on (10 × €50, source 16) | €500 | included |
| Automated resolutions (2,000 × ~€1.50, minus allowance) | ≈ €2,950 | included |
| AI layer per month | ≈ €3,450 | from €1,700 including 3,000 answers (≈ 2,000 handled tickets) |
| AI layer per year | ≈ €41,400 | from €20,400 |
The more important difference is the mechanics: with Zendesk, the bill grows with every success of your automation, and the classification is not auditable. With botBrains, you know the price upfront and we calculate your concrete volume together in the first call.
What Zendesk customers report
Individual, dated voices from public threads, each linked in the original:
"A majority of the chats we're being charged for are super simple questions that the AI gives a quick reply and a link to a relevant KP article ... it'd be cheaper to handle these with humans than pay $1.5 per."
r/Zendesk, August 13, 2026 (source 17)
"The more successful the automation is and the more enquiries it resolves, the higher the bill becomes."
r/Zendesk, August 17, 2026 (source 17)
The AI agent "sees that the file is attached but cannot read it".
Zendesk community, feature request, open since 2025 (source 2)
Where Zendesk AI is enough
In fairness: if your support almost exclusively answers recurring knowledge questions, your help center is excellently maintained, and you need no actions in third-party systems, Zendesk AI can be sufficient. The comparison tips where tickets contain attachments, where processes need system access, or where the automation volume grows large enough that the meter eats the economics.
You keep Zendesk
botBrains does not replace your helpdesk, it replaces the AI layer inside it. The agent for Zendesk answers tickets, fills fields, sets statuses, and escalates to your team, directly in your existing Zendesk. Workflows, reports, and macros stay untouched.
"We built this comparison the way we would buy ourselves: every claim about Zendesk comes from Zendesk's own documentation or from dated, linked user reports. Where Zendesk AI is enough, we say so honestly", says Liam van der Viven, co-founder and CTO of botBrains. "The difference shows most clearly on tickets with attachments and on processes that need real actions in your systems. That is exactly what we prefer to demonstrate live on your own tickets."
Frequently asked questions
Can botBrains really process attachments?
Yes. The agent reads the complete ticket history including attachments: images, PDFs, Office documents, and voice messages. That way the AI understands a screenshot of an error message or an invoice PDF right inside the ticket.
Do I have to leave Zendesk?
No. botBrains works inside your existing Zendesk: it answers tickets, fills fields, sets statuses, and escalates to your team. Your workflows and reports stay exactly as they are.
What does botBrains cost?
The ticket agent for Zendesk starts at €1,700 per month including 3,000 answers, which corresponds to roughly 2,000 handled tickets. In the first call, we calculate together what that means for your ticket volume.
How does Zendesk count a "verified resolution"?
According to Zendesk's documentation, an LLM classifies every interaction. Only resolutions classified as "verified" consume the allowance or get billed. The model's criteria are not published, and the classification is not auditable by customers (source 14).
How quickly is botBrains productive?
Kickoff, system integration, training on your real tickets, gradual go-live. A dedicated rollout manager guides you, and many system integrations are built together in a 30-minute call.
See the difference on your own tickets
30 minutes with a founder: we show you the agent on examples from your support, including tickets with attachments if you like, and calculate your automation potential. Free and without obligation. Book a demo
Sources
As of September 19, 2026. All Zendesk information from publicly accessible sources; Zendesk can change prices and features.
- Zendesk Help: Can AI agents scan and interpret attachments in conversations?
- Zendesk Community: Advanced AI Agent understanding of attached files and Implement AI Agent scanning of attachments, including OCR of images
- Zendesk Help: Automatically classifying tickets with intelligent triage
- Zendesk Help: Getting started with AI agents
- Zendesk Help: Migrating to the new AI agents experience
- Zendesk Help: Announcing the removal of AI agents Essential and legacy functionality (June 23, 2026)
- Zendesk Help: Creating custom actions for auto assist, AI agents, and action flows
- Zendesk Help: Understanding the action builder and action flows and Connecting to MCP servers
- internalnote.com: Building more powerful Action Flows (August 14, 2026)
- Premium Plus (Zendesk Premier Partner): Understanding Zendesk's new automated resolution pricing model
- Zendesk Community: Automated resolutions launch thread, page 9
- Leafworks (Zendesk partner): AI Agents Advanced
- Zendesk Community: Request for API Access to Generative Search Feature (official reply of August 7, 2026)
- Zendesk Help: About automated resolution tiers (May 18, 2026)
- Zendesk Help: Managing resolution allowances
- Zendesk: Pricing page (retrieved September 19, 2026)
- r/Zendesk: Looking for a ZD compatible AI chat bot (thread of August 13, 2026 with a comment of August 17, 2026)
