Garages and auto services
An accessory, a set of wiper blades, a routine maintenance part get ordered on the phone. Availability read at the source saves tomorrow's callback.
Helping somebody choose the right items, then getting an order genuinely confirmed by your store — rather than an intention noted somewhere.
7 days, 20 answered calls, no card
Calls beginning with do you have too often end with let me check and call you back. In between, somebody hung up and ordered elsewhere. The problem is not selling: it is knowing, during the conversation, what is in stock and at what price.
This add-on reads the catalogue of whichever store is connected: items, variants, availability and current price. The conversation helps a person choose, prepares a recalculated cart with its pickup or delivery terms, and has them confirm what they are taking.
The store stays in charge of the order. The confirmation recorded is the store's, rather than a Zenvox declaration: until the store confirms, the order is unconfirmed. That rule prevents a sale announced to a customer and absent from your system.
Items, variants and availability are read in the connected store. An answer about stock comes from the source, rather than from a copy refreshed last week.
The cart is prepared under standard pickup or delivery rules. The calculation is the store's, and a person sees what they are taking before going further.
A person confirms, then payment happens inside the provider's own flow. The order is recorded once the store genuinely confirms, and not before.
Order status is tracked on the file. A cancellation or return request is created as a request: by itself it authorises no refund.
The add-on includes collecting on its own orders, inside the scope of those orders. Another payment scope — ordinary invoices — belongs to the deposits and payments add-on, which then keeps its own capacity.
What it is not: a replacement for accounting, inventory or a whole commerce platform, nor a store built by Zenvox. For a restaurant, the industry's connected ordering stays sufficient: this add-on covers a separate retail store.
An accessory, a set of wiper blades, a routine maintenance part get ordered on the phone. Availability read at the source saves tomorrow's callback.
Counter-sold material is reserved during the call. Pickup is confirmed with its terms, and a customer file keeps a record of what was taken.
Products sold after a service are repeat sales. Ordering them inside the conversation beats a callback that will not happen.
Food or a care product gets reordered regularly. The order follows its statuses, and a return request stays a request subject to your decision.
A refund stays your decision and is not implicitly added to the right to collect. Executing a cancellation depends on whatever a store provides for.
The add-on carries order journeys per period, one connected store, and payment requests belonging to those orders.
Payment provider fees and commerce platform fees are billed by them, outside a subscription.
A status shown is technical qualification. A connected store stays the system of record for an order.
No. The store stays in charge of the order: until it confirms, the order is unconfirmed. That rule prevents a sale announced to a customer and absent from your system.
From the connected store, read at the source: items, variants, availability and current price. An answer about stock does not come from a copy refreshed last week.
Yes, as a journey, without becoming a sale. A journey starts once somebody explicitly engages a cart and counts once; a product question, a stock read or tracking an existing cart create no further journey.
No. The add-on replaces neither your accounting, nor your inventory, nor your commerce platform, and Zenvox does not build a store for you.
No. A cancellation or return request is created as a request: by itself it authorises no refund, and executing it depends on whatever your store provides for.
Payment in other cases, or the conversation carrying an order.
Orders from your store