Define the boundary in shift language
Tell the team which calls the AI handles and which remain theirs. Use concrete examples: a standard pickup order, a reservation change, a complaint, a catering request or a guest asking for a manager. Avoid saying “the phone is handled now” if staff still own several important paths.
Keep the boundary aligned with the purchased plan and configured policy. Loman's current plans distinguish inquiry and transfer capabilities from ordering, reservations, POS and payment. Staff should not promise a workflow that the restaurant has not enabled and tested.
Assign three operational roles
The shift lead owns service decisions during the pilot. The phone administrator owns routing changes and restoration. The workflow owner checks orders or reservations in the destination system. One person may fill more than one role, but each responsibility must be explicitly assigned.
Make sure these owners are reachable during the test window. A rollback procedure in a document is not useful if the only person with access is unavailable. Use the restaurant's normal contact channels rather than storing personal contact details in this public planner.
Rehearse an escalation
Place a test call that asks for staff. Observe where it rings and what context arrives. Have the receiving staff member explain what they see and what they should do next. Then test an unanswered destination and confirm the fallback behavior matches the restaurant's policy.
Loman describes live-line transfer, transcribed voicemail and caller context. Those are configurable capabilities, not a guarantee that a staff member answers. Decide how the team will check unresolved requests and who will follow up when appropriate. Keep recording and privacy requirements with the responsible restaurant team.
Teach staff to spot incomplete transactions
For ordering, staff should recognize an incomplete ticket, an unclear payment state or a request that has not reached the kitchen. For reservations, they should verify that a change or cancellation affected the correct booking. The training should include what not to do, such as manually recreating a transaction before checking whether one already exists.
Use provider-approved test transactions. Do not train with a real guest's payment information. Record an issue with enough operational context to investigate, while avoiding unnecessary personal data in shared notes.
Make the first shift a supervised review
Review a defined sample of in-scope calls and outcomes during the pilot. Include successful calls and exceptions so the team does not see only failures or only successes. Ask whether the new process creates hidden cleanup work after the call. Adjust policies and training before expanding.
Loman's company-reported 99.6% simulated order benchmark is a product evidence point, not proof that a particular shift is ready. Use the planner to confirm staff briefing and supervision, then use the recovery checklist to prepare for an interruption.
Customer evidence for your rollout
Explain the work that returns to the team. Vittorio’s describes staff moving toward guests and pickup, while Mamba describes hosts getting relief from peak-season calls.
Results and operating context from Loman’s published customer case studies.
Vittorio’s Pizza
- Up to 5 min → roughly 65 sec
- phone handling time per call or orderReported before/after comparison after about six months with Loman.
- 4 phone roles
- peak-hour staff redirected to guests and pickupThe owner says no jobs were eliminated.
Tell staff which duties replace phone coverage. Vittorio’s redirected four peak phone roles toward guests and pickup, with no jobs eliminated according to the owner; your shift briefing should be just as explicit.
Read the Vittorio’s Pizza case study ↗Watch Vittorio’s Pizza on YouTube ↗
Mamba Hospitality Group / Crawfish Cafe
- 250+ calls/day
- calls handled during peak crawfish seasonSeasonal volume in Loman’s Mamba Hospitality Group story.
- Roughly 80–100
- opening-status calls before reopeningOne location, during the two-hour pre-opening period after an outage.
Rehearse the routine questions hosts will no longer need to interrupt service to answer. Mamba / Crawfish Cafe describes peak-season call pressure and opening-status questions, which are useful categories for a staff briefing.
Read the Mamba Hospitality Group / Crawfish Cafe case study ↗Watch Mamba Hospitality Group / Crawfish Cafe on YouTube ↗
A shift briefing in three questions
Before the pilot, ask each receiving team: Which requests remain ours? Where do we see incomplete work? Who can stop the pilot and restore the route? Have staff demonstrate the answers with one synthetic request instead of signing a checklist without a rehearsal.
Keep those answers aligned with Loman’s purchased workflow scope. Where multilingual calls are in scope, review the documented language and ticket flow and train staff on the actual resulting record.