For teams that run on Zendesk
Zendesk public holidays in each schedule
Zendesk schedules hold your business hours and holidays, so SLA timers pause when you are closed. Holidays are entered per schedule and at most two years ahead, so a team with schedules for several countries or states types the same dates in again each year.
How it goes today
- Look up the public holidays per country or state.
- Open each schedule and add every date by hand.
- Check the schedules that share holidays and those that do not.
- Notice a forgotten day when an SLA runs on a holiday.
How it can go
Keep SLAs and opening hours right on public holidays in every country.
You say which country or region belongs to each schedule. Each autumn the public holidays for next year are added to the right schedules, and days you close on top of that, such as a company day, are added as well. You get a list per schedule to check, and nothing is changed before you approve.
Say this in ChatGPT, Claude or Copilot
Your chat gets connected to Hypamoon first, with this request filled in. You paste your Zendesk key in the portal, never in the chat.
With Hypamoon, for each of our Zendesk schedules, add the public holidays of the country or region it belongs to for next year, plus our own closing days. Send me a list per schedule to check first, and add them after I approve. Do this again every autumn.
An administrator creates an OAuth client in Zendesk Admin Center, under Apps and integrations, APIs, OAuth clients, and limits what it may read and change. It stays yours.
More for teams on Zendesk
- I want a customer contact added as CC when a ticket matches a rule.
- Real emails end up in suspended and nobody looks in time.
- I want to see which macros are used and which are not.
- We only see the comment on a low rating if we open the ticket events.
- Customers want an overview of their company's tickets.
- I want to know what customers ask about, beyond how many tickets.
- I want help center articles as a PDF to print or send.
- A customer says thanks and the solved ticket is open again.
- When someone changes a trigger, I can't go back to how it was.
- I want the time we spent per client each month, so we can bill it.
- Tickets stay with an agent who is on leave.
- I copy every order number into the shop to see what is going on.
- I want to send one message to a list of customers from Zendesk.
- I log in to each review site to read and answer reviews.
- Our contracts allow a number of tickets per month and nobody keeps count.
- We pay for agents who have not logged in for months.
- I want a message when a queue goes over a number.
- People without report access ask me for an export every week.
- I want a ticket to come back on the date I agreed with the customer.
- For every billing question I open another system to see what they pay.
- The same customer opens three tickets about one question.
- The same customer has two or three profiles in Zendesk.
- I look up every tracking number on the site of the carrier.
- Buyer questions on the marketplaces are answered outside Zendesk.
- We want NPS again and the score next to the customer in Zendesk.
- A customer asks for their data and I search ticket by ticket.
- Customers send ID numbers and we remove them by hand.
- I want to see which customers keep opening new tickets.
- The account details in our CRM do not reach Zendesk.
- IT hears about a new colleague when they are already at the door.
- I print tickets one by one to build a case file.
- I download attachments from each ticket to collect the documents.
- Everything for Zendesk