AI voice, done with restraint
What good AI voice sounds like, and where it stops so a human can take over.
Sunday Okoi
Operator & commercial, SavorQ
4 June 2026
The goal is not a chatty robot
Restaurants do not need a personality contest on the phone line. They need missed demand captured, orders structured correctly, and awkward cases handed to a person without embarrassment.
Restraint is the design principle. Answer quickly. Ask only what the ticket needs. Confirm clearly. Escalate early when confidence drops.
Where AI voice should stop
Complex complaints, sensitive allergy judgement calls, large events, and anything that requires discretion should move to a human. The product earns trust by knowing its limits, not by improvising through them.
Operators should define the stop conditions in advance: low confidence, prohibited topics, VIP flags, or kitchen saturation that means new orders should wait.
Judge it like an operator, not a demo
A polished demo call proves little. Production proof looks like capture rate, ticket accuracy, handoff quality, and whether FOH still trusts the queue when it is busy.
If AI voice creates cleaner tickets and fewer missed peaks without turning guests into support cases, it belongs in the operating layer. If it mainly sounds clever, it does not.
