Zendesk Business Hours, Groups and Routing

Zendesk business hours, groups and routing are the three settings that decide where a ticket goes and when the clock runs. Get them wrong and everything downstream reports nonsense.

Start free trial All Zendesk guides

Zendesk business hours

Schedules define when your team is working. Everything time-based depends on them: SLA targets, automations that fire on ageing tickets, and any report that measures elapsed time.

You can run several schedules, which matters for follow-the-sun teams or for a brand with different support hours. Holidays belong here too. Forget them and you've got the classic cause of a bad SLA month every December.

Groups

Groups are teams. Assign to a group first and a person second. That's the pattern that stops a ticket belonging to somebody who's on holiday.

Keep the number small. Every group needs its own views, its own routing rules and somebody watching its unassigned queue. Groups that nobody watches are where tickets go to age.

Routing that holds up

Route to a group, not a person. Personal assignment is how a ticket waits three days for one agent to come back.

Have a default. Every ticket that matches nothing must land somewhere watched, not in a void.

Watch the unassigned view. The most valuable view in any Zendesk instance.

Don't over-route. Ten narrow rules that each catch three tickets a week are ten rules to maintain and debug.

What this has to do with duplicates

Routing spreads related tickets across teams. When the same customer writes twice and the two tickets are worded differently enough to route to different groups, neither agent ever sees the other ticket.

That's a routing side effect rather than a routing failure, and it's why duplicate detection has to work across the whole account rather than inside one view.

FAQ

Frequently asked questions

Does Zendesk omnichannel routing respect business hours?

It respects agent availability rather than the clock. Zendesk omnichannel routing assigns on who is online and how much they're already holding, so business hours matter for SLA calculation and triggers, not for the assignment itself.

Do SLA policies use Zendesk business hours?

They can, and you choose per policy. On a weekend ticket, calendar hours and business hours won't give anything like the same answer.

How many groups should we have?

One per team that genuinely owns a distinct queue. Every extra group needs a watcher.