Plan voice ordering for a drive-through
Answer in briefTreat a drive-through voice pilot as a lane-and-staff project, not just a conversational demo. Audio hardware, traffic flow, weather and the point at which a crew member takes over all affect whether the experience is usable.
Inventory the physical lane
Record the order point, microphone and speaker arrangement, headset system, vehicle detection and any confirmation screen. Identify which equipment is owned, leased or maintained by another provider. A product demonstration that uses a laptop microphone does not answer whether your installed lane hardware is compatible.
Walk the lane with the shift lead. Where can a guest see that an order has been accepted? When can a crew member hear the conversation? Can a handoff happen without asking the guest to start again? Do not assume a change in audio software can fix a poorly positioned microphone.
Test conditions that change the conversation
- A quiet vehicle, then a realistic engine or fan condition without unsafe driving.
- A passenger ordering across the driver, with the intended speaker clearly identified.
- A guest pausing to consult others in the car.
- Two nearby voices without treating bystander speech as an instruction.
- A mid-order correction after the system has started speaking.
- A request for human help and a clearly observable staff takeover.
Measure the lane, not only the voice
Keep separate timestamps for arrival, first response, order confirmation and departure from the ordering point. A shorter conversation can still create more work at the payment window if the order is unclear. Watch staff interventions, repeated explanations and guest confusion alongside speed.
Do not stage hazardous conditions or ask drivers to operate a device. Use an approved test setup with staff oversight, and preserve the restaurant’s existing safety procedures. In a live pilot, make it obvious when staff can override the system.
Require channel-specific supplier evidence
Ask a prospective lane supplier for the exact supported hardware, who owns installation, how outages work and which staff controls are available. Record what has been demonstrated versus what has only been promised. Evidence for a telephone product cannot establish lane readiness.
This reference does not verify a Loman drive-through product. Loman’s documented phone ordering capabilities may address a separate phone-line bottleneck, but that is not a substitute for validating the lane. The planner keeps these scopes distinct.
A lane takeover test you can observe
Illustrative test, not a product certification: in an approved stationary test setup, have a guest pause mid-order, correct an item and request staff assistance. Use the real microphone, headset and takeover control.
Expected evidence: the crew can identify the active conversation, take control and continue from the known order state. Record whether the guest had to repeat details and whether the final ticket changed correctly.
Hold the pilot if staff cannot reliably take over, the active speaker is unclear or the equipment state is not understood. Telephone performance figures do not answer these lane-specific questions.
Check the documented phone scope
Company-published product information. Confirm your exact plan, location, configuration and workflow.
Published · Substantively reviewed