n8rhood Tables
Not built

An agent should be able to book a table. Ours cannot yet.

This page is here because the alternative was a screenshot of a conversation that has never happened. There is no agent interface today — no MCP server, no tools, no endpoint.

What exists today

Enough that the interface, when it is written, has something true to sit on.

  • An availability engine that works from the venue's room and the bookings in n8rhood — its hours, turn times and tables — including a booking the venue takes by phone, WhatsApp or Instagram once it records it in the console. A party that stays past its turn is not in it yet.
  • A table hold the database decides, so two guests booking online at the same moment cannot take the same table. Once saved, a walk-in, and a table set or moved by hand, holds its table for its turn too, so it is not given to a guest online.
  • A ledger of every change to a booking's status, table, note or headcount, wherever it was made: if a colleague changed the same detail after you did, their version stands, and yours is still in the log.

What it will do, and what it will not

Written now, while it costs nothing to commit to.

  • It will never confirm a table the availability engine did not offer. An agent gets the same answer a guest gets.
  • It will never take a booking without a real contact the venue can reach. A reservation nobody can confirm is not a reservation.
  • It will hold, not promise. A held table is a row with a deadline on it, and it goes back to the room when the deadline passes.
  • The venue can switch it off. An owner who does not want agents booking their Saturday says so once.

When

No date. Naming one would be the same species of claim this page exists to avoid — and the console has to be finished first.

What is finished

The service screen, the availability rules, the room, the waitlist and the offline substrate all run today.

See what it does