Plan restaurant phone voice ordering

Map your line before forwarding it

Write down the number guests dial, the carrier or phone provider, the locations behind that number and the destination for staff assistance. Check whether forwarding is unconditional, busy-only or no-answer. Ask what happens when the forwarding destination cannot be reached. Test the real public number, not only a demonstration line.

An overflow pilot can be easier to observe than an immediate full cutover. Keep the current configuration recorded so an authorized person can restore it. Set a check-in at the start of each pilot shift and verify the staff destination is staffed rather than silently reaching an empty handset.

The caller cannot inspect your screen

Prompts should expose the choices needed to finish the order without reading the whole menu. For a sandwich, that might mean size, bread and required sides before optional extras. A final readback should distinguish the confirmed order from information still being collected.

Give callers time to correct themselves. “Actually make that two” is a change to the active order, not a fresh order. If a guest changes the pickup time, explain any effect on availability or preparation rather than carrying an outdated assumption forward.

Define the hard edges

• Service hours: distinguish answering the phone from accepting orders for an open kitchen.
• Delivery: confirm service area, minimums and dispatch responsibilities.
• Payment: use the configured approved workflow and confirm a failure path.
• Allergens: do not infer safe preparation from a menu description. Route uncertainty to trained staff.
• Reservations: treat bookings as a separate workflow from kitchen tickets.

What to verify with Loman

Loman documents 24/7 restaurant phone answering and 55-language support. Current plan information places ordering, reservations, POS integration and payment in Premium. Confirm the specific plan and system before your pilot, rather than assuming every feature is included in every package.

Our recommendation covers the phone channel. Carry your real menu, forwarding rules and handoff destination into the fit check. Use the channel planner to record unresolved requirements.

A phone-order test you can inspect

Illustrative test, not a customer result: create a fictional two-item pickup order, change one modifier and request a different collection time before confirming.

Expected record: one order at the correct location, with the corrected quantity and modifier, an accepted collection time and an explicit payment status. The kitchen ticket and the spoken confirmation must describe the same order.

Failure check: interrupt the downstream connection. The caller must hear the truthful order status; staff must know whether anything needs recovery. Inspect for a duplicate before retrying.