Restaurant holiday hours: a phone and ordering checklist

Before a holiday, check more than the closing time on your door. A guest can see one time on Google, hear another on the phone, and find a third in the ordering checkout. Start with one approved record for each location, then verify what each guest-facing system actually says and accepts.

This checklist is for a manager preparing a temporary closure, an early close, or special service hours. It covers the change and the return to normal hours. For choosing the right store during a call, use the separate multi-location routing worksheet.

Write down the hours for each service

Ask the location manager to approve the schedule before anyone changes a setting. Record the date and local timezone, including the next calendar date when a service crosses midnight. Keep these fields together:

• Location: store name, address, public phone number, and local approver.
• Dining hours: when guests can arrive and when the dining room closes.
• Order acceptance: the last time you will accept a new pickup or delivery order.
• Fulfillment: the last pickup or delivery time the kitchen can support.
• Advance orders: whether guests can order for a later date while the restaurant is closed.
• Phone response: the approved answer to questions about today, tomorrow, and the next opening.
• Staff help: who, if anyone, can receive a transferred call during the closure.
• Return to normal: the date, time, owner, and check that will confirm the usual schedule is back.

As a hypothetical example, a restaurant might close its dining room at 8 p.m., stop new pickup orders at 7:15 p.m., and permit collection until 7:45 p.m. Those are three different rules. Have the manager choose the actual times; do not calculate the order cutoff from the dining-room hours alone.

Update the places guests check

Use a small change log with one row for each system: approved value, person responsible, saved time, public check, and remaining issue. Include the website, search listing, phone system, direct ordering page, and each delivery service you use. A saved setting is only one step; read the guest-facing result too.

Google's Special hours guidance covers short exceptions without changing the regular schedule. It recommends confirming official-holiday hours even when they stay the same. The guidance also distinguishes service-specific hours and longer closures. Choose the appropriate setting for your situation, then check the public profile.

For Toast Online Ordering, the takeout and delivery schedule guide describes date-specific overrides, order cutoffs, and separate settings by dining option. It also warns that third-party services request schedule updates on their own timing. Check each ordering destination instead of assuming that a saved Toast change has reached every service.

Those instructions describe Google listings and Toast online ordering. They do not establish how your phone agent receives hours. Ask the phone provider which setting controls its answers, whether someone must publish the change, and how to confirm the effective schedule.

Test the boundaries, not just the middle of the day

Agree on a test setup with your provider and restaurant manager. Use clearly identified test orders if order submission is needed, and avoid sending unexplained tickets to the kitchen. Check the following paths against the approved record:

1. Before opening: ask when this location opens and whether an order can be placed now or only scheduled for later.
2. Before the last-order cutoff: check the offered pickup time against the kitchen's last supported fulfillment time.
3. After the cutoff but before closing: verify the distinction between being open and still accepting new orders.
4. On the closed date: ask about today and the next opening. Check that a transfer does not lead to an unstaffed destination without the agreed fallback.
5. Across midnight: use actual dates in the test notes so “tomorrow” has an agreed meaning.
6. After reopening: confirm that the usual answers, ordering slots, and staff route are back.

If you cannot simulate a time boundary, mark it untested and assign an observation at that time. Do not turn a passed midday call into a claim that every holiday path works. Record what the guest heard, what the ordering page offered, and what reached staff separately.

Check existing reservations and advance orders separately

A new schedule does not tell you what happened to commitments already made. Have a manager review the reservations, scheduled orders, and pickup promises that overlap the changed hours. Decide who will handle each conflict through the restaurant's normal process before relying on the new phone answer.

For a group with several restaurants, complete a separate record for each location. Test two stores with different holiday hours to catch an answer copied from the wrong site. Keep customer details out of a shared test worksheet; use approved test records where possible.

Close the change only after the public checks pass

Keep unresolved differences visible: which system is wrong, the correct value, who owns the fix, and when to recheck it. After the holiday, verify the return to normal hours and retain the record for the next exception. For the line routing itself, use the call-forwarding checklist.

If you are evaluating Maple, bring the hours record to a demo. Voice covers answering and FAQs; Pro adds phone ordering and supported integrations. Confirm the update process for your setup and test the call-to-kitchen workflow on the phone-ordering product page.

Published by Maple. This AI-assisted guide combines linked Google and Toast documentation with an original change record and proposed tests. The example hours are hypothetical; this page does not report a customer trial or promise automatic schedule synchronization.