Takeout and quick service
A phone is still a genuine channel wherever no in-house online ordering exists, especially outside large centres.
A phone order lands in your own system and comes back accepted — with no third-party app commission.
7 days, 20 answered calls, no card
Plenty of independent restaurants push customers to order direct rather than through a delivery app, for one plain reason: commission. Yet ordering direct means telephoning, and telephoning on a Friday at six means ringing into an empty room.
This add-on takes the order on the line and carries it through to acceptance by the kitchen. It knows the menu, its options and what is available tonight; it reads prices as you entered them, inventing neither a price nor a dish.
An order taken is separate from an order accepted: it is written into your ordering system, and the customer hears a confirmation once the restaurant accepts. Should a write fail, a retry runs and the exception is raised to your team rather than vanishing.
Dishes, options, sides and whatever ran out: an order is built on current availability, rather than a menu printed in spring.
An order is sent to a restaurant's ordering system. A failed write is retried, and whatever still fails is flagged to a team.
A customer hears a pickup time once an order has been accepted. Until then it stays a request, and it is described as one.
Authorized changes are applied and status follows. A request beyond what you authorized is passed on rather than decided.
The Restaurants & caterers base answers on the menu, hours and access, and passes a request to the counter. It informs about ordering; it neither writes an order into your system nor gets it accepted.
For these orders, payment requests are included here: you do not stack the Deposits and payments add-on on top for those same orders. That add-on serves any other billing. And with no deposit asked, no collection is triggered: an order can be taken with no payment at all.
A phone is still a genuine channel wherever no in-house online ordering exists, especially outside large centres.
An evening service fills a room and leaves takeout calls with nobody to answer. They stop disappearing.
Repeat orders, shifting quantities, pickup at an exact hour: an order written in the right place avoids retyping by hand.
A restaurant accepts or refuses an order, as it would at a counter. Zenvox invents no dish and no price, promises no lead time a kitchen has not confirmed, and guarantees nothing about allergen traces.
This add-on is included in the free trial, like every add-on. After that, you add it to your Restaurants & caterers base whenever it is useful.
The payment link belongs to your own merchant account.
The order is written into your ordering system, under the authorization you give from your account, and the customer hears a confirmation once the restaurant accepts it.
No. An order taken is written into your ordering system, and the customer hears a confirmation once the restaurant accepts. Until then it stays a request, and it is described as one.
A retry runs, and whatever still fails is flagged to a team rather than vanishing. The exception is visible: nobody discovers the missing order at pickup time.
No. The order is built on the menu, its options and current availability, with prices exactly as you entered them. It adds no dish that does not exist and promises no lead time the kitchen has not confirmed.
Not for these orders: the payment request is included here, and nothing is billed twice. The Deposits and payments add-on serves any other billing, and with no deposit asked, no collection is triggered.
Your own merchant account: the payment link sent to the customer is yours, under your payment provider's terms.
Go back to your restaurant, or read a neighbouring add-on.
Connected orders