Takeout and quick service
A phone is still a genuine channel wherever no in-house online ordering exists, especially outside large centres.
Connected orders
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
The task it takes over
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 an order on a line and carries it through to acceptance by a kitchen. It knows a 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 a customer hears a confirmation once a restaurant accepts. Should a write fail, a retry runs and an exception is raised to a team rather than vanishing.
Step by step
- During a call
A menu as it stands tonight
Dishes, options, sides and whatever ran out: an order is built on current availability, rather than a menu printed in spring.
- Write
Into your system, beyond a sticky note
An order is sent to a restaurant's ordering system. A failed write is retried, and whatever still fails is flagged to a team.
- Confirm
Acceptance comes from a restaurant
A customer hears a pickup time once an order has been accepted. Until then it stays a request, and it is described as one.
- On a change
Changes and status
Authorized changes are applied and status follows. A request beyond what you authorized is passed on rather than decided.
An add-on, not a base capability
A Restaurants base answers on a menu, hours and access, and passes a request to a 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 a deposits and payments module on top for those same orders. That module stays necessary for any other billing. And with no deposit asked, no collection is triggered: an order can be taken with no payment at all.
What this changes for your business
Table service restaurants
An evening service fills a room and leaves takeout calls with nobody to answer. They stop disappearing.
Caterers
Repeat orders, shifting quantities, pickup at an exact hour: an order written in a right place avoids retyping by hand.
What it receives
- Your menu, its options and prices exactly as you entered them
- Current availability and whatever ran out
- Pickup rules: lead times, hours, zones if you deliver
- Which changes you authorize without a callback
What it produces
- An order written into your ordering system
- Acceptance confirmed to a customer, with a pickup time
- A payment request, whenever you ask for one on that order
- Exceptions raised: a failed write, a sold-out item, a request outside your rules
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.
What is metered, and what comes from elsewhere
Two allowances travel together, and neither overlaps with a base.
- Accepted orders per month, reset at each period
- Payment requests on those same orders, within a same period
- Inbound calls stay metered on a base, separately
- No double billing with a deposits and payments module on these orders
A payment link belongs to your own merchant account: transaction fees sit with your payment provider and are billed by them.
With your ordering system
Writing into an ordering system requires qualification product by product. A status below reflects that qualification.
- Point of sale and event toolsTo qualifyA family requirement rather than a certified product; a vendor's booking module establishes nothing about its ordering coverage.My software is not in the list
- OpenTableTo qualifyAn application is required and no Zenvox approval exists; useful on a dining room side, with no established ordering scope.OpenTable
Questions about this add-on
An order taken — is it an order accepted?
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.
What if the write into my system fails?
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.
Can it invent a dish or a price?
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.
Do I need the payments module to collect on these orders?
Not for these orders: the payment request is included here, and nothing is billed twice. The deposits and payments module stays necessary for any other billing, and with no deposit asked, no collection is triggered.
Where do the transaction fees come from?
The payment link belongs to your own merchant account: transaction fees sit with your payment provider and are billed by them, outside this add-on.
Where to next
Go back to your restaurant, or read a neighbouring add-on.
Connected orders