Zoho Desk SLAs, Explained: Business Hours, Escalations and the Customer-Tier Field That Drives Them.
A service level agreement in Zoho Desk is a promise the help desk makes to itself: a ticket of this kind, from this customer, will get a first response within this many hours and a resolution within that many, counted on this calendar, and if the promise is missed, these people hear about it. Zoho Desk has the machinery for all of that, and most teams configure a third of it. This is the whole of it, in the order to set it up, and then the part that is usually missing: the field that decides which promise a ticket gets.
Before a target means anything, the system has to know when the clock runs. Business hours in Zoho Desk are a named calendar: the days, the hours, the time zone, and the holidays. A target of four hours against a nine-to-five calendar is a different promise from four hours against twenty-four-seven, and a ticket raised at five on Friday is either due at nine on Monday or at nine on Saturday depending on which calendar the policy uses.
Most teams need two calendars: the standard support hours for most customers, and an extended or round-the-clock calendar for the customers who paid for it. Define both before any policy, because a policy references a calendar and you cannot change the reference on a live ticket without recalculating its due time.
An SLA policy in Zoho Desk is a table: for each priority (low, medium, high, urgent), a first-response target and a resolution target, measured on the policy's calendar. A standard policy might promise a first response in eight business hours for low and one hour for urgent, and resolution in five business days for low and eight hours for urgent. A premium policy halves those.
Two configuration details decide whether the policy works in practice. First, the targets are per priority, so the priority has to be set correctly and early, which means a rule that sets it from the ticket's channel, subject or customer rather than leaving it at the default. A ticket that sits at medium because nobody changed it is a ticket the premium policy never sees as urgent. Second, the clock pauses on a status. Decide which statuses stop the clock (waiting on customer, waiting on third party) and which do not (in progress, escalated), and write that into the policy, because the resolution target is only fair if time waiting for the customer does not count against the agent.
A target without a consequence is a report. The escalation is the consequence: when a target is approaching or missed, Zoho Desk performs an action. The actions available are an email to named people, a change to the ticket (reassign, raise priority, add a tag), and a notification to the agent. The standard pattern is three levels: at seventy-five percent of the target, notify the agent; at the target, notify the team lead and reassign if the agent is unavailable; at double the target, notify the head of support and the account owner in sales.
The last recipient is the one teams forget and the one that matters. A missed resolution on a premium account is a renewal risk, and the person who owns the renewal should hear about it before the customer brings it up. That recipient lives in the CRM, as the account owner, which is the first sign that the SLA does not stand on its own.
A help desk with two policies has to choose one per ticket, and Zoho Desk does this by criteria: the policy applies when the ticket matches a rule on its fields. The rule can read the channel, the department, the product, or a field on the contact or the account.
Here is the commercially important version of that rule: the premium policy applies when the customer's tier is premium. The tier is the plan they are on, the contract value, the renewal date, the strategic flag, whatever the business uses to decide who gets the faster promise. And that tier is not a help desk fact. It is a sales fact, decided when the deal closed and changed when the account grows or shrinks, and it lives on the account in Zoho CRM.
Without the connection, the help desk has three bad options. The agent reads the tier from the CRM by hand and sets a field, which happens for the first month. The tier is typed into Desk once at onboarding and never updated, so the customer who upgraded in March is on the standard policy in September. Or every ticket gets the default policy, and the largest account waits in the same queue as a free trial. The SLA is configured perfectly and it treats every customer the same, because the field that selects it never arrived.
With Zoho CRM connected to Zoho Desk, the account and its fields are synchronised into Desk, so the tier is on the Desk account the moment it changes in the CRM. The policy criteria read it, the right policy attaches when the ticket is created, the clock runs on the right calendar, and the escalation reaches the account owner because the owner came across with the account. Nobody typed anything twice, and the customer who upgraded in March was on the premium policy in March.
The same connection carries the ticket history back to the CRM, so the account owner sees the missed SLA on the account before the renewal call, and the quarterly review can show the customer their own response times. That is the loop the Customer Success work is built on: the help desk promises according to what sales sold, and sales sees what the help desk delivered.
Calendars first, two of them. Then the priority rule, so tickets arrive with the right priority. Then two policies, standard and premium, with the clock-pausing statuses decided. Then three escalation levels per policy, with the account owner on the last one. Then the connection, with the tier and the owner on the fields that sync. Then the policy criteria that read the tier. In that order, each step has what it needs from the one before, and the whole thing takes a week including the test.
Teams choosing between help desks sometimes ask whether this is a Zoho Desk strength or a weakness, and the honest comparison in our piece on Zoho Desk against Zendesk is that both can run tier-driven SLAs; the difference is that in the Zoho suite the tier field and the connection are already on the same data model, which is the part that otherwise costs an integration project.
An SLA is only as good as the field that selects it. Discovery is no-risk: we read your policies, your calendars and your CRM tiers and show you which customers are on the wrong promise today, and you pay only if you go ahead.
In a no-risk discovery we show where your service team, your tickets and your customer records stop agreeing, and what one connected system would change. You pay only if you proceed. The 6-minute guided demo shows the system first. Or see how we approach it.
More on the same problem:
Start a Zoho One trial through our sign-up, or tag us as your Zoho partner for free consulting time every month.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.