VantegrateNative API integrationIntegrate Zoho Desk with AI agentsthat handle your tickets on WhatsApp
Vantegrate's AI agents connect to your account through the official Zoho Desk REST API: they answer customers on WhatsApp, open and update tickets, report the status of every case and hand off to your team with a summary. Your tickets and conversations stay in Zoho Desk.
How the data flows
What does it mean to integrate Zoho Desk with Vantegrate's AI agents?
Integrating Zoho Desk with Vantegrate's AI agents means that an agent answers your customers on WhatsApp and works on your real help desk: it opens and updates tickets, reports the status of each case and, when a person is needed, hands off with the full context. It connects through the official Zoho Desk REST API with OAuth 2.0 and learns about changes through webhooks.
If your WhatsApp number is already connected to Zoho Desk, the agent works inside that channel; if it isn't, the agent answers from its own number and logs every conversation as a ticket. Your tickets, contacts and conversations stay in your Zoho Desk account: the agent reads and updates them, it doesn't take them anywhere.
What do you want to connect to your Zoho Desk?
Pick what you need and we'll write the message for you.
1 · Pick what to solve
2 · What our team receives
Vantegrate
online
What data moves between Vantegrate and your Zoho Desk
The agent works on your Zoho Desk records in real time (through webhooks, on the editions that include them): it reads tickets, contacts and accounts to answer with context, and logs every conversation where it belongs.
Tickets, contacts and accounts
The agent creates and updates tickets with their subject, priority, department and custom fields, and reads the contact, the account and the history to answer with context.
WhatsApp conversations
If the number lives in Zoho Desk, the agent picks up the conversation through the API, replies and, when it hands off, assigns it to a person on your team with a summary in the ticket.
Real-time events
Zoho Desk webhooks flag a new ticket, a status change or an incoming message, and the agent acts without anyone entering it by hand.
How the integration works, step by step
Vantegrate sets up the connection and rolls it out in phases; your team authorizes the permissions and validates.
App with OAuth 2.0
We register the app in the Zoho API console and request only the scopes your use case needs. The token is bound to your Zoho Desk organization and the base URL comes from your data center.
Integration user and profile
The agent works as a Zoho Desk user whose profile sets which departments it sees and what it can do; the permission to create webhooks also depends on the profile.
Channel and handoff rules
We decide where the WhatsApp number lives, which conversations the agent takes, when it hands off and to whom, and how it works alongside your Zia bots and assignment rules.
Events and validation
We subscribe to the webhooks your use case needs, test with real cases in a test department, validate with your support team and roll out in phases.
Two ways to add the agent to WhatsApp in your Zoho Desk
Zoho Desk brings WhatsApp into its instant messaging module: your agents see the conversations inside the help desk and every chat creates or updates a ticket based on your account settings (Zoho). Zoho acts as a WhatsApp Business Service Provider (BSP) and notes that a number can be connected to only one service at a time (Zoho), so the first step is deciding where your number lives.
If the number is already in Zoho Desk, the agent works inside that channel: a webhook flags every incoming message, the agent picks up the conversation through the API, replies with data from your systems and, when a person is needed, assigns it to someone on your team, who continues in the same chat. The API only lets a user reply to a conversation assigned to that user, so it's always clear who owns it.
If your WhatsApp number isn't in Zoho Desk yet, the agent answers from its own number and logs each conversation as a ticket through the API, with the history inside; how your team follows up on a handed-off case is defined during discovery. Either way, messages the business starts need a template approved by Meta. In the Zoho Desk channel, those messages are also paid for with WhatsApp credits bought upfront in Zoho (Zoho).
| Dimension | Number in Zoho Desk | Agent's own number |
|---|---|---|
| Where replies happen | In the Zoho Desk chat, through the messaging API | From the agent's number |
| Ticket | Zoho Desk creates it based on your settings | The agent creates it through the API |
| Handoff to a person | The conversation is assigned in Zoho Desk | Defined during discovery |
| Alert for each message | Incoming message webhook | Reaches the agent directly |
The exact rules are defined with your team based on your edition and settings.
The channel rules don't change: messaging a customer first, or replying outside the 24-hour window, requires a template approved by Meta. Costs and categories are covered on the WhatsApp page.
What the Zoho Desk API exposes: tickets, messages, attachments and events
Zoho Desk exposes a REST API with OAuth 2.0: the app requests only the scopes it needs (tickets, contacts, search, events, messaging) and the token is bound to one organization. The base URL depends on your account's data center, from desk.zoho.com in the US to desk.zoho.eu in Europe, and Zoho says to take it from the token response instead of hardcoding it (Zoho Desk API).
Usage is measured in daily credits, based on your edition and number of users, and in concurrent calls: the Professional edition starts at 75,000 credits a day plus 500 per user, with up to 15 calls at the same time, and fetching a single record costs one credit, according to that documentation. For real time there are webhooks, which Zoho Desk includes in the Professional, Enterprise and Ultimate editions: they flag new tickets, updates, threads, attachments and WhatsApp messages, arrive signed with a JWT, and the receiving URL has to respond within 5 seconds (Zoho Desk webhooks).
Attachments travel through the API too: the event for a new thread includes its files and the API lists the attachments on every ticket. With that, Arconte reads the invoice, purchase order or packing slip, checks the data against your ERP and leaves the result as a private comment on the ticket, so your team sees it without opening the file.
| Surface | What the agent does | Good to know |
|---|---|---|
| Tickets and contacts API | Creates, updates and searches tickets; reads the contact and account | Scopes per module and daily credits by edition |
| Messaging API | Picks up the WhatsApp conversation, replies and assigns it to a person | Only replies to conversations assigned to its user |
| Webhooks | Hears about tickets, updates, threads, attachments and messages | In Professional, Enterprise and Ultimate; JWT signature; 5-second response |
| Comments and attachments | Reads the ticket's files and leaves private comments | A comment is set as public or private when it's created |
Based on Zoho Desk's documentation; limits depend on your edition and users.
About API limits: credits reset every 24 hours and unused ones expire; if you need more, Zoho lets you buy them. On editions without webhooks, changes are picked up by querying the API, and the agent's volume is sized with your team.
How the agent works alongside Zia, Zoho CRM and Zoho MCP
Zoho Desk has its own AI, Zia: Answer Bot uses your knowledge base to answer customers on your website and messaging channels, Guided Conversations builds low-code bots, and Zia Agents take roles such as support specialist or sentiment analyst, according to Zoho. Vantegrate's agent doesn't replace it: it covers the part that needs data from your other systems, like the order in your ERP or the account in your CRM, and the sale that continues on WhatsApp. During discovery we decide which conversations each one handles.
Zoho CRM and Zoho Desk are separate products: the CRM organizes leads, contacts, accounts and deals, and Desk handles support tickets. Zoho connects them with a two-way sync of contacts, accounts and products, and shows CRM data next to the ticket (Zoho). If you use both, the agent works with each one through its own API: the support case goes to Desk, and the lead or deal that starts in a conversation goes to the CRM.
Zoho also offers Zoho MCP, a service that connects models like GPT or Claude to the APIs of its apps, Zoho Desk included, with OAuth-based permissions (Zoho). It's another door to the same APIs; Vantegrate's integration works with the Zoho Desk REST API and webhooks, with the minimum scopes your use case needs.
| Zoho piece | What it does | What the agent adds |
|---|---|---|
| Answer Bot and Guided Conversations | Answer from your knowledge base or with prebuilt flows | Answers with data from your ERP and CRM |
| Zia Agents | Support, quality and sentiment roles inside Desk | The sale that continues on WhatsApp |
| Zoho CRM integration | Syncs contacts, accounts and products | Logs the lead or deal that starts in a chat |
| Zoho MCP | Connects AI models to Zoho's APIs | Integration through the REST API with minimum scopes |
Based on Zoho's pages; availability depends on your edition and plan.
Zoho Desk is a third-party product: Vantegrate integrates through its public API, and everything that already works in your account, including your bots and assignment rules, stays the same.
You've seen how it connects. Want to walk through your case?
Tell us how your Zoho Desk is set up and we'll tell you what data we need and where the agent connects.
An agent connected to your Zoho Desk vs. a standalone tool
| Standalone AI tool | Agent connected to your Zoho Desk | |
|---|---|---|
| Data source | A copy that drifts | Your source of truth, live |
| Where your data lives | In a third-party system | In your environment, encrypted end to end |
| Result of each operation | Stuck in another app | Written back to your Zoho Desk |
| Permissions and audit | Broad and hard to audit | Least-privilege scope and an audit trail |
| Reaching production | Often stalls as a pilot | Validated, phased rollout |
Why add an AI agent to your Zoho Desk
Third-party figures, each with its published source. None of them is a Vantegrate result.
125,000+
Businesses worldwide trust Zoho Desk, according to Zoho
20.3%
Of the tickets AI touches are resolved end to end, without a person
30%
Of service cases are already handled by AI, as service teams estimate
The number of businesses is Zoho's own count. Chatarmin's figure comes from 131 online stores that are its customers and doesn't represent e-commerce as a whole; Salesforce's is the estimate of 6,500 service professionals surveyed worldwide.
Which agents run on your Zoho Desk
Two products in the suite use this integration, each with the permissions it needs.
Sellium
Customer service and sales agent on WhatsApp: answers with data from your systems, opens and updates the ticket in Zoho Desk, reports the status of each case and hands off to your team with a summary when a person is needed.
Explore Sellium
Arconte
Document agent: reads the invoices, purchase orders and packing slips that arrive attached to a ticket, extracts the data, checks it against your ERP and leaves the result as a private comment on the ticket.
Explore ArconteThe integration doesn't take your tickets anywhere
AI comes to your data, not your data to the AI: the agent reads and updates your Zoho Desk through the official API, with the scopes you authorize. Zoho publishes its own certifications, including ISO/IEC 27001 and SOC 2 Type 2 (Zoho certifications).
- Connection through the official Zoho Desk REST API with OAuth 2.0: the token is bound to your organization and requests only the scopes your use case needs.
- Webhooks arrive signed with a JWT, which is verified before each event is processed.
- Your tickets, conversations and attachments stay in your Zoho Desk account, and every action the agent takes is logged.
- The agents run on Salesforce or Oracle Cloud Infrastructure, whose SOC 2 and ISO 27001 certifications belong to those platforms, not to Vantegrate; Zoho's belong to Zoho.
Frequently asked questions about the Zoho Desk integration
What support, customer service and IT teams ask before connecting an AI agent to their help desk.
How do I integrate Zoho Desk with an AI agent?
How do I integrate Zoho Desk with an AI agent?
With an app connected to the official REST API of Zoho Desk over OAuth 2.0, with the scopes your use case needs, and with the webhooks that flag new tickets, status changes and incoming messages. The agent answers on WhatsApp, opens and updates tickets, reports the status of each case and hands off to your team with a summary. Vantegrate sets up the connection; your team authorizes the permissions and validates. Meet the agent in Sellium.
Can the agent handle the WhatsApp number I already connected to Zoho Desk?
Can the agent handle the WhatsApp number I already connected to Zoho Desk?
Yes, if your Zoho Desk edition includes instant messaging. Its messaging API lets the agent pick up the conversation on WhatsApp, reply and assign it to a person on your team, who continues in the same chat. Since Zoho connects each number to a single service, the number stays in Zoho Desk and the agent works through the API. During discovery we decide which conversations the agent takes and which go straight to your team.
How is the agent different from Zia, Zoho Desk's AI?
How is the agent different from Zia, Zoho Desk's AI?
Zia answers from your knowledge base, runs guided bots and helps your agents with summaries and reply suggestions inside Zoho Desk. Vantegrate's agent works with data from your other systems, like the order in your ERP or the account in your CRM, and carries the sale that continues on WhatsApp. They can work side by side: during discovery we decide what each one handles.
What's the difference between integrating Zoho Desk and Zoho CRM?
What's the difference between integrating Zoho Desk and Zoho CRM?
Zoho CRM is the sales system (leads, contacts, accounts and deals) and Zoho Desk is the support system (tickets and conversations). Zoho syncs them both ways and the agent works with each one through its own API: the support case goes to Desk and the lead or deal that starts in a conversation goes to the CRM, where the sales agent qualifies it and moves it through your pipeline.
Can the agent handle US customers on WhatsApp?
Can the agent handle US customers on WhatsApp?
Yes, for support conversations. WhatsApp is used by 32% of US adults (Pew Research Center), so it works best as one more channel next to the email, chat and phone your team already runs in Zoho Desk. Meta does not deliver marketing template messages to US phone numbers (Meta), but a reply inside a conversation the customer started isn't a template, and Meta lists a follow-up on a support case the customer asked to move to WhatsApp among its utility template examples (Meta).
WhatsApp integration
The official API as the agent's channel: templates, the 24-hour window and costs.
Learn moreAI agent to human handoff
How the agent hands a conversation to a person with the full context.
Learn moreAI agents for enterprises
The full Vantegrate suite: sales, marketing, documents, data and logistics.
Learn moreLet's connect AI agents to your Zoho Desk
Tell us which Zoho Desk edition you use, where your WhatsApp number lives and how you hand off cases today, and we'll show you what the agent takes on, which permissions it requests and how each conversation lands in your help desk. A 30-minute conversation, no commitment.
Francisco Morales, co-founder, takes your call. We reply on WhatsApp within 4 business hours, no strings attached.
