In an open kitchen, a chef plates a dish in front of a wood fire
Product

Your standards, appliedto every request.

TableAgent applies your house rules to every request, passes you what they don’t cover, and remembers every decision.

The architecture

You keep your tools.You gain your house’s memory.

Every request, wherever it comes from, converges in one place. There, your standards decide: what they cover is executed in your software, the rest goes up to your team.

Where the guest writes or calls
Phone · coming soonMissed callsWhatsAppInstagramFacebookEmailWebsite Chat
Everything converges here
TableAgent Operational Intelligence
Understands the contextApplies the house standardsArbitratesExecutesPasses to the team when neededRemembers the decision
Where the booking lives
Your booking software

It recognises the guest from their number, reads availability, the pace of service and their history, and writes the booking, the deposit terms and the guest note. Zenchef, SevenRooms.

Passes on and learns
Your team

It knows when to hand over: it passes the exception on with its context; the team’s decision is kept, and becomes a rule if they choose. Host, reservations manager, management.

Nothing to replace

Your channels, your software and your team stay yours.

Hands folding linen napkins before service
Configuration

Your house, understood.

TableAgent is configured around how your venue actually works.

  1. 01Your house rules
  2. 02Your tone
  3. 03Your seating logic
  4. 04Your booking conditions
  5. 05Your offers
  6. 06Your exceptions
  7. 07What should go back to the team
  8. 08Your guests’ preferences
Under your control
Your team decides what TableAgent handlesEU hostingGDPRMulti-site groups
One decision, end to end

Watch a requestbecome a rule.

Every request follows this path. Those a human decides can become, if they choose, tomorrow’s rules.

  1. 01CapturedAn email at 8:05 pm, in the same queue as the messages: eighteen covers, private hire, Saturday 12 December.
  2. 02UnderstoodA request for the whole room on a Saturday in December, from a contact with no history with the house.
  3. 03DecidedTwo December Saturdays are already privately booked. A third would close the month to regulars. No rule covers this case.
  4. 04Passed onTo the reservations manager, with the December calendar and the deposit terms. The guest is told the house is checking.
  5. 05ExecutedAccepted with a one-third deposit, and written into the booking software.
  6. 06RememberedThe decision is kept. If the team wishes, it becomes a rule: December private hires accepted from twelve covers, one-third deposit.
Its safeguards

It never guesses.It checks, or it hands over.

When a detail is missing or no rule covers the case, TableAgent says so and lets your team decide.

A detail is missing

It flags it and passes it to your team, without assuming anything.

A rule to update

Your team edits or removes it in a moment. The history is kept.

Your software isn’t responding

Your team is alerted at once, and the guest is told the house is checking.

A decision to review

The rule is adjusted. Every change keeps its date and the name of the person who made it.

Its commitments

What it guarantees,and what it leaves to your tools.

It adds to your tools without replacing any. Going live takes one week: see the setup.

  • Always a replyEvery request gets a reply, including one that says the house is checking.
  • Always explainableEvery autonomous action traces back to a rule a human can read.
  • One source of truthThe booking lives in your software. It writes the decisions there.
  • Yours aloneYour house’s rules are yours, and stay yours: they serve your house only.
What TableAgent is not
A booking systemA point of saleA marketplaceA second booking database