Restaurant call forwarding: a setup and test checklist

Before you forward your restaurant's phone, write down two destinations: where a guest's first call should go, and where a request for staff should go. Test both from an outside phone. A greeting that sounds right does not tell you whether the caller can reach the host stand.

This checklist is for an operator connecting an answering service or AI phone agent to an existing restaurant line. Use it with the person who manages your phone account. It covers routing and a return to your prior setup; use our phone-ordering trial checklist to test the order itself.

Which calls should you forward?

Choose the rule before asking for an activation code. Forwarding all calls, forwarding an unanswered call, and forwarding a busy line are different settings. AT&T's Phone for Business instructions describe each separately, plus a forwarding option for outages. Availability depends on the service on your account.

• All incoming calls: choose this when the answering service should receive the first request. Test the separate route to staff.
• No answer: choose this when staff should have the first chance to pick up. Agree on the delay and test whether voicemail answers before forwarding starts.
• Busy line: choose this when the service should receive a call that arrives while the line is in use. Test it with one call already connected.
• Outage routing: ask which failures your provider detects and where it sends calls. Do not assume an unanswered call and an unreachable phone trigger the same rule.

A rule that works on one account may need different steps on another. Verizon's traditional business phone guide, for example, distinguishes fixed and variable forwarding destinations, with availability varying by area. Get the instructions for your exact service rather than copying a star code from a general article.

Fill in this routing record before making a change

Keep the completed record with the shift manager. Use full phone numbers in your private copy; this example uses labels.

• Public restaurant number: the number a guest sees on your site and listings.
• Provider and service: the account, line type, and authorized person who can change it.
• Forwarding rule: all calls, no answer, busy, or a supported scheduled rule.
• Answering destination: the confirmed number supplied for this restaurant.
• Staff destination: a number or extension that reaches the right team without sending the call straight back to the answering service.
• Unanswered staff call: the agreed next step, such as a message or another staffed destination, if your services support it.
• Return procedure: the provider's exact deactivation steps, previous settings, and who can restore them.

Test the guest's whole path

Run these checks during a quiet period with staff ready to answer. Use an outside phone and record what actually happens, including the time spent ringing. Do not count a test as passed just because the settings screen says forwarding is on.

1. Normal call: dial the public number. Check the restaurant name, location, greeting, and the point at which the answering service picks up.
2. Ask for staff: request a person. Confirm which handset rings and whether a staff member can speak to the caller.
3. Staff do not answer: repeat with the receiving team ready to observe, but not pick up. Record the final destination and message. Check that the call does not loop back through the same greeting.
4. Busy and no-answer rules: test each enabled rule separately. Keep a second line or colleague available so you can create the intended condition.
5. Closed hours: use a supported test configuration to check the closed-hours path. Confirm what the guest hears and whether a transfer is appropriate.
6. Return to the prior setup: have the account owner restore the saved settings, then call the public number again. Confirm the original destination before ending the test.

If a check fails, record the dialed number, intended destination, time, and observed result for your provider. Avoid repeatedly changing several settings at once; you need to know which change fixed the path.

Check the bill and the handoff before launch

Ask your phone provider about forwarding charges and ask the answering vendor about its own fees. Verizon notes that forwarding to a long-distance number can incur long-distance charges. A flat answering-service price does not establish the carrier's charges.

Give the manager a clear stop condition: for example, a staff transfer reaches the wrong place or a caller gets stuck in a loop. Name who can restore the previous routing. Do not cancel the existing phone service as part of a forwarding test; discuss any separate number transfer with the providers responsible for it.

For Maple, Voice covers answering and call transfer; Pro adds ordering and reservations. Bring your completed routing record to a Maple demo and confirm the supported setup for your line.

Published by Maple. This AI-assisted guide combines linked carrier instructions with an original routing and test worksheet. It does not report a carrier test or promise compatibility with every phone service.