Setting up your table plan with AI
- Waar vind ik dit
- AI assistant or your own AI agent (MCP)
You can also have an AI agent set up your dining room. You tell it what your room looks like, for example twelve tables for four, four tables for two by the window and a terrace with six tables, and it creates the floor plan, the tables, the zones and the combinations. Handy for a new location or for a plan you already have on paper.
One thing the agent does not do: put the tables in their real place. It places them neatly on a grid. Afterwards you drag them in the editor to where they really stand (see Drawing your dining room).
What you need
- An AI agent connected to the Gasto configuration tools. How to do that is described on Connecting an AI agent to the MCP server.
- The right menu_confmod_floorplan, the same right as for the floor plan editor, plus tool_config_use and the rights of the table plan tools themselves.
- The configuration locks must be open.
How to ask
Give the agent the same information you would enter in the editor. An example:
Create a floor plan Restaurant of 14 by 9 metres. Create the zones Window and Room. By the window there are four tables for two, R1 to R4. In the room there are eight tables for four, 1 to 8, and a large table 9 for six to ten people. Tables 3 and 4 may go together, and then seat eight.
The agent first shows what it is going to create. Only when you agree does it carry it out. Afterwards you can ask it what is there; it lists the tables, zones and combinations with their numbers.
What the agent fills in if you say nothing
- A table without values is for 2 to 4 guests, with 15 minutes of buffer after a booking. Those are the same defaults as in the editor. What they mean is explained in Setting up tables: name, occupancy and buffer.
- A table combination without a given maximum seats as many guests as the tables together. Set the maximum higher and the agent warns you.
Asking a second time is safe
If you ask the agent again for table 9 for six to ten people, it adjusts the existing table 9 instead of making a second one. It recognises tables and zones by their name on the floor plan. Renaming a table therefore does not go by name: say which table you mean, and the agent looks up its number.
The agent does not create a floor plan with a name that already exists again. It reports that it is already there, and carries on with that floor plan.
Zones and combinations
Zones work as in Zones and the order in which your room fills up: the agent creates the zone and puts tables in it. A combination records which tables may be pushed together, and may only contain tables of the same floor plan. How Gasto uses combinations during service is described under Combining and blocking.
Note the difference: during setup the agent can record which tables can go together. During service an agent can seat a party on such a combination, but it cannot come up with a new combination then. Which tables may be joined is a decision about your room, and you make it during setup.
Removing a table or zone
You can ask the agent to switch a table off. That works just like deleting in the editor: if guests are seated at it now, it refuses. Planned bookings on that table lose their table and return to the bookings still to be allocated, and the table disappears from combinations. The agent says so beforehand. Removing a zone takes it off the tables.
What you do yourself afterwards
- Dragging the tables into place, and drawing walls, bar and kitchen: Drawing your dining room.
- Linking the floor plan to what guests book. Without that link Gasto allocates nobody: Linking your floor plan to what guests book.