Zoho Desk for IT Services and MSPs: Tiers, Contracts, Hours

An IT services firm or managed service provider can run client support on Zoho Desk, but the edition decides how much of the MSP workflow you get. Professional is the realistic floor: $35 per agent per month billed monthly, or $23 per agent per month billed annually ^[1]. It brings up to 10 departments you can run as support tiers, round-robin assignment, one Blueprint per department, telephony and five webhooks. Contracts, ticket-credit support plans and branded portals per client need Enterprise, at $50 per agent per month billed monthly or $40 per agent per month billed annually. Time entry starts on Standard. One naming trap first. Searches for zoho service desk usually mean ManageEngine ServiceDesk Plus, a separate IT service management product, not Zoho Desk.

Which edition fits a desk with tiers and contracts

Free stops at 3 users with no workflow rules or custom fields, and Express stops at 5 users with a single department. Standard removes the user cap and adds time entry, four SLA policies and the Zoho CRM, Jira and Slack integrations, which Free and Express lack. It still runs one department, so every tier shares one queue and one rule set. Once first-line, second-line and specialist queues need their own rules, Professional is where the structure appears. Every active agent needs a license on the same edition, and deactivated seats stay billed until you reduce the count; the full pricing rules cover the rest.

The jump to Enterprise is easier to judge in numbers. For eight agents billed annually, Professional comes to $184 a month and Enterprise to $320 a month, a gap of $136 a month, by our arithmetic. Enterprise includes 50 light agents, while on Standard and Professional each one is an add-on at $6 per light agent per month (not available on Free or Express). Light agents can view tickets and add private comments but cannot reply or take assignments, which suits engineers and account managers. At eight full agents, the included seats cover the gap once you need about 23 light agents, roughly 2.8 per full agent. Below that, pay for Enterprise only for contracts, branded portals or skill-based routing.

The morning queue: alerts, tiers and routing

Zoho's customer story says SysGroup, a UK provider, handles 2,000 to 3,000 tickets a month, and roughly half are monitoring alerts that systems at data centers and customer sites raise on their own ^[2]. Support email lands in first-line, second-line and third-line queues, and assignment rules send larger customers straight to a dedicated specialist. That shape maps onto departments: Zoho's MSP page describes departments as separate support tiers, with agents grouped into teams inside each. Teams start on Professional.

Routing splits the editions again. Round robin starts on Professional and spreads tickets by load or in sequence; Zoho's customer story about Booth, an outsourcing firm, says tickets go to whichever agent is online, and agents toggle themselves active or inactive. Direct assignment rules number 5 on Standard, 15 on Professional and 30 on Enterprise. Skill-based assignment, which routes by language or domain expertise, is Enterprise only, with up to 30 active skills per department.

AI triage depends on edition and data center. SysGroup's first-line agents let Zia draft a level-zero reply, then validate it before sending. On Express and Standard, drafting runs only with your own OpenAI key (DeepSeek in the China data center), billed by that provider. Zoho's native Zia model starts on Professional and runs only in the US, IN, AU, EU, JP and CA data centers. Only one generative AI service can be active per organization. Sentiment analysis starts on Standard for English text; non-English sentiment is Enterprise only and not available in the SA or UAE data centers. Anomaly alerts on ticket traffic, which Cartika's story says help supervisors step in, start on Professional. Field predictions and auto tags read English text only.

Contracts, support plans and the SLA clock

Zoho's MSP page says SLAs can set response and resolution times by priority, channel, time due and customer type. Booth's story describes four levels: P1 resolved within 4 hours, P2 within 8, P3 within 24 and P4 within a week. Customer-based SLAs start on Professional. Two clock rules matter for client reports. An SLA linked to business hours counts only working time, and an On hold status freezes the timer and stops escalations. Firms covering clients in several time zones should note that only Enterprise allows more than one business-hours set.

