Schedules · Documentation-based procedure

Route out-of-hours calls on holidays and special dates

Content updated:

Short answer

Configure phone availability using regular hours, exceptions, holidays and a genuine closed-hours route. In Spain, load the national and regional holidays from the annual BOE resolution and the two local holidays of each team's municipality. In Aircall and CloudTalk, confirm which rule takes priority for each number and use greetings that describe the service actually available.

Key verification: Test schedule boundaries and exception dates in the correct time zone.

Sources and limitations

Set up the regular schedule first, then the date exceptions, and finally the closed-hours route. The phone system must know what to do at every moment, including local holidays, annual leave and team breaks. A calendar without an exit destination can send calls down an empty route.

A number's hours do not always match those of the team that answers it. A landline from one city may be answered from another region or time zone; what matters for routing is the cover you have arranged and published, and the public holidays that apply where each team works. For outbound calls to other countries, the time that matters is the recipient's: the guide to scheduling calls by the recipient's local time explains how to allow for it.

Prepare an operational calendar

Route out-of-hours calls on holidays and special dates: table 1
SituationRuleExample destination
Normal dayWeekly opening windowCustomer service team
Break without coverOutside the opening windowVoicemail with reopening message
Local holidayFull-day date exceptionClosure message or genuine on-call cover
Reduced hoursException with specific hoursService only during those hours
Annual leaveExceptional period and return reviewCovering team or alternative channel

Decide who reviews the calendar and who confirms cover. An on-call route drawn in the editor is useless unless someone has agreed to take it. Also set a review date to remove expired exceptions.

Public holidays in Spain: three levels and where to find them

Spain has at most fourteen public holidays a year: the national and regional ones, which the Directorate-General for Labour publishes in the BOE (the official state gazette) every autumn, and up to two local holidays for each municipality, published in the regional or provincial official bulletin. This is set out in the Resolution of 8 October 2026 listing the 2027 public holidays, published in the BOE on 13 October 2026, which refers to article 37.2 of the Workers' Statute and Royal Decree 2001/1983.

Route out-of-hours calls on holidays and special dates: table 2
LevelWhere it is publishedWhat to load into the phone system
NationalAnnual BOE resolutionDates common to every site
RegionalAnnex to the same resolution, by regionDates for the region where each team works
LocalRegional or provincial bulletinTwo dates per municipality for each site

For 2027, the resolution sets nine holidays common to the whole country: 1 and 6 January, 26 March (Good Friday), 1 May, 12 October, 1 November, and 6, 8 and 25 December. The rest depend on each region: for example, Maundy Thursday (25 March) is a holiday in Aragon but not in Catalonia. For the rest of 2026, the 2026 holiday resolution includes 8 and 25 December as common holidays.

Neither Aircall nor CloudTalk loads Spanish regional and local holidays for you, as explained below. Copy the dates from the official source, not from a third-party calendar, and keep the link on the calendar record.

Example: one queue answered from two regions

An invented company answers a single number with one team in Zaragoza and another in Barcelona. According to the 2027 resolution, these dates are holidays in only one of the two regions:

Route out-of-hours calls on holidays and special dates: table 3
Date in 2027HolidayZaragozaBarcelonaPlanned route
25 MarchMaundy ThursdayClosedOpenBarcelona team only
29 MarchEaster MondayOpenClosedZaragoza team only
23 AprilSt George's Day, Aragon DayClosedOpenBarcelona team only
24 JuneSt John's DayOpenClosedZaragoza team only
16 AugustMonday after the AssumptionClosedOpenBarcelona team only
11 SeptemberNational Day of CataloniaOpenClosedZaragoza team only

On top of these six dates come each city's two local holidays, which must be taken from its bulletin. A company-wide closure rule would be wrong on these days: there is cover, but only half the team. Check whether that half can handle the expected demand or whether a message warning of longer waits is needed.

Aircall: keep regular hours and special dates separate

The Time Rule widget defines time slots and the time zone; calls outside them follow its alternative branch. Aircall explains these fields in its Time Rule guide. Check the "At any other time" branch explicitly.

Special dates are handled with the Date Rule. Its special dates guide explains how to create them in Call Settings, as a full day or a time range, and link them to the number. A single special date can be shared across numbers and edited each year. The most common documented flow puts the date rule before the weekly rule so that the exception is evaluated first. See the combined set-up of opening hours and holidays.

After saving, publish the flow: Aircall states that unpublished changes are not active. A screen showing the correct schedule may be displaying an edit that is not yet live.

Order in which a calendar is evaluatedAn incoming call is first checked against special dates. If the date is a holiday or special date, it follows the holiday or reduced-hours route. If not, the weekly window is checked: inside the window the call goes to the service team; outside it goes to the closed-hours route with voicemail or an alternative channel. Incoming call 1. Special date or holiday? Yes Holiday route No 2. Inside the weekly window? Yes No Service team Closed route: voicemail or channel
The date exception is checked before the weekly schedule; if the order is reversed, a holiday falling on a weekday goes through the normal window. Every final destination must exist and be staffed or clearly announced.

