Zoho Desk Setup Guide for 2027: From Departments to Reports

What should you decide before you open Zoho Desk?

Most Zoho Desk problems start as planning gaps. Agents end up with tickets in the wrong queue, SLAs fire on the wrong tickets, and reports cannot answer basic questions. A short planning session prevents most of this.

Use this checklist before anyone touches Setup:

• Departments: one per team or brand that has its own agents, email address and SLA.
• Channels: which of email, web forms, chat, phone, social and WhatsApp you will support in the first phase.
• Ticket statuses: which ones mean Open, On Hold and Closed, since status type controls SLA timers.
• Ticket fields: the five to ten fields you actually need for routing and reporting.
• Routing: by department, round robin, load or skill.
• Service levels: response and resolution targets by priority or customer type.
• Integrations: Zoho CRM, Zoho Books, telephony and anything else agents must see.
• Reports: the three or four numbers your manager will check every week.

How do you set up departments, channels and ticket fields?

Work through the setup in this order so that later steps have something to attach to. Departments come first because channels, SLAs and assignment rules are all tied to a department.

1. 1Create departments and add agents, roles and profiles so permissions are right from day one.
2. 2Set up the email channel under Setup > Channels > Email. Forward your support mailbox to the Zoho Desk address and map each support address to a department.
3. 3Add a From address for replies and the SPF record Zoho recommends, so replies are less likely to land in spam.
4. 4Customise ticket statuses and map each one to the Open, On Hold or Closed type.
5. 5Add custom ticket fields and layouts. Keep picklists short and agree the values with the team.
6. 6Add other channels: web forms, chat, social, instant messaging and telephony.
7. 7Turn on the help centre and knowledge base if you plan to offer self-service.

How should you configure assignment rules, SLAs and automation?

Zoho Desk runs automation in a fixed order when a ticket is created or updated. According to Zoho's SLA documentation, direct assignment rules run first, then workflow rules, then SLAs, then round robin, then Blueprint, then notifications. Design with that order in mind, otherwise a workflow can change a field after the SLA has already been chosen.

Start with direct assignment rules for clear cases, such as tickets from a key account going to a named team. Use round robin for general queues so work spreads evenly. Zoho lists round robin on the Professional edition and skill-based assignment on Enterprise.

For SLAs, create targets for each priority, choose business hours or calendar hours, and add escalations for response and resolution. Our separate guide on SLA and escalation rules covers this step in detail.

Use workflow rules for field updates, alerts and tasks, and Blueprint when a ticket must pass through defined stages, such as returns or onboarding.

Which Zoho Desk features depend on your edition?

Zoho sells Desk in several editions and the feature list differs between them. The table below reflects Zoho's published edition comparison when this guide was written. Check the official Zoho Desk pricing page for your region before you commit, because edition contents change.

What reports should a support team build first?

Zoho says Desk includes more than 30 built-in reports and more than 10 built-in dashboards. Start with those before you build custom reports, and add your own only when a question is not answered.

In the first month, most teams need: tickets received by channel and department, first response time, resolution time, SLA violations, open tickets by agent, and customer happiness ratings. If leadership wants support data next to sales or finance figures, Zoho Analytics can combine Desk data with other apps.

Reports are only as good as the field data behind them. If agents skip a category field, your top issues report will be wrong, so make reporting fields mandatory where you can.

Are there regional points for USA, Canada, Gulf, UK, EU and India teams?

Zoho runs regional data centres, including the US, Canada, Europe, India, Australia, Saudi Arabia and the UAE. Your data centre is set when the account is created, so pick it deliberately if your customers or regulators expect data to stay in a region. UK and EU teams should also read our notes on Zoho and GDPR.

Holiday calendars differ by country and, in some places, by state or province, so build a holiday list for each team you staff. Zoho says the help centre can run in more than 50 languages and the agent interface in more than 20. Confirm that each language you need is on Zoho's list, including Arabic for Gulf customers.

Many businesses in India and the Gulf treat WhatsApp as a main support channel, so plan it in phase one there rather than as an afterthought.

What are the most common Zoho Desk setup mistakes?

These are the issues we see most often when auditing existing Zoho Desk accounts:

• Too many departments, which splits reporting and confuses customers.
• Custom statuses mapped to the wrong status type, so SLA timers keep running while you wait on the customer.
• Dozens of optional fields that nobody fills in.
• Workflow rules and SLAs that overlap or contradict each other.
• Going live without testing replies, escalations and notifications on a sample ticket.
• No owner for the knowledge base, so articles go stale within months.

Flowpeak sets up and tidies Zoho Desk remotely from Chennai for teams in the USA, Canada, the Gulf, the UK, Europe and India. We start with a free scoping call, agree the design, and quote the work in writing before anything is built.

Frequently asked questions