Contracts are the Enterprise feature that matters most here. A contract links an account to one support plan and shows as Future, Active or Expired, with expiry alerts a set number of days ahead. A ticket-based support plan sets a credit limit and a credit cycle, such as 100 tickets a week; tickets inside the limit follow the plan's SLA, and further ones can be charged under the contract ^[3]. A valid contract SLA wins over an account SLA, which wins over the global one. Plan carefully. Once tied to a contract, a plan's type, credit cycle and SLA are locked, and the Contracts module has no custom views or mass actions.

Logging hours and turning them into invoices

Manual tracking is the default, and timers can run on several tickets at once. Automatic tracking logs replies, draft replies, field updates, approvals, comments, resolutions and remote sessions, can pause after 30 seconds of idle time, and gives agents 10 seconds to edit logged time ^[4]. It does not log work done by workflow rules or AI agents. Each entry records time spent, the agent's cost per hour, any additional cost and a computed total in your company currency. On each account, a Time Entry tab splits hours into total, billable, invoiced and non-billable.

To bill, connect Zoho Books or Zoho Invoice, one at a time, not both. Agents can then create invoices and estimates inside a ticket and see a client's unused credits and outstanding receivables. Zoho's customer story says Avineon used time-per-ticket dashboards to see which request types run long and whether some customers were underpaying; Avineon reports cutting labor costs by nearly 50%. VNMT Solutions sees Zoho Books billing details inside tickets and reports invoice resolution time down 32%. Treat both as single-firm results, not a forecast.

Remote sessions and the engineering handoff

Agents can start a Zoho Assist remote session from inside a ticket. The plan comparison lists one free Assist user on every edition, and each further technician needs an Assist license. Unattended access works only for online devices, after the client installs software from a link the agent sends. When the session ends, the agent sets the ticket status, edits the resolution and adds session notes. Remote time joins the automatic tracker only with the Assist add-on.

Escalations to engineering run through Jira, GitLab or Azure DevOps. The Jira integration, Standard and higher, works with cloud and on-premise Jira, maps departments to projects many-to-many, and syncs comments and status both ways in real time. An on-premise Jira must run HTTPS and be reachable from the internet, and only comments posted after linking sync. RJG, a technology and consulting firm, connects Desk to Jira and Confluence^[p1] so engineers see the tickets that need them. A GitLab extension turns tickets into issues, and Professional's five webhooks can push ticket and time-entry events to your own tools.

Where Zoho Desk stops short for an MSP

It is a help desk, not an IT service management suite. Zoho's customer story about THG Ingenuity describes a client portal for tickets connected to ManageEngine ServiceDesk Plus, the route Zoho's own customers take when they need both. Several MSP-shaped features sit only on Enterprise: branded help centers per client, layout rules (which Booth pairs with Blueprints), the sandbox Analysis Prime uses to test rules, and Deluge custom functions. Departments can be disabled but never deleted. Disabling one hides its tickets, contracts and SLAs.

Branded portals carry their own rules. Each brand is a department with its own help center, logo and up to 3 secondary domains, on a common user base with one login for every portal or a unique base per brand. Switching to unique users needs at least two branded help centers and cannot be rolled back by an admin, and disabling multi-brand then deletes the branded help centers. Decide before onboarding clients. The automation guide covers Blueprint and SLA setup.

The bottom line

Zoho Desk fits IT services firms and MSPs that bill time and run tiered queues, as long as the edition matches the workflow. Standard covers time entry and Jira for a single queue. Professional adds departments as tiers, round robin, Blueprint, telephony and webhooks, and it is the sensible start for most firms. Move to Enterprise when contracts with ticket credits, per-client portals or skill-based routing are part of how you sell support, or, for a team of about eight full agents billed annually, when you need roughly 23 or more light agents, by our arithmetic. Above about 17 full agents, the 50 included light agents can no longer cover the gap. Pair it with ManageEngine ServiceDesk Plus only if you also need full IT service management.