Direct integration with your Zoho Desk department. The web AI agent creates a ticket on session finalize when the visitor needs help, your human agents reassign and update status from the AI Support tab, and every change syncs back to Zoho Desk in real-time. No bridge service, no field mapping, your tickets stay in your Zoho.
A complete ticket lifecycle that starts in chat and lives in your Zoho Desk department.
When the LLM (or a human agent override) classifies a chat as a support request, ZohoDesk_Create_Tickets creates a ticket with the visitor's email, full chat description, and the request-context block (page URL, referrer, browser).
The AI Support tab shows the ticket pill, status selector (Open / On Hold / Escalated / Closed), and Resolved Tickets card. Status changes flow through ZohoDesk_Update_Tickets and update Zoho Desk live.
Set the optional zoho-desk-userid field per station and tickets created from that station's web sessions are auto-assigned to that Zoho Desk user — useful for routing by product line or shift.
Same OAuth client model as Zoho CRM. Four required fields, then pick a department.
At api-console.zoho.com, add a Self Client and request scopes Desk.tickets.ALL, Desk.contacts.ALL, and Desk.basic.READ. Generate a refresh token from the grant token (region-specific — use the same region endpoint your Zoho Desk org lives on).
Org ID is shown under Zoho Desk Setup → Developer → API. Department ID — call GET /api/v1/departments with your refresh token (or copy from the URL when you open a department in Zoho Desk). Pick the department where AI-Agent tickets should land.
Under Zoho's Integrations settings — typically https://mcp.zoho.com/desk-mcp/<org-key>/sse. Required so MyDaddy.io can create and update tickets in your Zoho Desk.
Portal: Settings → Integrations → Desk Provider → Zoho Desk. Paste the four required values and save — the change takes effect live, no restart needed. Set Active Desk Provider to Zoho Desk.
For each station, set zoho_desk_userid in Stations → Edit → Zoho Desk User ID. Tickets created from web sessions on that station's caller-id are auto-assigned to that Zoho Desk user. Leave blank to use Zoho Desk's own auto-assignment rules.
Open the AI support widget on your site, run a chat the LLM classifies as a help request, and resolve. A new ticket should appear in your Zoho Desk department within seconds. Change the status from the AI Support tab — it should update in Zoho Desk in real-time.
Stored under your workspace's namespace. Portal writes these for you.
| Key | Purpose | Required? |
|---|---|---|
organizations.<org>.desk-provider | Active desk routing (zoho · zapier · none) | Required |
organizations.<org>.zoho-desk-refresh-token | OAuth refresh token | Required |
organizations.<org>.zoho-desk-mcp-url | Your Zoho Desk connection URL | Required |
organizations.<org>.zoho-desk-org-id | Your Zoho Desk org ID | Required |
organizations.<org>.zoho-desk-department-id | Department where tickets land | Required |
stations.<ext>.zoho-desk-userid | Per-station auto-assign to a Zoho Desk user | Optional |
The AI Support tab's ticket controls only show up when Zoho Desk (or a Zapier fallback) is configured; the tab itself is always visible.
Direct integration, four fields to fill in, and your tickets stay in your Zoho org. Worth a try if it fits your stack.