This is a guided demonstration using a fictional restaurant. It illustrates a pickup-order journey. No food is prepared and no payment is taken. The walkthrough describes the reviewed demo design; it is not a claim of full production acceptance or a list of promised integrations.
One workflow with a deliberate confirmation point
The useful thing to inspect is the transition from a conversation to an action. A caller can ask questions, correct a dish or change a quantity without that speech alone becoming a placed order. The demo prepares a quote first and requires a separate on-screen confirmation.
- Choose a language and review the demo notice.
- Ask about the configured menu and build a pickup order.
- Review the server-calculated quote on screen.
- Enter a fictional first name and tap Confirm order.
- Check the displayed order confirmation.
This is a workflow illustration, not a screenshot of a customer deployment.
Start with the notice and language
The demo includes English, Punjabi and Hindi language choices. Before starting, review its own consent and data-handling notice and acknowledge that you are speaking to an AI. Microphone access is needed for the voice conversation.
Use fictional details throughout. The restaurant and orders are for demonstration. Do not provide payment information, real health details or other sensitive personal information. The notice in the demonstration governs that experience; do not assume another Lucentia assistant’s recording or retention terms are identical.
The menu is a boundary, not a suggestion
The voice assistant uses the configured restaurant menu to look up dishes and prepare an order. A useful demo request is a named dish with a quantity, followed by a correction. Check that the resulting order contains what you intended, not simply that the assistant sounded confident.
Special preparation requests need to stay attached to the right dish. Ask for less oil on one item, then inspect whether the request appears against that item rather than every dish in the cart. A recorded request is not a guarantee that a kitchen can satisfy it. Allergen information in this demo is not verified; do not use it to decide that a dish is safe.
The quote comes from the server
When the order is ready for review, the demo requests a calculated quote. The screen shows line items, subtotal, demo tax and a total in Canadian dollars. These are fictional restaurant amounts, not Lucentia implementation or DineDesk subscription prices.
The screen gives you a record to inspect. Ask for a quantity change and check that the revised quote replaces the previous one. The reviewed design requires a fresh quote after changes; a fluent spoken total is not sufficient evidence that the current cart is correct.
Only the on-screen button confirms
The caller enters a name for the demo order and taps Confirm order. Saying “yes” during the conversation does not perform that action. If you are evaluating the demo with Lucentia, deliberately try spoken consent without touching the button and check that no order is claimed as placed.
After a successful button confirmation, the screen displays the order number and amount. Treat that visible result as the record to inspect. If an error appears, do not assume success from a previous spoken sentence; review the on-screen state with the person guiding the demonstration.
What this demonstration does not establish
- It does not prepare real food or take payment.
- The reviewed demo is pickup only; it does not demonstrate delivery or reservations.
- It does not establish a connection to your POS, payment processor or existing ordering platform.
- It does not prove that every language, interruption, device or failure scenario has passed acceptance testing.
- It does not announce an approved subscription price or production launch date.
The source and deployment notes reviewed for this article still identify release acceptance work as open. A working demonstration is useful evidence for a specific flow, but a commercial rollout needs its own confirmed scope, support arrangement and acceptance results.
Bring a short test script to the guided demo
Try an ordinary menu question, a multi-item order, a quantity correction, an item-specific request and an unavailable feature. Check what the system does when it cannot answer. Then inspect the quote and test the confirmation boundary. This is more revealing than asking the receptionist to describe itself.
Bring a sample menu and your operational requirements to the conversation, but use fictional caller details in the demo. The team can assess product fit and discuss which capabilities are available for your situation without treating the demonstration as a commitment to build every requested feature.
Request a guided DineDesk demonstration. If your workflow needs separately assessed integrations or different approval rules, read custom implementation versus SaaS and discuss a scoped Lucentia Services engagement.
Basis for this walkthrough
Lucentia reviewed the DineDesk demo interface implementation and its deployment notes on 22 October 2026, alongside the public DineDesk overview. The design review establishes the described flow and limits; it does not substitute for live acceptance testing. Private source files and demo access credentials are not published here.