How does an AI phone order call work from start to finish?
Every call follows the same sequence: the agent knows the restaurant before it speaks, takes the order, prices it from the system, settles how the food gets to the customer, reads it all back, and only sends it to the kitchen after a clear yes.
Each step is tied to the restaurant’s actual data rather than to what a language model guesses. Here are the steps in order:
- The call starts: the agent receives the restaurant card (opening hours, address, delivery zones and menu) before saying a word.
- Greeting: a short hello in the restaurant’s name and in the dialect set for that agent, then an invitation to order.
- Understanding the order: items, quantities, sizes, extras and notes, with a question whenever a detail is missing.
- Pricing: every price comes from the menu system; the agent never speaks a price the system did not return.
- Pickup or delivery: for delivery, the agent checks the address falls inside a served zone and applies that zone’s fee.
- Scheduled orders: for a later time, the system checks it falls within opening hours and that the slot still has capacity.
- Read-back: the agent reads the full order to the caller and waits for an explicit yes.
- Sending: the order is created in the POS and appears on the kitchen display at the right station.
What does the voice agent know before it answers?
It knows what is on the restaurant card: opening hours, address, delivery zones and menu.
Common questions like “Are you open now?” or “Do you deliver to my area?” are answered straight from the card. Then comes the greeting: one short line that names the restaurant and invites the order, in a dialect the restaurant chooses for its agent: Jordanian, Palestinian, Syrian, Lebanese or Saudi. With Sara, our voice agent, the persona, voice and phrases can be set per restaurant.
How does the agent handle sizes, extras and special requests?
It matches what the caller says against the menu items and their configured options, and asks when something is missing, for example when an item comes in more than one size and the caller has not said which.
If the caller asks for “a shawarma” and the menu has both chicken and beef, the agent asks which. If the item comes in two sizes, it asks for the size. Free-text notes like “no garlic” or “extra pickles” are attached to that specific item so the kitchen sees them exactly as said.
Prices never come from the agent’s memory. The agent asks the menu system for the price of the item with its options and extras, the system computes the total, and the agent repeats it as returned. If the system returns no price, the agent does not say a number.
How are pickup, delivery and scheduled orders handled?
The agent asks whether the caller will collect the order or wants it delivered. For delivery, it checks the address sits in one of the restaurant’s delivery zones and adds that zone’s fee as the restaurant defined it.
If the address is outside every served zone, the agent says so and can offer pickup instead. For scheduled orders, say dinner for 8 pm, the system checks that the time is within opening hours and that the slot has room. If the slot is full, the agent offers another time.
Here is a short example of a shawarma pickup order:
SaraGood evening, this is Sara at the restaurant. What can I get you?
CallerTwo chicken shawarma sandwiches, one with no garlic, and a large fries.
SaraSure. Will you pick them up, or would you like delivery?
CallerI’ll pick them up, in about half an hour.
SaraGreat. Let me read that back: two chicken shawarma sandwiches, one with no garlic, and a large fries, for pickup in about thirty minutes. Is that right?
CallerYes, that’s right. Go ahead.
SaraDone, your order is with the kitchen. See you soon.
How does the agent confirm the order before it reaches the kitchen?
It reads the whole order back, with items, options and pickup or delivery details, and sends it only after an explicit yes. Silence or a hesitant answer does not count as confirmation.
Once confirmed, the order is created in the POS and shows up on the kitchen display at the relevant station, so the shawarma can go to one station and the fries to another. Order creation is designed so that a retry after a network drop does not create a duplicate. Our POS is built on Odoo 19 Community with an Arabic interface.
What protects the restaurant at each step of automated phone orders?
Each step has a guardrail that comes from the restaurant’s settings or its system, not from the agent’s judgment. In summary:
| Step | What the agent does | What protects the restaurant |
|---|---|---|
| Call starts | Receives the restaurant card | Answers rely on the restaurant’s own data |
| Greeting | Greets in the restaurant’s name and set dialect | Persona and phrases the restaurant controls |
| Understanding | Matches speech to items and options | No item or option that is not on the menu |
| Pricing | Asks the menu system for prices | No price the system did not return |
| Delivery | Checks the zone and adds its fee | No promise to deliver outside defined zones |
| Scheduling | Checks the time and slot capacity | No orders outside hours or over slot capacity |
| Confirmation | Reads back and waits for a clear yes | Nothing is sent without an explicit yes |
| Sending | Creates the order in the POS | No duplicate order on retry |
What happens when the restaurant is closed or the caller needs a person?
If the restaurant is closed or the register is closed in the POS, the system refuses new orders, and the agent tells the caller the opening hours instead of taking an order nobody will cook.
If the caller asks for a person, or has a complaint or a special request the agent does not cover, the agent sends the restaurant manager a WhatsApp alert and logs the request in the dashboard for follow-up.
What does a restaurant need to prepare for AI phone ordering?
Four things: a clean menu with its options and extras, delivery zones with their fees, accurate opening hours, and a POS connection, or the built-in demo POS to start.
- A clean menu: clear item names, with sizes and extras set up as separate options rather than notes typed into the item name.
- Delivery zones: the areas you serve and the fee for each.
- Opening hours: including closed days, since scheduled orders are checked against them.
- A POS: a connection to your system, or the demo POS built into the platform to try the full flow end to end.
ABRAJRUM is a Jordanian technology and AI company that builds Arabic-speaking AI voice agents for customer service, a restaurant platform and a point-of-sale system. Each restaurant has its own dashboard, data and agent, with one owner account per restaurant and no staff roles yet.
Common questions
Can the agent get a price wrong?
The agent never makes up a price; every price comes from the menu system, which also computes the total. If a price in the menu is wrong, it will be repeated as is, so accuracy starts with an up-to-date menu.
What if the caller changes their mind mid-call?
They can add, remove or change items before confirming. The agent reads back the latest version of the order, and nothing is sent without an explicit yes.
Will the agent transfer the call to a staff member?
No live transfer. It sends the manager a WhatsApp alert and logs the request in the dashboard, and the restaurant calls the customer back.
Do we need a new POS for automated phone orders?
Not necessarily. You can start with the built-in demo POS to try the flow, or use our Odoo-based POS, with the connection qualified for each restaurant before going live.
Does the agent take orders when the restaurant is closed?
No. When the register is closed in the POS, the system refuses new orders and the agent tells the caller the opening hours.