The context is already there.
It knows the open page, the restaurant and your current filters. It can read bookings and settings without asking you to describe your restaurant again.
An unexpected booking, a rule to understand, the week’s numbers. Luigi reads your restaurant’s data, traces what happened and prepares the next step, right on the page where you work.To understand a setting, you don’t need to spend time calling technical support: ask Luigi.
From rules to service, from numbers to support. Four practical problems, with the open page at your side.
Why can’t guests book for next month on the website?
The maximum advance is set to 7 days. Later dates aren’t open for bookings yet. I can extend it to 30 days.
Checked against the restaurant’s booking rulesThis extends the window for new bookings. Opening times, closures and availability still apply.
Illustrative data and conversations. Buttons only change this example.
Luigi works with your restaurant’s context and Eatable’s tools. Here’s what that means during service and as you prepare it.
It knows the open page, the restaurant and your current filters. It can read bookings and settings without asking you to describe your restaurant again.
It analyses history and the complete activity log: changes, times and events. It traces which rules were in place and shows what the explanation is based on.
To change a rule or update a booking, it prepares an operation to review. You see the values and consequences, then approve or cancel right in the conversation.
Summaries, records, exportable tables and action buttons appear in the conversation. Read the numbers and move to the next action without copying the result.
Approved changes are logged under the person who makes them and marked ‘Via Luigi’. You can revisit what changed in the activity log.
When you need assistance, Luigi can propose a ticket with a subject and description of the issue. You review the content and approve before it opens.
Start with a question or a problem to solve.
Tools check the data, calculate availability and apply rules and permissions.
Shows the result, explains it and proposes the next step. Changes wait for your approval.
Calculations stay in the Core. Decisions stay with you. Luigi does not change the rules on its own.
Luigi is included in Eatable Base and opens beside the page you’re working on in the Eatable dashboard. Availability depends on the restaurant being enabled: we’ll check how you can try it during the demo.
Every operation that changes data requires explicit approval. Luigi prepares the proposal and shows what will change; you can approve or cancel. It cannot perform actions outside your permissions.
It can consult bookings, settings, history and the complete activity log to trace what happened and explain the decision. Explanations must rely on available data, without inventing a cause when information is missing.
Luigi can propose opening a ticket and prepare a subject and description with the problem’s context. Opening it requires your approval.
The Luigi panel and billing show monthly usage and when availability renews. Luigi is included in Eatable Base and does not use the AI credit wallet; we check restaurant enablement during the demo.
During the demo we start with your bookings, your rules and the work you’d like to simplify.