Settingsbeginner

Configure holidays and date overrides

Pick a country to import the public holiday calendar automatically, then add date overrides for company-specific closures (or partial-day hours like Christmas Eve 8-noon). Holidays default to closed; you can override.

4 min read

Configure holidays and date overrides

Public holidays and one-off closures need to be reflected in your opening hours, otherwise SLA timers count through them and IVR flows route customers to a “we’re open” experience on Christmas Day. Atender handles this with two layers: a country-based holiday calendar (auto-imported), and per-date overrides (manually set).

Before you start

  • A working opening-hours rule (create one)
  • A list of company-specific closures or special hours (your office closes between Christmas and New Year, for instance, even though those aren’t all public holidays)

Holiday calendars and date overrides only make sense on a rule that also has explicit weekly open hours, unless the intent is for that rule to be closed. If you leave the weekly schedule empty while setting a holiday country or date overrides, Atender treats that as no regular open hours, so the rule is closed. For true 24/7 coverage, use the explicit Always open assignment, or an explicit always-open schedule/sentinel where your UI exposes one.

Step 1 — Pick a country or region/nation for the holiday calendar

Atender imports public holidays automatically based on the country code, or region/nation where offered, that you set on the rule.

  1. Open the rule in Settings → Opening Hours.
  2. Find the Holiday country (optional) field.
  3. Pick the country or region/nation whose public holidays apply to your team. Common options: United States, United Kingdom, Canada, Norway, Sweden, Germany, France, etc. For UK teams, choose England, Scotland, Wales, or Northern Ireland if the team observes that nation’s bank holidays; choosing United Kingdom keeps the legacy whole-UK calendar and does not include the August nation-specific bank holiday.
  4. Save.

Holidays from the selected country are now treated as closed — SLA timers pause, IVR routes after-hours, automation schedule restrictions evaluate as “outside hours.”

The holiday calendar updates as new years roll in. You don’t need to maintain a list yourself.

Multi-region teams

If your team operates in multiple countries (US team, EU team, UK team), use separate rules per region with different country codes. One rule per region, each with the appropriate holiday calendar. See multi-timezone hours.

Step 2 — Add date overrides for company-specific events

Date overrides handle anything that’s not a public holiday: company-only closures, half-days, special-event hours. An override can cover a single day or a continuous range of dates, and it can repeat every year.

For each:

  1. In the rule, find Date Overrides & Holidays.
  2. Click Add Override. The new override starts on the date shown on the date button next to it (today unless you pick another).
  3. Set the dates:
    Start date — the first (or only) day the override applies.
    to — optional end date for a range. The field shows the placeholder “Same day”; leave it that way for a single-day override, or click the X to remove an end date you no longer want.
    Repeat each year — turn this switch on if the override should apply on the same dates every year.
  4. Set the behavior:
    Closed — fully unavailable. Same effect as a holiday.
    Open — turn the switch off so it reads Open, then set the opening and closing times for the dates covered. Useful for Christmas Eve 08:00-12:00, Black Friday 06:00-22:00, etc.
  5. Save.

A range can span up to 366 days, or up to 365 days if it repeats each year.

Overlapping overrides

Two overrides you add can’t cover the same date in any year (an override on an imported holiday’s date is allowed). If you try to save an override that overlaps an existing one, Atender refuses it with a message naming both overrides. Adjust the dates of one of them, or remove one, and save again.

Ranges and imported holidays

Imported public holidays are not added inside a date range. On those dates, the range applies instead. For example, if your year-end shutdown override covers 24 Dec – 1 Jan and the calendar also includes 25 Dec, 26 Dec, and 1 Jan, the shutdown override’s behavior is what takes effect on those days.

Override an imported holiday

Some teams want to operate on certain public holidays (a 24/7 critical-issue team, say). To override an imported holiday with custom behavior:

  1. Add a date override for the same date as the holiday.
  2. Turn the override’s switch to Open and set its hours (your regular hours if you’re operating normally).
  3. Turn on Repeat each year if you want the same behavior every year.
  4. Save.

The override takes precedence over the imported holiday for that date. Without Repeat each year, next year’s holiday will need its own override.

Step 3 — Verify

  1. After saving, open a conversation that should be affected (e.g., on a holiday date).
  2. Check the SLA badge — it should say “paused” or remain at its last value rather than counting down.
  3. Check any automation that uses schedule restrictions — it should behave as if the workspace is closed on the holiday.
  4. For voice channels: test an IVR flow’s Is Open node — the call should route to the after-hours branch.

Common patterns

  • Standard public holidays — Set country code; nothing else needed
  • Company-only closures (year-end shutdown) — One date override marked Closed covering the range, such as “24 Dec – 1 Jan, every year”
  • Half-day Christmas Eve — Date override with custom hours 08:00-12:00
  • Black Friday / extended hours — Date override with custom hours 06:00-22:00
  • Operating on holidays — Date override with custom hours matching your normal day
  • Different holiday calendars per team — One rule per team-region pair, each with appropriate country code

Maintenance

A few practices that prevent the calendar from drifting:

  • Annual review. Once a year (typically December), review your company-specific closures. Closures that recur on the same dates are covered by Repeat each year, so you only need to add new overrides for one-off closures or dates that have changed.
  • Don’t override imported holidays unnecessarily. If a holiday should be closed, the country calendar already handles it. Adding a redundant override creates clutter.
  • Use descriptive override names. 2026-12-24 Christmas Eve half-day is more useful than just the date alone.

Troubleshooting

  • Symptom: Public holidays aren’t being recognized. Fix: Check the country code on the rule. Common mistake: setting it to the team’s location (US) when your holiday calendar should be the country (Canada). For UK teams, also check whether the rule should use England, Scotland, Wales, or Northern Ireland instead of the legacy United Kingdom calendar.
  • Symptom: A specific date should be closed but the timer is counting. Fix: That date isn’t a public holiday in the imported calendar. Add a date override marked Closed.
  • Symptom: Override applies on the wrong day. Fix: Timezone mismatch. The override date is interpreted in the rule’s timezone — verify it matches.
  • Symptom: Atender refuses to save an override. Fix: Another override already covers one of the dates. The message names both overrides; change the dates of one or remove it.

See also

Tags

How To