Plan requirement
| App | Holidays |
| Subscription | Any Zendesk Support plan |
| Access | Admin |
Importing public holidays into a Zendesk schedule instead of typing them in, which is what makes it worth having.
What it is for
Zendesk schedules let you mark holidays as non-working days. Entering them is manual, and for a company operating in several countries that is a long afternoon every year.
The app imports them: choose the countries and regions you need, choose which schedule they go into, and they are there.
What it covers
230 countries and around 3,000 regions. You choose the kind of calendar you want: national, local, religious or observance, so you can take the ones that matter and leave the rest.
What you choose per import
Four things: the country, the kind of calendar, this year or next, and the language the holiday names are written in. Then you pick all the holidays it found or just some, and the schedule they go into.
That year choice is the one to plan around. You cannot load three years ahead in one go, so an admin who sets up the schedules in December is importing next year, and comes back for the year after that. Zendesk itself only accepts holidays up to two years ahead, so the two limits sit close together.
What it does not do
It fills a schedule; it does not change what a schedule can hold. Anything Zendesk itself cannot express, the app cannot add.
So a day where you close at lunchtime is still not possible. A holiday is a whole day off or it is nothing, and that is Zendesk's limit rather than ours.
Why it matters beyond opening hours
Everything that counts working time reads the schedule: first reply targets, SLA clocks, and anything that works out a date in working days. A missing holiday quietly makes all of those wrong for a day.
Import selectively
Bringing in every observance for a country produces a schedule full of days your office is open. Take the ones you close on.
Comments
0 comments
Article is closed for comments.