How Do You Set Up SLAs and Escalations in Zoho Desk?

How do SLAs work in Zoho Desk?

An SLA in Zoho Desk is a set of rules that gives each ticket a response due time and a resolution due time. Each SLA belongs to one department and applies to the Tickets module.

An SLA contains targets. Each target has conditions, for example Priority is High, and the times that apply when those conditions match. Zoho allows up to 10 targets per SLA on the Standard, Professional and Enterprise editions, and one target on Free and Express.

SLAs can be global, tied to specific accounts, or linked to a contract through a support plan. When more than one could apply, Zoho checks a valid contract SLA first, then an account SLA, then the global SLA. Customer-based SLAs are listed for Professional and Enterprise, and contract management for Enterprise only.

You also choose when the SLA runs: on ticket creation or update, on a field update such as priority, on a customer reply, on an agent response, or on comments. Each selected trigger resets the SLA, so choose only what you need.

How do you create an SLA in Zoho Desk step by step?

You need the Support Administrator role. Set up business hours, holiday lists and ticket statuses first, because the SLA depends on them.

1. 1Go to Setup > Automation > SLA, pick the department and click New SLA.
2. 2Name the SLA and choose whether it applies to all accounts or selected accounts.
3. 3Choose the execution triggers, for example ticket creation and a change of priority.
4. 4Add a target for each priority or customer type, with conditions on the ticket fields.
5. 5Set the response time and resolution time in minutes, hours or days.
6. 6Decide whether the response time applies to the first response only or to every reply.
7. 7Choose Business Hours or Calendar Hours for the target.
8. 8Add response and resolution escalations, then save and test on a sample ticket.

Note that Zoho counts a ticket as resolved only when its status is Closed, so agree with the team when a ticket should be closed.

How do business hours and holiday lists affect SLA timers?

If a target uses Business Hours, the timer only runs during working hours and skips non-working days and holidays. If it uses Calendar Hours, the timer runs around the clock. Use calendar hours only for genuine 24/7 coverage, such as critical incidents.

Zoho has updated holiday lists so you can keep several lists for teams in different regions, set recurring holidays so they do not need re-entering each year, and add holidays that span several days. Zoho describes business hours and holiday lists as organisation-wide settings that affect SLAs, time-based actions, Blueprints, telephony and chat. What you can configure varies by edition, so check your plan.

Ticket status matters too. Every status maps to one of three types: Open, On Hold or Closed. When a ticket moves to an On Hold status, such as Awaiting Customer Response, Zoho freezes the SLA timers and pauses escalations. When it returns to Open, the timers resume with the hold time removed. A customer reply moves the ticket back to the default status automatically.

How do escalation levels work in Zoho Desk?

Escalations are the actions Zoho Desk takes when a due time is close or has passed. You set them separately for response and resolution, and each level can fire before, on or after the due time.

A common pattern is a warning to the agent before the response is due, then a notification to the team lead when it is missed. For resolution, level one alerts the owner, level two the lead, and later levels the support manager and, for key accounts, the account manager.

What should teams in different regions plan for?

Most SLA problems across regions come from calendars rather than from Zoho itself.

• USA and Canada: teams often cover several time zones. Decide whether your SLA follows the customer's hours or the team's hours, and build business hours to match. Canadian public holidays differ by province.
• UK and EU: bank holidays differ between England and Wales, Scotland and Northern Ireland, and between EU countries. Keep one holiday list per team location. If customer contracts promise response times, link those accounts to contract or account SLAs.
• UAE and the Gulf: set business hours to the working week your team actually staffs, and add reduced hours for periods such as Ramadan if your team works shorter days.
• India: holidays vary by state, so a team in Chennai and a team in Pune may need different lists. Shared services teams covering US or UK customers may need business hours that match the customer, not the office.

What are the common SLA mistakes in Zoho Desk?

These are the faults we find most often when reviewing SLA setups that managers no longer trust:

• Selecting every execution trigger, so the SLA resets each time anyone comments.
• Custom statuses such as Waiting on Supplier mapped to Open instead of On Hold, which causes false violations.
• Using calendar hours for a team that works five days a week.
• Workflow rules that change priority after the SLA has been applied. Zoho runs workflow rules before SLAs, so test the order.
• Escalation emails sent to a shared inbox nobody reads.
• Targets based on fields agents often leave blank, so tickets fall back to the wrong target.

Flowpeak designs and tests Zoho Desk SLAs remotely, including holiday lists for teams in several countries and escalation paths that match your contracts. Work is quoted in writing after a free scoping call.

Frequently asked questions