Switch restaurant answering services: a number and handoff checklist

Before switching your restaurant's answering service, find out who controls the number your guests dial. Changing the destination of a forwarded call and moving that number to another carrier are different jobs. Put the number, account owner, and planned change in writing before setting a launch date.

This guide helps an operator prepare a vendor handoff. It does not assume that your new answering provider needs to take over the number. First ask whether the new service can work with the phone account you already have.

Are you changing the answering destination or the carrier?

With forwarding, your phone service routes an incoming call to another destination. AT&T's Phone for Business guide distinguishes all-call, busy, and no-answer forwarding. The available rules depend on the service. Use our forwarding setup and test checklist once you know which rule applies.

Porting moves the number between providers. Twilio's porting guide, for example, says that Twilio becomes the carrier when a number ports to it. That is a separate process from sending calls to an answering destination. Ask the receiving carrier to confirm whether your number is eligible before committing to that route.

If the old answering vendor supplied your public number, ask who holds its carrier account and who may authorize a transfer. If your restaurant holds the number and forwards calls to the vendor, ask whether changing the forwarding destination is enough. Record the answer rather than assuming all answering services use the same setup.

Build a handoff record

Give the manager and the person making the change one shared record. Keep account numbers and transfer credentials in your secure account system, not in a public worksheet.

• Public number and location: which number guests dial and which restaurant it serves.
• Account control: current carrier, account holder, authorized contact, and whether the answering vendor holds the account.
• Change type: forwarding destination, carrier transfer, or another provider-approved setup.
• Current and new service: what each answers, where staff transfers go, and who handles an open guest request during the change.
• Records to retain: approved greetings, hours, menu rules, unresolved requests, and any reports your team is allowed to export.
• Timing and support: the agreed change window, receiving-provider contact, and staff member watching the first calls.
• Failure plan: who can restore routing or arrange temporary coverage, what triggers that step, and how staff will learn it happened.
• Old account closure: who checks completion, remaining services, notice terms, and the final bill.

For a US number port, Twilio's published requirements include authorization, matching account name and address, a recent phone bill, an account number, and a PIN when required. Those are Twilio's requirements; obtain the exact list from your receiving carrier. A mismatch can delay the move, so confirm the service record rather than relying only on the restaurant's current mailing address.

Test the new answering service before moving guest traffic

Ask for a supported test number or test setup. Give both teams the same restaurant facts and define what a successful call means. A test of the new service does not prove that the public number has moved.

1. Ask about hours and location. Check the answer against the manager's approved information.
2. Ask for a person. Confirm the destination, then repeat with staff unable to answer and observe the fallback.
3. If ordering is included, place an agreed test order and inspect what reaches the restaurant. Confirm how to keep test tickets out of normal production.
4. If reservations are included, test that workflow separately and distinguish a request from a confirmed booking.
5. Raise a request the new service should hand to staff. Check who receives it and how an unresolved request is tracked.

Use the restaurant voice AI demo checklist for order and reservation tests. Keep a short list of failures, their owners, and the checks that must pass before the switch.

Confirm the public number after the change

During the agreed window, have staff and the provider available. Call the public number from outside the restaurant. Check the greeting, the intended service, a staff transfer, and the final destination when staff cannot answer. Record the time and result. For several locations, use the paired-location routing checks so a working call does not hide a wrong-store destination.

If your number also receives texts or serves another business system, list those uses in the handoff and confirm them separately. Do not infer that one successful voice call proves every service works. Ask the provider what recovery is possible after a port; restoring a forwarding rule and reversing a completed carrier transfer are not the same operation.

When should you end the old service?

Agree on this with the providers before the change. AT&T's business wireless transfer instructions explicitly tell customers not to cancel existing service before the transfer and activation. That instruction is specific to its process; confirm the sequence for your line and receiving carrier.

After the agreed checks pass, review what remains on the old account before closing it. Ask about other numbers, bundled services, retained records, notice periods, and final charges. Put a named person in charge of each unfinished item. Avoid promising guests or staff a switch date that the receiving provider has not confirmed.

For Maple, Voice covers answering and call transfer; Pro adds ordering and reservations. Bring your number and handoff record to a Maple demo to confirm the scope for your restaurant.

Published by Maple. This AI-assisted guide combines linked provider instructions with an original handoff worksheet. It does not report a completed number transfer or promise that every number or phone service is supported.