Multi-Channel
Email, chat (Zoho SalesIQ embed), phone (Zoho Voice integration), social (X, Facebook, Instagram DMs), web form, WhatsApp Business, and Telegram all land in the unified ticket queue. The Agent Workspace shows all channels in a single inbox view, eliminating tab-switching. Channel-specific parsing extracts the customer email and creates or updates the Contact record. Email forwarding is the most common setup — point your support@ alias to a Zoho-provided forwarding address, and inbound mail becomes tickets.
SLAs
Response and resolution targets per priority (Low, Medium, High, Urgent). Business hours per team handle global support — APAC team’s “9am-6pm IST” SLA differs from EMEA’s “9am-6pm CET”. Escalations on breach route to a designated manager and optionally update the ticket priority. Configure SLA per ticket category, channel, or contract — an Enterprise customer’s SLA differs from Free tier. Pause SLA on “Awaiting Customer Response” status to avoid penalizing the team for customer-side delay.
Blueprints
Ticket lifecycle as a state machine — same model as CRM Blueprints. Stages enforce required fields, validations, and transitions. A typical support flow: New → Triaged → In Progress → Awaiting Customer → Resolved → Closed. Each transition can fire actions (notify customer, update field, call webhook, run Deluge). Works well for complex service processes (warranty claims, billing disputes, technical escalations) where you need audit-able process compliance.
Knowledge Base
Internal and public KB with version control and approval workflows. Suggested articles surface in the agent UI based on ticket subject and description (Zia-powered). Public KB deflection — measured by “Article views without ticket creation” — reduces ticket volume by 15-30% in mature setups. Multi-language KB serves global users from a single article tree with per-language variants. Article ratings (helpful/not helpful) and search-no-results reports surface content gaps.
Integration with CRM
Tickets link to CRM Contacts and Accounts via email match. Agents see full customer context (deal pipeline, last sales contact, account ARR) in the ticket sidebar. Sales sees service history (open ticket count, recent escalations) on the CRM record. Unified customer view without integration plumbing — both apps share the same Contact and Account records natively. Configure the integration under Setup → Marketplace → Zoho → CRM.
Zia Capabilities in Desk
Zia handles ticket sentiment classification (Positive, Neutral, Negative), auto-tagging (extracts keywords for categorization), reply suggestions (drafts a response based on similar resolved tickets), and Answer Bot (deflects via KB before creating a ticket). Sentiment-based routing — auto-escalate any Negative-sentiment ticket from a Customer over $50k ARR — is one of the highest-leverage Zia configurations.
Common Failure Modes
Stale macros: 200+ macros accumulate, agents pick wrong ones, customer experience degrades. Quarterly macro audit. SLA violation false positives: tickets marked “Awaiting Customer” still tick if the status auto-reverts on inbound reply — verify the SLA pause/resume logic. Knowledge base rot: articles become outdated; require a quarterly review with article owner attestation.
Cost Considerations
Free plan covers 3 agents and email-only. Standard adds multi-channel; Professional adds Blueprints; Enterprise adds Zia, custom modules, and the Answer Bot. Compare against Zendesk, Freshdesk, and Salesforce Service Cloud on three axes: per-agent cost (Zoho roughly 50-60% cheaper at equivalent tiers), CRM integration depth (Zoho wins inside its ecosystem), and AI maturity (Zia trails ServiceNow’s AI but matches Zendesk’s).
What to do this week
Audit your SLA pause logic on “Awaiting Customer” status, configure Zia sentiment-based escalation for high-ARR accounts, and run the KB search-no-results report to surface your top 10 content gaps.
