Delivery time promises you can keep (and show customers)
A customer can accept a 45-minute delivery time. They will complain when you promised 25 and arrive after 50.
Nexara is a restaurant order and operations platform built in Amman, Jordan. It puts phone, website, Talabat and Careem orders into one live queue, with customer-facing tracking links and statuses a kitchen and a caller can read. It does not provide a guaranteed exact arrival time for every order. Managers set honest delivery ranges from the branch’s preparation, handover and travel conditions, and update them as the queue grows.
Figures in this post are illustrative examples, not a client's actual results.
What should a delivery promise include?
Measure the stages behind the arrival range so staff can see where time is being used.
| Stage | What to measure | How it shows to the customer |
|---|---|---|
| Preparation | Order accepted to ready | Part of the arrival window |
| Handover | Ready to driver pickup | Part of the arrival window |
| Travel | Pickup to customer address | Part of the arrival window |
| Delay | Time beyond the promise | A direct update and revised range |
Do not show a single minute when the branch cannot control every stage. A range such as 35 to 50 minutes gives the customer a usable arrival window. If the kitchen is already backed up, change the range before accepting more orders.
How should times differ by order channel?
A restaurant’s own website, call center, Talabat and Careem may serve the same menu while using different operational steps. Set a promise for each channel and branch. Talabat and Careem commonly retain commissions of 25 to 30 percent on the orders they bring, while 0% commission on your own channels covers orders placed through the website, installable app and call center.
| Channel | Set before accepting | Check during service |
|---|---|---|
| Own website or app | Preparation window plus dispatch area | Live order status and tracking link |
| Call center | Address, items and current branch load | Customer record and order history |
| Talabat or Careem | Partner channel settings and branch capacity | Inbound status, cancellations and driver details |
| Pickup | Preparation time only | Ready-for-pickup status |
Nexara places phone, website, app, table QR, Talabat and Careem orders in one live queue per branch. The cashier still records the day’s net sale at close. Nexara is the order and operations layer beside the till, not a cash register.
How do you turn a promise into a working process?
The numbers below are an illustrative example, not a client’s actual figures. A Jordanian branch handling 60 to 400 orders a day may need different ranges across service periods. If a branch needs 18 minutes to prepare food, 7 minutes for handover and 15 to 25 minutes for travel, the displayed promise is 18 + 7 + 15 to 18 + 7 + 25, which is 40 to 50 minutes. When preparation stretches to 30 minutes, the new range becomes 30 + 7 + 15 to 30 + 7 + 25, or 52 to 62 minutes, and the staff update the promise before accepting the next order.
- Record the normal preparation time for each busy service period.
- Separate delivery areas by the zones your branch actually serves.
- Add the driver handover time to the kitchen estimate.
- Show a range instead of a precise minute when travel varies.
- Pause or lengthen the promise when the live order board grows.
- Give staff one sentence to use when a customer calls about delay.
- Review delivered orders and complaints at the end of the shift.
What should customers see while waiting?
Show the promise at checkout, in the confirmation message or receipt, and on the tracking page when that channel supports it. Use plain status words: received, preparing, ready, out for delivery and delivered. Avoid telling a customer that the driver is on the way while the order is still in the kitchen.
Nexara provides a customer-facing tracking link with a token. Orders move through statuses such as awaiting payment, pending, confirmed, preparing, ready for pickup, out for delivery, delivered, cancelled and refunded. Nexara does not send WhatsApp order notifications. Its WhatsApp module is a conversation inbox for call-center roles, so use the channel’s supported customer updates or call when a delay needs personal handling.
What should staff do when delivery is late?
Treat a late order as a case to manage. Check the order status, kitchen progress, driver handover and address. Then give the customer a new range and a clear action.
- Find the order on the live board using the order history search and filters.
- Confirm whether the food is preparing, ready, out for delivery or held by a problem.
- Call the customer when the revised arrival time will miss the original promise.
- Record the complaint and the reason, such as kitchen delay, address issue or driver delay.
- Offer the remedy your restaurant policy allows and assign follow-up before closing the case.
- Review breached cases so the next promise reflects the actual constraint.
Nexara includes complaint cases with SLA clocks, routing, escalation and statuses such as open, breached, escalated and resolved. It also keeps customer records with addresses and order history.
For a practical operating pattern, see complaint cases and SLA handling. If your restaurant uses its own drivers, delivery dispatch for own drivers covers the dispatch side.
How can feedback calls improve the next promise?
Ask about the delivery while the experience is still fresh. A call can identify whether the breach came from preparation, driving, an item or the address.
- Was the order delivered within the promised range?
- Was the food temperature acceptable?
- Was anything missing or changed?
- Was the tracking information accurate?
Nexara creates feedback-call tasks from delivered orders and supports item summaries, dispatch information, reports and PDF output. A manager can connect feedback to the original order instead of keeping delivery complaints in a loose notebook.
Read feedback calls after delivery for a repeatable call process. Review breached cases in the complaint report before the next service.
What to remember
- Build every promise from preparation, handover and travel.
- Use a range that changes with the branch’s live workload.
- Show statuses customers can understand and track.
- Contact late customers before the original promise expires.
- Review breached cases in the complaint report before the next service.
Questions people ask
What is a good delivery time estimate for a restaurant?
Use a range based on preparation, handover and travel. The correct range is the one your branch can meet during the service period shown.
How do I reduce late delivery complaints?
Change the displayed range when the branch queue grows, then contact customers before the original promise expires. Record the reason for each breach so the next estimate reflects the actual conditions in the kitchen and on the road.
Can customers track restaurant orders in Nexara?
Yes. Nexara provides a customer-facing tracking link with a token, and orders move through statuses such as preparing, ready for pickup, out for delivery and delivered.
Does Nexara calculate an exact arrival time?
Nexara supports order statuses, delivery dispatch and customer-facing tracking. It does not provide a guaranteed exact arrival time for every order, so the branch sets an honest operating range.
Can Nexara send delivery updates on WhatsApp?
No. Nexara’s WhatsApp module is a conversation inbox for call-center roles, not an order-notification sender.
What should staff say when an order is late?
Use a sample line such as: Your order is ready and waiting for the driver. We expect it within 15 to 20 minutes, and I will record this delay for the manager. (Example wording, not a Nexara-approved script.)