Skip to main content
Escalate complex issues to your Zoho Desk support team. When the AI can’t help, it creates a ticket automatically — and agent replies flow back into your unified BubblaV inbox.

Why Connect Zoho Desk?

  • Seamless Escalation: Complex issues go to human agents as proper Zoho Desk tickets
  • Bidirectional Sync: Ticket updates and agent replies land in the Live Support inbox; BubblaV replies post back to the ticket
  • Knowledge Ingestion: Import help-center articles and closed tickets so the chatbot answers from your own content
  • OAuth Connect: One approval in Zoho — no API tokens to create or rotate, and no marketplace app to install

Setup Steps

1

Navigate to Integrations

Go to DashboardIntegrationsZoho Desk
2

Pick Your Data Center

Choose the Zoho region your account lives on — United States (.com), Europe (.eu), India (.in), Australia (.com.au), Japan (.jp), Canada (.ca), or Saudi Arabia (.sa). Check the URL suffix after signing in at accounts.zoho.com if unsure.
3

Authorize Access

Click Continue with Zoho. You’ll be redirected to Zoho to review permissions and click Accept.
4

Verify Connection

After authorization, you’ll land back on the Zoho Desk configure page with the connection status showing your organization name. The six Zoho Desk tools are synced automatically — three are hidden (dashboard/copilot-facing) and three are available to the chatbot.

How It Works

Zoho Desk syncs by polling: every couple of minutes BubblaV checks for tickets changed since the last sync. No webhooks or marketplace app are involved.
  1. New Tickets: Tickets created in Zoho Desk appear in the BubblaV Live Support inbox, with the requester linked by email
  2. Zoho Desk → BubblaV: When an agent replies to a ticket in Zoho Desk, the reply appears in the live support conversation
  3. BubblaV → Zoho Desk: When you reply in BubblaV live support, the message is posted to the Zoho Desk ticket (public for agent replies, private notes for visitor messages)
  4. Status Sync: Closing a ticket in Zoho Desk resolves the matching conversation in BubblaV

Available Tools

Once connected, these tools become available:

How Escalation Works

  1. Customer asks a question AI can’t answer
  2. AI offers to create a support ticket
  3. Customer confirms with their email
  4. Ticket created in Zoho Desk with the full conversation context (the requester contact is found or created by email)
  5. Your team responds in Zoho Desk — the reply appears in the BubblaV conversation

When Tickets Are Created

  • Customer explicitly requests human help
  • AI says “I don’t know” multiple times
  • Complex issues beyond AI capabilities
  • Customer asks for escalation

Knowledge Sync

From the Zoho Desk configure page you can:
  • Import articles — your help-center categories and articles become knowledge sources
  • Import closed tickets — past resolutions (with personal details anonymized) become searchable answers
  • Sync now / Force re-sync — push imported sources into website_content so the chatbot can cite them

Draft Replies with Copilot

Zoho Desk tickets in your Live Support inbox support one-click Draft reply:
  • Open any Zoho Desk ticket and click Draft reply — AI Copilot drafts a response grounded in your knowledge base and the ticket’s conversation history.
  • Review and edit the draft, then send it. The reply is posted to the Zoho Desk ticket as a public comment, so the customer sees it in their original support channel.

Troubleshooting

  • “No Zoho Desk organization is accessible” — your Zoho account is valid but has no Zoho Desk organization on the selected data center. Sign in at desk.zoho.eu (or desk.zoho.com / .in / etc. matching your chosen region) with the SAME account you connected with and create / activate the organization, then reconnect. Note: Zoho accounts are data-center specific — an org created under a .com account is invisible to a .eu account.
  • Wrong data center — if connecting fails or ticket lookups return empty, reconnect and pick the data center matching your Zoho login URL (the .eu/.in/etc. suffix).
  • Connection requires reconnection — your refresh token was revoked (e.g. password reset or revoked sessions in Zoho). Click Reconnect with Zoho in the configure panel.
  • Sync gaps after long downtime — the poll cursor pauses during failures and resumes automatically; if you suspect missed tickets, run Force re-sync on knowledge sources and check the Live Support inbox again.