Skip to content
Eatable logoEatable logoBook a demo
Eatable/Luigi
LuigiIncluded in Eatable Base

He knows your rules.
He helps you act.

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.

01 / Luigi

A real question.
Answers inside your workflow.

From rules to service, from numbers to support. Four practical problems, with the open page at your side.

Settings

Restaurant rules

Online bookings
Maximum advance · days
7
Maximum guests per booking
8
Automatic confirmation
Enabled
Automatic table assignment
Enabled
Current
You

Why can’t guests book for next month on the website?

Luigi

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 rules
Maximum advance · days7 30

This extends the window for new bookings. Opening times, closures and availability still apply.

Illustrative data and conversations. Buttons only change this example.

02 / Luigi

You can start with the problem.
Luigi helps find the next step.

Luigi works with your restaurant’s context and Eatable’s tools. Here’s what that means during service and as you prepare it.

01 / Luigi

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.

02 / Luigi

The past explains the present.

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.

03 / Luigi

A proposal, then approval.

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.

04 / Luigi

Data in a useful form.

Summaries, records, exportable tables and action buttons appear in the conversation. Read the numbers and move to the next action without copying the result.

05 / Luigi

The work stays traceable.

Approved changes are logged under the person who makes them and marked ‘Via Luigi’. You can revisit what changed in the activity log.

06 / Luigi

Support already has the context.

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.

How Luigi works

Luigi provides the answers. Eatable provides the rules.

  1. 01

    Your request

    Start with a question or a problem to solve.

  2. 02

    Deterministic Eatable Core

    Tools check the data, calculate availability and apply rules and permissions.

  3. 03

    Luigi helps you decide

    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.

Before you ask Luigi.

Where do I find Luigi?

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.

Can it change settings without asking?

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.

Can it help explain a past decision?

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.

What if I need support?

Luigi can propose opening a ticket and prepare a subject and description with the problem’s context. Opening it requires your approval.

Can I see usage?

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.

Bring a question from your restaurant.
Let’s start there.

During the demo we start with your bookings, your rules and the work you’d like to simplify.