Teaching your AI receptionist your business hours, holidays, and after-hours rules

An AI receptionist that does not know your hours will offer a caller a Tuesday 9:00 a.m. appointment when your shop opens at 10:00, and it will cheerfully take a booking request at 3:00 a.m. on Christmas morning. Business hours, holidays, and after-hours rules are the settings that keep the AI’s promises aligned with reality. They are also the settings most businesses configure once, badly, and never revisit.

This guide walks through setting up your hours correctly, handling holidays and special schedules, and defining what happens when someone calls outside those hours. Get this right and every caller gets an answer that matches what your business actually does.

Start with your real hours, not your posted hours

Most businesses have two sets of hours: the ones on the website and the ones they actually keep. The website says 9 to 5. In reality, the last appointment is at 4:00, the phones go quiet at 4:30, and Friday afternoons are a ghost town. Configure the AI with the real hours. The AI books appointments and sets expectations, so it needs the schedule your team actually works, not the aspirational one on your Google profile.

Enter hours per day, not as a single range. Tuesday might run 9 to 6 while Wednesday runs 9 to 3. Lunch closures matter too. If nobody answers the phones from noon to 1:00, the AI should know that, because a caller transferred during lunch will hit voicemail and wonder what happened. Day-by-day hours take five minutes to enter and prevent a whole category of confusion.

Define what after-hours calls get

After-hours handling is a business decision before it is a technical setting. You have a few options, and the right one depends on your business. Booking-only mode lets the AI schedule appointments but not transfer calls, which suits businesses where after-hours callers mostly want to book. Message-taking mode has the AI collect the caller’s details and reason for calling, promising a callback. Emergency triage mode asks screening questions and transfers truly urgent calls to whoever is on call.

Pick one primary mode and configure it fully rather than half-configuring two. A common setup for service businesses is booking plus emergency triage: the AI books routine appointments and screens for emergencies, transferring only genuine urgencies. For retail or office businesses, message-taking is usually enough.

Whatever you choose, the AI’s after-hours greeting should state the situation plainly. “You’ve reached us after hours” is honest and sets the right expectation. An AI that pretends it is 2:00 p.m. when it is 2:00 a.m. confuses callers and erodes trust when they figure it out.

Handle holidays and special days explicitly

Holidays are where hour configurations break down, because they are exceptions to the weekly pattern. Most AI receptionist platforms have a holiday calendar where you enter specific dates with their own hours or a closed status. Enter your full holiday list for the year in one sitting. Thanksgiving, Christmas Eve, New Year’s Day, and whatever else your business observes. If you wait until the week of the holiday, you will forget, and the AI will book appointments for a day nobody works.

Special days need the same treatment. Early-closure days, staff training days, inventory days, the day after your busiest season ends. Any day the schedule differs from normal should be an explicit entry. The weekly hours are the default; the holiday calendar is the override. Both need to be right.

Check whether your platform lets you set holiday hours in advance for the whole year or only a few months out. If it limits how far ahead you can schedule exceptions, put a recurring reminder on your own calendar to extend them. A holiday list that expired in March will not save you in December.

Time zones and multi-location setups

If your callers span time zones, set a home time zone for the business and have the AI confirm times with the zone attached. “Thursday at 10:00 a.m. Eastern” leaves no room for confusion. Some platforms detect the caller’s time zone from their number and translate; if yours does, verify it with a test call from a number in a different zone before trusting it.

Multi-location businesses need per-location hours. Each location gets its own schedule, its own holiday list, and its own after-hours rules, because the downtown office and the suburban branch rarely keep identical hours. The AI needs to know which location the caller wants before it applies the schedule, so the location question should come early in the call flow.

Review the schedule quarterly

Hours change. Summer hours differ from winter hours. You add a Saturday shift, drop the late Thursday, start closing for lunch. Every change needs to reach the AI’s configuration the same day it takes effect, or callers start getting wrong information. Make the AI’s schedule part of your operational checklist: when hours change on the door and the website, they change in the AI dashboard too.

A quarterly review catches the drift. Open the hours configuration, read it against reality, fix what diverged, and extend the holiday calendar. Fifteen minutes, four times a year, prevents the slow rot where the AI’s answers gradually stop matching your business.

Hours configuration pairs naturally with a coverage plan for the days you are closed. The holiday and PTO coverage guide covers the strategy side, and the business-hours versus after-hours rules post goes deeper on what each mode should do. For urgent calls that arrive outside hours, make sure your emergency triage screening is set up before you need it.