Turn restaurant calls into accurate orders
APEX VoiceOrder is being built to answer your eligible phone calls, take pickup orders across complex menus, validate items and modifiers, confirm the total with a read-back, and escalate to your team when a call needs a human — producing a structured order you can trust. It's in active development, and this site is an illustrative preview.
- Answer eligible calls
- Validate every item & modifier
- Read the order back
- Hand off to your staff
Built to reduce missed orders and staff interruptions — measured by accepted orders, not just answered calls.
Sample pickup call
Sample call · connecting…
Items appear here as they are confirmed and validated.
Designed around the outcomes restaurants actually feel
Accepted orders
the metric that matters
Validated items & modifiers
before the order is placed
Clean human handoff
when a call needs a person
Fewer missed calls
during the dinner rush
From a ringing phone to a validated order — in one call
The flow we're building: a clear, repeatable path your staff can trust. No app for the caller, no change to how your customers already order.
Answer eligible calls
During your defined hours, VoiceOrder picks up eligible pickup calls so the phone stops pulling staff off the line — and callers stop hitting a busy tone.
Understand & clarify
It follows the conversation naturally — dish names, spice levels, modifiers, substitutions — and asks a quick clarifying question when something is ambiguous.
Validate & confirm
Every item and modifier is checked against your menu and rules. Prices and totals are calculated by Apex services, then read back to the caller for confirmation.
Deliver the order
The confirmed order reaches your team as a dashboard entry, email, SMS, or printable ticket where supported — with a full call and order record behind it.
The phone is still where orders are won and lost
VoiceOrder is built for the specific ways restaurant phone ordering breaks down — and gives you a record when it does.
Calls go unanswered at the worst time
The rush hits, the phone rings out, and pickup orders — and regulars — quietly go to the restaurant down the street.
The phone pulls staff off the floor
Someone stops mid-task to take an order by hand, and the line, the counter, or the kitchen waits.
Orders come through wrong
A missed modifier or a misheard dish turns into a remake, a refund, and a customer who doesn't call back.
After-hours and overflow calls vanish
Calls outside staffed hours or during a spike leave no record — you never even know what you missed.
Totals get fudged over the phone
Prices quoted from memory drift from the real menu, and the numbers don't reconcile at pickup.
No evidence of what actually happened
When something goes wrong on a call, there's nothing to review — just a he-said-she-said.
The voice is conversational. The numbers are not up for interpretation.
A voice model is great at conversation — and the wrong place to invent a price. VoiceOrder draws a hard line between the two.
Voice model
Handles the conversation
- Understanding the caller
- Natural, conversational phrasing
- Intent extraction & clarification
- Recovery when a call gets messy
Apex services
Own the facts
- Prices, taxes, fees & discounts
- Order totals
- Item & modifier availability
- Payment status & order acceptance
The model is never allowed to invent these values. If a fact isn't confirmed by an Apex service, the order doesn't move forward — it clarifies or hands off instead.
Escalation
Handoff, not hang-up
- The caller asks for something outside the menu or rules
- A large, catering-style, or unusual order
- Repeated confusion or a frustrated caller
- Anything the system isn't confident it can complete correctly
A person is always the safety net
VoiceOrder is not a black box that either works or fails silently. When a call needs a human, it says so and transfers — you stay in control of the hard calls.
You decide the guardrails: hours, which calls are eligible, when to escalate, and how orders reach your team. It runs with your rules — not around them.
Designed to show every call and order — with the evidence behind it
The operational view VoiceOrder is designed around: what came in, what was accepted, what was handed off, and the record you can review when you need it.
38
Calls answered
29
Orders accepted
4
Handed off
1m 52s
Avg. handle time
Orders by hour
- $26.90Accepted
#1042 · Chicken Biryani +1
6:14 PM
- $41.20Accepted
#1041 · Lamb Karahi +2
6:09 PM
- $14.50In kitchen
#1040 · Veg Thali
6:02 PM
- —Handed off
#1039 · Catering inquiry
5:58 PM
Control, evidence, and honest status — by default
Serious restaurant technology has to be accountable. VoiceOrder is built to be inspected, bounded, and truthful about what it did.
You set the guardrails
Approved number, menu, hours, eligible calls, escalation rules, and how orders are delivered.
Deterministic by design
Prices, totals, availability, and acceptance are owned by Apex services — never invented on a call.
Call & order records
Every interaction leaves a reviewable record, so you can check exactly what happened.
Payment stays separate
Launch runs on pay-at-pickup or an optional SMS payment link — no card details taken by voice.
Transparent status
Clear operational states — accepted, in kitchen, handed off — with honest failure and recovery handling.
Scoped to your operation
One location, one menu, defined hours — a controlled footprint you can reason about.
Help shape VoiceOrder as a founding restaurant
VoiceOrder is in development and we're lining up a small group of founding restaurants for when the pilot opens. It's planned as a controlled, hands-on pilot — scoped, supported, and measured by accepted orders. Not a permanent free plan, and not unlimited custom development.
- One restaurant, one location, one approved number
- Your approved menu and defined operating hours
- A defined call / minute allowance for the pilot
- Pay-at-pickup or SMS payment links to start
- Direct support from the Apex team
- Roughly a 30–60 day window
Straight answers
What restaurant operators ask us most — answered without the hype.
No. Answering the call is the easy part. VoiceOrder is being built to complete accurate pickup orders — validating items and modifiers against your menu, calculating totals deterministically, reading the order back, and handing off to your staff when needed. Success is measured in accepted orders, not answered calls. (VoiceOrder is in development; this site is an illustrative preview.)
That's the core of what we're building. Our earliest focus is independent Indian and Pakistani restaurants in Dallas–Fort Worth, precisely because those menus are hard. Items, modifiers, and substitution rules are designed to be validated against what your kitchen actually allows.
No — that's a core design principle. The voice model handles conversation only. Prices, taxes, totals, availability, payment status, and order acceptance are designed to be owned by deterministic Apex services. If a fact isn't confirmed, the order doesn't proceed — it clarifies or hands off.
It's designed to transfer the call to your staff with context, rather than fail silently. You define the escalation rules, hours, and which calls are eligible.
The plan is a dashboard entry, email, SMS, or a printable kitchen ticket where supported — with a full call and order record behind each one.
At launch, pay-at-pickup or an optional SMS payment link. No card details are taken over voice. Secure in-call payment collection is planned for a later phase.
The pilot is designed to run without requiring custom POS integrations. Deeper POS integrations (like Square) are on the roadmap, not promised for every restaurant at launch.
We're finalizing founding-pilot terms with early restaurants directly. Rather than post a number that might not fit your operation, we scope it with you when you apply.
Stop losing orders to a ringing phone
Apply for the Founding Pilot and we'll scope VoiceOrder to your restaurant, your menu, and your hours.
No payment details required to apply