Is this a reservation system?

No. It is a map of the questions that arrive before and around a booking. Your reservation system stays exactly where it is.

Why questions instead of a booking widget?

Because the booking is rarely the blocker. The blocker is the message asking whether the fryer is shared, whether the terrace is covered, and whether you can seat eight — sent at an hour nobody is free to answer.

What happens when Lina does not know?

She says so and hands the guest to a human. On an allergen question a confident wrong answer is far worse than an honest "let me get someone".

Who keeps the allergen information correct?

You do, from your phone, in the DL Panel. It is your kitchen and your dish — what we remove is having to call a developer when the recipe changes.

Industry · Restaurant

The questions that arrive after the kitchen closes.

Pick the guests you actually get. This shows the questions they send before booking — and the facts your restaurant has to publish for Lina to answer them instead of someone mid-service.

Why this exists

A restaurant does not lose bookings on the food. It loses them in the gap between a guest reading the menu and somebody replying to their message — which lands at 19:40, mid-service, on a phone that is already ringing.

This is not a booking form; you already have one. It maps the guests you actually get to the questions they send, and to the facts your menu and listing must state before any assistant can answer them. The knowledge is the product — this shows exactly which piece of it is missing.

What we build for restaurant businesses

Lina for guest questions — Answers allergen, hours and terrace questions on your site, in the guest’s language, while the kitchen works.
A menu that is readable — A fast static site that loads on mobile data outside your door, not a PDF.
QR menu at the table — No app; the guest scans and reads, in their own language.
Allergen information that holds — Published once per dish, edited from your phone when the dish changes.
Document handling — Licences, inspections and supplier contracts filed and searchable in Fioka.
Your own domain — A direct listing that does not hand every guest to a portal that charges commission.

Questions

Is this a reservation system?: No. It is a map of the questions that arrive before and around a booking. Your reservation system stays exactly where it is.
Why questions instead of a booking widget?: Because the booking is rarely the blocker. The blocker is the message asking whether the fryer is shared, whether the terrace is covered, and whether you can seat eight — sent at an hour nobody is free to answer.
What happens when Lina does not know?: She says so and hands the guest to a human. On an allergen question a confident wrong answer is far worse than an honest "let me get someone".
Who keeps the allergen information correct?: You do, from your phone, in the DL Panel. It is your kitchen and your dish — what we remove is having to call a developer when the recipe changes.