Zendesk Out of Office
Somebody goes on holiday with fourteen open tickets assigned to them. Zendesk out of office handling doesn't exist natively, which is the whole problem.
What Zendesk doesn't do on its own
There is no built-in concept of an agent being away. Assignment does not expire. An SLA clock doesn't pause because the assignee is on a beach. A ticket assigned to somebody who left the country on Friday will sit there quietly accruing age until a human notices.
That's worth stating plainly, because a lot of teams assume the platform handles it and only discover otherwise when a customer escalates after nine days of silence.
What you have instead is a set of parts you assemble: an app for marking agents away, triggers and automations for the reassignment, schedules for the calendar side, and a communication plan for the customer. None of them is hard. All of them are optional, which is why most teams have none.
The Zendesk out of office app
Zendesk publishes an Out of Office app in its marketplace. Broadly, it lets you mark an agent as away, shows that state to other agents on the ticket, and can act on tickets assigned to that agent, typically by unassigning or reassigning them so they return to a queue somebody is watching.
Two honest caveats before you build a process on it. First, several Zendesk marketplace apps come from Zendesk Labs and are supported on a best-effort basis rather than as core product, so check the listing for its current status and last update. Second, the exact behaviour and options have changed over versions, so read the app description in your own account rather than trusting a blog post about how it worked two years ago.
Used well, it does the important thing: it makes absence visible inside the tool, instead of living in a shared calendar nobody has open.
Reassigning without the app
You can get most of the value with configuration you already have.
oof_cover when they leave, then run an automation that unassigns anything with that tag which has been untouched for a day, sending it back to the group queue.The pattern that fails is relying on individual handover conversations. They work fine until somebody is off sick unexpectedly, which is exactly when you need the process most.
Holiday schedules and the SLA clock
Different problem, same word. A schedule in Zendesk defines your business hours, and it supports holidays: specific dates or ranges when the clock stops.
Get this right and your SLA numbers become honest. A ticket that arrives at 4pm on Christmas Eve should not be burning a four-hour first-response target through a public holiday, and if your schedule has no holidays configured, that is precisely what it does. Your attainment number then reflects your calendar rather than your performance.
Set the holidays once a year, per schedule, for every region you support. Then check your SLA policies are actually attached to a schedule rather than running on calendar hours, because a policy on calendar hours ignores the schedule entirely.
Telling the customer, carefully
An auto-reply during a shutdown period is a good idea, badly implemented most of the time.
Good: a trigger scoped to tickets created during a known closure window, saying you're closed until a specific date, giving a genuine emergency route, and setting expectations for the return. Specific dates. Real alternatives.
Bad: a generic away message that gives no date, offers no alternative, and reads as a brush-off. Those generate a second ticket within the hour, because the customer reasonably concludes nobody read the first one and tries a different channel.
And do not auto-reply per agent. Customers write to a company, not to Ahmed. A message saying "Ahmed is on leave" when the customer has never heard of Ahmed just adds confusion to a queue that already has plenty.
Frequently asked questions
How do you handle agent vacation in Zendesk?
Reassign before they go, not after. Zendesk agent vacation has no native concept, so teams use the out of office app or a view. A Zendesk holiday schedule affects SLA clocks rather than assignment, and a Zendesk auto reply on the agent's address helps nobody if the ticket is still assigned to them.
Does Zendesk have a built-in out of office setting?
Not as a core assignment feature. There is a marketplace app for marking agents away and acting on their tickets, and beyond that you assemble the behaviour from triggers, automations and views.
What happens to tickets assigned to an agent on holiday?
Nothing automatically. They stay assigned, keep ageing and keep burning their SLA target until somebody reassigns them.
Do holiday schedules pause SLA timers?
Yes, provided the SLA policy uses business hours and the schedule has the holiday configured. A policy running on calendar hours ignores schedules completely.
Should we send an auto-reply when the team is closed?
Yes, if it names a specific return date and offers a real emergency route. A vague away message tends to produce a second ticket rather than a patient customer.
How do we stop tickets sitting unassigned during cover?
Keep a permanent unassigned view sorted oldest first and make checking it somebody named responsibility each day. It covers holidays, sickness and every other orphaning route at once.
Silence produces second tickets
A customer who hears nothing writes again through another channel. Ticket Merger links the two so nobody answers both.
Start free trial14-day free trial. No credit card required.