CloudTalk: check which rule takes priority for each number

CloudTalk supports company hours and per-number hours. Number-specific hours replace the company-wide ones. Exceptions for a date replace that day's normal schedule; they do not simply remove a few hours from it. Its holiday calendars are national only and do not include regional holidays, which you must add as exceptions. In addition, a number has no time zone of its own: its hours are entered in the account's time zone, with daylight saving applied automatically. Source: CloudTalk business hours and exceptions, consulted on 27 October 2026.

So review every number that has its own rules. If you switch the company to summer hours, a number with individual settings may keep running on a different calendar. If a team works from the Canary Islands, convert its hours to the account's time zone before entering them.

Example: normal service runs from 9:00 to 18:00, and on one day there will only be cover from 10:00 to 12:00. Define and test that exception as a full day with reduced opening hours. Do not assume it will be added to the usual hours.

Write greetings that describe the service actually available

You have reached [company]. Our opening hours are [days and times, with time zone if needed]. Today, [date or reason], we have special hours. You can [leave a message or use the channel that is actually available].

Do not promise an immediate call back if the team returns several days later. A generic "we will be with you shortly" message may keep playing during holidays if it is not part of the correct branch.

Check that the dates and hours published on your website match what the caller hears. If there is an urgent channel, restrict that route to the cases the team can actually handle.

Test the calendar's boundaries

  1. A moment inside a normal time slot.
  2. A moment just before opening and just after closing.
  3. The break between two slots on the same day.
  4. A reduced-hours exception.
  5. A local holiday added manually.
  6. One number with individual hours and another on company hours.

Use simulation features if the provider offers them, or set up a controlled exception on a test number. Avoid changing the clock on a production device to test the calendar. Record the selected time zone and the result.

Voicemail: design the message you want to receive

Ask for a name, a way to call back and a brief reason. Do not request full card numbers, passwords or sensitive information. Explain a response time the team can meet and an alternative if the matter cannot wait. The greeting should be short and easy to follow over the phone.

Original example: "You've reached the quotes team. We can't take your call right now. Please leave your name, phone number and a line about the service you need. We review messages on the next working day. You can also write to us through the contact channel on our website." Adjust that commitment to your real schedule; do not copy it if you check the mailbox at a different frequency.

Voicemail: message handling sheet

Route out-of-hours calls on holidays and special dates: table 4
StateActionEvidence
ReceivedLog date, line and recipientMessage located, not just an email received
ReviewedSummarise the reason and next actionTask with a deadline
In progressReply through the agreed channelAttempt and result logged
ClosedConfirm resolution or impossibility of contactReason for closure and date

The state system is an operational proposal, not a function attributed to every provider. It can be kept in your task manager or CRM. A shared, unassigned mailbox often lets two people return the same message while another goes unhandled.

Missed calls: classify before calling back

Separate recoverable queries, test calls, obvious errors and unusable numbers. Check whether the customer called again and was already handled. The "missed" counter does not equal the number of people waiting for a callback.

Aircall distinguishes reasons such as IVR abandonment, no available agent and out-of-hours calls. These labels describe the technical path and help prioritise review, but they do not alone explain the customer's intent. See the documented missed-call reasons.

From a missed-call alert to closing the taskEvery missed call first goes through triage: recoverable, a test or obvious error, or an unusable number. Only recoverable ones create a task assigned to a person. After a callback attempt, the result is logged as contacted, no answer or wrong number. If contacted and the query was resolved, the task closes; if not, it returns to the queue with a new deadline instead of generating an uncontrolled attempt. Missed call Triage recoverable or not Test, error or invalid number Assign one person, one deadline Call back and log contacted or no answer Resolved: close the task Unresolved: new deadline, not a retry
A missed call only becomes a callback task if triage marks it recoverable; the outcome of each attempt decides whether the task closes or returns to the queue.

Missed calls: a minimal recovery sheet

Route out-of-hours calls on holidays and special dates: table 5
FieldWhat to record
ReferenceCall ID and a link to the internal record
Contact or queryVerified identity or "pending identification"
OwnerOne person, with a planned substitute
DeadlineDate and time compatible with coverage
Last attemptTiming and a verifiable result
StatusPending, in progress, contacted, resolved or closed with a reason

A shared sheet can cover a small volume. If you use a CRM, log the task on the matching record and keep the call reference. HubSpot lets you log activities and add follow-up; its activity guide details the available fields and the functions that require another plan.

Missed calls: a five-step procedure

  1. Review: discard test calls and check whether a later conversation already resolved the query.
  2. Assign: one person accepts the pending item before making the attempt.
  3. Call back: use the approved corporate number and the minimum context you already know.
  4. Record: note connected, no answer or wrong number; then add the business outcome.
  5. Close or reschedule: leave the next step and stop attempts once the query is resolved.

