01
Use only configured menu items
The agent answers from the Menu and may suggest at most one relevant item. An absent dish is not invented.
Restaurant / food · shipped order counter
Dvaarik's food configuration uses the Menu to capture items, delivery or pickup, service area and order timing, then records an Order and payment step without a Calendar or Staff rota. At ₹2/min, 600 two-minute order calls are about ₹2,400/month in voice usage.
Product configuration and public price checked 15 Aug 2026.
Dvaarik models food as repeatable stock chosen inside a conversation. Orders, Menu, Diners and Payments are the shape-specific pages; Kitchen Staff is a label, not a roster page in this shape.
01
The agent answers from the Menu and may suggest at most one relevant item. An absent dish is not invented.
02
The fulfilment choice controls address, service area, timing and any configured delivery charge.
03
Items and quantities are added as the diner confirms them, then the address and total are read back once before the order is placed.
04
The current food shape is an Order Counter. The page therefore does not market table reservations or a staff calendar that the vertical registry does not add.
Shipped configuration · read 15 Aug 2026
Dvaarik provisions the Order Counter shape for the backend key food. The configured job is to order: repeatable stock is selected and paid for inside one conversation without a calendar or staff rota
| Configuration | Shipped value |
|---|---|
| Vertical key | food |
| Dashboard shape | Order Counter |
| Trade nouns | Orders · Menu · Kitchen Staff · Diners · Menu card |
| Shape-specific pages | Bookings · Customers · Services · Payments |
| Pages every vertical receives | Overview · Calls · Conversations · Leads · Outbound · WhatsApp · Instagram · Campaigns · Widget · Agent · Voice · Knowledge · Billing · Settings |
The Restaurant / Food dashboard adds Bookings, Customers, Services, Payments to the fourteen universal platform pages. The same registry also changes the owner-facing vocabulary: Bookings become Orders, Services become Menu, Staff become Kitchen Staff, Customers become Diners, Brochure become Menu card. The page list and words are derived on each request rather than being a marketing-only template.
Ask-on-call budget
2 CALL MINUTES
The food flow asks whether the customer wants to order and whether fulfilment is delivery or pickup. Menu items and totals come from the configured catalogue.
Column-only fields do not force another spoken question. Post-call extraction can still populate a field when the caller volunteers the information naturally.
| Lead field | Capture behaviour |
|---|---|
| Order intent and items | Captured as the diner confirms menu items. |
| Delivery or pickup | Asked early because the fulfilment path changes. |
| Date and delivery area | Recorded when the order is for later or depends on service area. |
The Restaurant / Food intake record names Order intent and items, Delivery or pickup, Date and delivery area. Spoken questions use the stated CALL MINUTES budget; extraction-only columns preserve useful details without turning every call into an interrogation.
Vertical scoring rubric
Food scoring measures the order outcome: an order with a settled date and delivery or pickup is high, while no current interest or an address outside the delivery area is low.
Worked monthly voice cost · 15 Aug 2026
At Dvaarik's ₹2/min direct voice rate, 600 calls a month averaging 2 billed minutes each would use 1,200minutes and cost about ₹2,400/month in voice usage (600 × 2 × ₹2), with the call-volume assumption and rate read on 15 Aug 2026.
Dvaarik bills whole minutes rounded up. The worked amount excludes a phone line and optional recurring channel plans, so the number is a voice-usage equivalent rather than a bundled quote.
Read the full pricing scopeThe restaurant page no longer claims a table-reservation calendar in the current Order Counter shape.
The restaurant agent never invents a dish, price, delivery area, or order status.
The restaurant lead rubric treats a settled order, date, and delivery or pickup as the strongest outcome.
The restaurant monthly example isolates voice usage and does not hide a phone line or optional channel plan inside the ₹2/min figure.
Dvaarik's answers below restate the shipped workflow, lead capture, scoring basis and price assumptions without adding features outside the current vertical configuration.
The current food vertical is an Order Counter whose Bookings noun is Orders. It adds Orders, Diners, Menu and Payments without Calendar or Staff, so this page does not claim a table-reservation workflow.
The food flow captures order intent and menu items, delivery or pickup, and the date or delivery area when relevant. Totals and item facts come from the configured menu rather than guesses.
At ₹2/min, 600 calls averaging two billed minutes use 1,200 voice minutes and cost about ₹2,400/month in voice usage, excluding the phone line and optional channels.