Case study: a Zarqa family restaurant tames 300 phone orders a day
At Darna Kitchen in Zarqa, the rush did not create new problems. It exposed the same missed address, unfinished order and driver callback again and again.
Nexara is a restaurant order and operations platform built in Amman, Jordan, for restaurants and multi-branch chains. It gives phone-heavy restaurants caller history, saved addresses, one live order board and Arabic kitchen printing beside the till. Nexara does not provide JoFotara, Jahez or DHUB integrations today.
Figures in this post are illustrative examples, not a client's actual results.
The Zarqa problem was ordinary and expensive
Darna Kitchen is a fictional family restaurant in Zarqa with one busy delivery branch. It receives about 300 phone orders on a typical day in this example. The owner has two people answering calls, a cashier beside the till and a kitchen team working from printed tickets.
Before Nexara, useful caller details lived in a notebook, staff memory, an old messaging thread or a paper ticket. A repeat customer still had to explain the same building, floor and nearby landmark.
The usual failures were a rushed address, an order left in draft or a driver receiving no clear landmark. At 300 illustrative calls a day, a small error rate creates extra work for the branch.
| Pressure point | What happened | Operational cost |
|---|---|---|
| Repeat callers | The agent asked for the address again | Longer calls during the rush |
| New callers | The address was written in shorthand | Drivers called back for directions |
| Busy agents | An order stayed incomplete or was copied incorrectly | The kitchen started the wrong ticket |
| Complaints | The branch searched through papers | Slow answers and repeated explanations |
What changed when the caller became a customer record
Nexara's call-center screen lets an agent search by phone number. The caller's saved addresses and past orders appear before the agent rebuilds the basket. The agent can confirm the address, choose items, select the payment method and place the order from the same screen.
For a returning customer, the agent confirms the stored address and asks what has changed. If the customer moved, the new address can replace the old one for the next call.
The restaurant owns the customer records. Nexara supports customer records with addresses and order history, plus CSV export of orders and customers. A blacklist is also available for branches that need to flag repeated abuse or unsafe orders.
The call screen can log a complaint. The complaint becomes a case with status, routing and an SLA clock.
For a deeper explanation, see how customer records stay with the restaurant.
How the phone order reaches the kitchen
The phone order joins the same live order board as website, app, table QR, Talabat and Careem orders. The cashier can record the day's net sale at close for reconciliation. Nexara is the order and operations layer beside the till.
On an ordinary ESC/POS thermal printer, the ticket can print in Arabic, with English available on the same ticket. Printers connect over USB or a network. Tickets queue and print once, never twice, never lost.
If a printer stops responding, the order stays on the board. Staff can re-route that printer's categories from the dashboard, or use automatic failover to a configured backup printer.
Read how Nexara takes a phone order for the agent's screen-by-screen process.
The address check that prevents a failed delivery
- Search for the caller by phone number before typing a new customer.
- Read the saved address back to the customer, including the building, floor and landmark.
- Ask what has changed since the last order.
- Confirm the order type, delivery address and payment choice before placing the order.
- Check the printed ticket before the driver leaves.
- Log a complaint as a case when the customer reports a missing item or delivery problem.
Use these six checks during the call.
| Example measure | Before | After |
|---|---|---|
| Average call time | 6 minutes | 4 minutes |
| Illustrative wrong-address deliveries | 12 | 5 |
| Illustrative address-related rate | 4.0% | 1.7% |
| Address source | Paper and memory | Customer record plus confirmation |
What the owner should measure for one branch
Pick one branch and record the same measures for seven days before changing the call flow. Use the call-center report tab and order history to compare the period after setup.
| Measure | How to check it | Why it matters |
|---|---|---|
| Phone orders received | Call log and order history | Shows demand and missed orders |
| Incomplete orders | Abandoned-order reasons | Shows where calls break down |
| Address callbacks | Driver and complaint records | Shows address quality |
| Wrong-address complaints | Complaint cases | Shows delivery accuracy |
| Manual corrections | Order history and reprints | Shows ticket and entry errors |
| Saved-address confirmations | Customer record review | Shows repeat-caller discipline |
| Average call time | Call-center report tab | Shows whether the process fits the rush |
The call-center module is available on Nexara's Pro plan. Nexara has a free plan plus paid plans per branch in Jordanian dinar, with current rates available on request. The founder answers support through WhatsApp and email on Amman hours.
Test whether a new agent can find the caller, confirm the address, place the order and read the ticket within the branch's normal call time.
Where Nexara fits, and where it stops
The restaurant's own website, app and call-center orders carry 0% commission. Talabat and Careem keep their own commission on the orders they bring.
Activation for partner channels depends on partner approval.
Nexara's WhatsApp module is a conversation inbox for call-center roles, not an order-notification sender. JoFotara e-invoicing, Jahez and DHUB integrations are not available today.
Nexara is built in Amman and its live deployments are in Jordan. The platform is available in Arabic and English and runs through a browser with the branch print agent.
What to remember
- Search by phone number before creating a new customer.
- Confirm the saved address, landmark and floor on every delivery call.
- Send every phone order to one live board and an Arabic kitchen printer.
- Measure wrong-address complaints for one branch before expanding the process.
Questions people ask
How can a restaurant stop losing phone orders?
Use one call-center screen that links the caller's phone number to the order, address and order history. Place the order before ending the call and check it on the live order board.
Does Nexara remember a caller's address?
Yes. Nexara saves addresses and order history, and the call-center screen shows them after the agent searches by phone number. The agent should still confirm the address before placing the order.
Can Nexara print phone orders in Arabic?
Yes. Phone orders can print on standard ESC/POS thermal printers in Arabic, with English available on the same ticket.
What happens if the kitchen printer stops working?
The order remains on the live board and the ticket waits in a queue. Staff can re-route categories from the dashboard, or use a configured backup printer.
Is Nexara a POS or cash register?
Nexara is the order and operations layer beside the till. It gathers orders, sends them to the board and kitchen printer, while the cashier records the day's net sale for reconciliation.
Does Nexara send order notifications on WhatsApp?
No. Nexara includes a WhatsApp conversation inbox for call-center roles, but it does not send WhatsApp order notifications.