The callback should match the request and the contact's preferences. If you cannot identify the reason, avoid revealing information from another record that shares that number. Confirm who you are speaking to first.

Automatic or manual callback: decision table

Route out-of-hours calls on holidays and special dates: table 6
SituationRecommended mechanismWhat to watch
Low volume, wide service hoursManual, with the minimum recordThat no pending item is left without an owner
High volume, few available slotsAutomatic, with a window and a capped attempt countWhat happens when it reaches voicemail
Queries that need CRM context before callingManual, or automatic with a prior alert to the agentThat the agent has the record open before it rings
Campaign with customers already called several timesManual, after reviewing the history firstContact fatigue and complaints about persistence

If the service fails: a simple dependency map

Route out-of-hours calls on holidays and special dates: table 7
FailureAlternative to studyDependency that remains
Office internetAnother connection or device compatible with mobile dataProvider and coverage of that network
A computer or applicationAnother compatible device or accessTelephony service
Provider's phone systemAgreed operator route or an independent alternative numberOperator capacity and prior configuration
Main number unreachableChannel or number of another service published as an alternativeWhether the customer can find and use it

A mobile connection in the same office can fix local access, but not a provider outage. A second number contracted on the same platform can share the same incident. Note these dependencies rather than counting alternatives by name.

Each alternative keeps a different dependencyThree types of failure lead to different alternatives: an office internet outage is solved with another connection, a device failure with another computer, and a provider phone system outage with an operator route or an independent number. No alternative removes every dependency: each one still needs a provider, an operator or the customer to be able to use it, so the plan must check that dependency before relying on it. Office internet → another connection Device or app → another device Provider's phone system → operator route Each alternative keeps a dependency: check it before the incident
The three alternatives solve different failures, but none removes dependence on a third party entirely.

Continuity plan: rehearsal acceptance table

Route out-of-hours calls on holidays and special dates: table 8
Simulated conditionWhat should happenAcceptable if…
Local internet downTwo people switch to the alternative connectionBoth complete a test call in under five minutes
Provider dashboard unreachableThe route activates without editing live configurationThe procedure does not require opening the dashboard during the outage
Plan holder absentA backup with the same access activates the alternativeThe backup needs no extra authorisation from the holder
End of the rehearsalReturn to the normal route and a verification callThe final call goes through the usual path, with no diversion active

Common mistakes and how to spot them

  • Forgotten regional holiday. Symptom: unanswered calls on one particular working day. Check: compare the exceptions loaded with the BOE annex for the region of each site.
  • Local holidays for the wrong municipality. Symptom: closure in the city of the number's area code rather than the team's. Check: note each team's municipality and its bulletin on the calendar.
  • Unpublished exception. Symptom: the editor shows the date, but the call follows the normal route. Check: call from outside on the test date and review the publication status.
  • Per-number hours overriding company hours. Symptom: one number answers on a holiday the others observe. Check: list the numbers with their own hours after every company-level change.
  • Last year's dates. Symptom: Maundy Thursday or Easter Monday closed on another year's date. Check: review every movable date when the annual resolution is published.
  • Empty closed-hours route. Symptom: busy tone or a cut-off without a message. Check: test the out-of-hours branch with a real call.

Keep hours, on-call cover and advertising aligned

Schedule a review before holiday periods and whenever shifts or sites change, plus another every October, when the BOE publishes the following year's holidays. Decide who will review accumulated messages on return; any temporary set-up needs someone responsible for following it up.

The phone system organises where incoming calls go. If you also need to adjust when call-focused ads are shown, follow the Google Ads scheduling guide (in Spanish). If calls are already pending, use the call-back procedure described above.

From the author's experience

I would always assign the holiday calendar to a functional owner and leave the technical team to implement and test it; without a clear owner, a configuration that was correct when it was set up can be out of date by the next local holiday. In a multi-site rollout, I would always test each location's numbers and queues against its national, regional and municipal dates separately.

When cover depends on which site is open, I would set up independent calendars per route or queue and define an explicit rule for falling back to another open site, rather than duplicating the same schedule in many places in the flow. Facing a "no answer on holidays" issue, my first step would be to check the precedence between normal, special and exception rules, and to confirm which version of the flow is actually published, because a saved change that has not been activated does not change the real call path; after that I would check the time zone applied to the number, and finally run a simulation or a controlled call on the affected date.

In the holiday greeting I would always say when service will resume, whether there is any alternative cover and how to leave a request, avoiding any promise of an automatic call back unless a process actually guarantees it.

Sources and limitations

Documentary review: . Content type: Documentation-based procedure.

How to report a correction

Check current terms

Consider these options if they solve the problem described. Confirm features, limits and availability in your country.

AircallOfficial plans and termsCloudTalkOfficial plans and terms

Estos enlaces llevan a las páginas oficiales de cada proveedor. CallsIQ no usa enlaces de afiliación. Our commercial policy.

How this guide was prepared

Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.