FAQ
Questions Restaurant and Hotel owners ask before they start.
Search the most common product, pricing, QR, Qube AI and Hotel questions.
No. DineQube guest journeys are designed to open in the browser after scanning the QR code.
No. The QR is an entry point. DineQube also connects Restaurant ordering, Hotel guest requests, live operations and Qube AI capabilities.
DineQube should not be presented as replacing every mature POS function. It is positioned around direct QR ordering, guest experience and connected operational workflows.
Operational availability controls depend on the enabled DineQube Restaurant configuration. The product is designed to give the merchant control over live ordering states.
DineQube includes Restaurant takeaway workflows where enabled in the current product configuration.
The Hotel guest experience can include food ordering, amenities, housekeeping, laundry, assistance and hotel information depending on property configuration.
The Hotel operations experience is designed to surface room-linked guest requests and their service state for the team.
Qube AI is the intelligence layer inside DineQube. Current public positioning includes supported AI voice alerts and AI-assisted menu workflows, with deeper intelligence clearly marked as coming soon where applicable.
English and Hinglish are the active public language positioning for supported Qube AI voice alert workflows.
Yes. Direct Delivery OS is live for eligible Restaurant Growth accounts, including direct customer ordering, rider assignment, delivery status workflows and customer updates.
No. AI Inventory Intelligence is shown as a future / Coming Soon capability.
No. DineQube’s current public commercial flow is demo-first paid activation; there is no free-trial period.
The current public pricing uses a Custom plan for Hotel requirements above 20 rooms.
Use the Book Demo page and select Restaurant or Hotel so the enquiry is routed with the right context.