A person asks an agent to book the table. Everything rests on one answer.
People are starting to hand the whole booking to an AI agent. The agent can only commit and pay when the restaurant side is current and committable. Most restaurants are not yet ready for an agent to find them accurately, read their real state, and act with confidence.
A few places look possible, but the outdoor tables and Saturday hours read as hours old. I cannot confirm a table for four at 7pm without the restaurant's own current answer.
The menu on the listing and the menu on the site disagree, and the review counts do not line up. I cannot be confident the vegan mains are current.
Public pages disagree on the cancellation window and on whether a deposit is held. I cannot commit to this booking without the restaurant confirming.
The agent-human transaction
A person delegates the booking. The agent has one question.
The person never sees the work behind the answer. The agent will only commit and pay when the restaurant side is current and committable. Obenan governs that merchant truth and makes the merchant side committable before the agent acts, then hands off to the booking and payment layer.
The person says
“Book me a table for four, 7pm Saturday, outdoor, with vegan options, and a cancellation window I accept.”
The agent asks
Can this merchant commit to this transaction, right now.
Current and committable
A confident yes. The booking can proceed.
Stale or unverifiable
The booking breaks here, after the person thought it was done.
Why dining is first
A table cannot be committed on stale facts.
Dining sits at the front of agent-assisted booking. Assistants already move people from finding a restaurant to holding a table. Every reservation rests on facts that change through the day, and the agent will only act when it trusts them.
Live tables
Availability changes by the minute, not by the day.
Hours and service windows
Kitchen times, last seating, and special days.
Party-size and seating rules
Indoor, outdoor, bar, and minimum spend.
Menu and cuisine
Real dishes, dietary fit, and what is in season.
Reviews and reputation
Current, and from a source the restaurant controls.
Cancellation and deposit policy
The terms a person will actually accept.
The transaction sequence
What happens when an agent is ready to book a table.
Obenan makes the merchant side current and committable. The booking and payment layer handles the reservation and the money. No overlap, no checkout page, no card data.
A person hands the task to an agent
Person and agentThe person delegates the whole booking: a table for four, 7pm Saturday, outdoor, vegan options, and a cancellation window they accept.
The agent asks one question
AgentBefore it can act, the agent needs one answer: can this merchant commit to this transaction right now.
Obenan makes the merchant side answerable
Merchant truthHours, live tables, party-size rules, cuisine and menu, price, reviews, and cancellation and deposit policy are governed and current, with a freshness and confidence signal the agent can read.
The merchant side becomes committable
Merchant truthWhen the table, the policy, and the confirmation path are all current, the question gets a confident yes. If anything is stale or unavailable, it stays discoverable and does not become committable.
The moment a stale answer would have broken the booking.
Obenan makes the merchant side committable, then hands off. No checkout page. No card data crosses this line.
Obenan hands off the current merchant answer
HandoffThe current, committable merchant answer passes to the booking and payment layer the restaurant already uses. The Obenan role ends here. No checkout page. No card data.
The booking and payment layer takes the transaction
Booking and paymentThe booking platform, PSP, acquirer, or card network presents the reservation and the payment step, manages authentication, and handles all card data and compliance.
Confirmation returns to the person
Booking and paymentThe confirmed reservation flows back through the agent to the person. The table is held, and the restaurant is notified through the systems it already runs.
Obenan makes true
Identity, hours, live availability, party-size rules, menu and cuisine, price, reviews, and cancellation and deposit policy, with freshness and confidence.
The payment layer handles
Reservation, checkout, authentication, card data, authorisation, and settlement.
Obenan does not
Process payments, host checkout, handle card data, or replace the POS or booking system.
The same dining request, answered with current merchant truth.
When merchant reality is governed and queryable, the agent stops hedging. It answers with live tables, real menu fit, and a policy a person will accept, the shape a restaurant wants for every agent-assisted booking.
Three nearby places hold an outdoor table for four at 7pm this Saturday. The nearest reserves it until you confirm, checked against the restaurant's live tables under a minute ago.
Two of them list current vegan mains, not just sides, straight from the restaurant's own menu, and the ratings come from the same source the restaurant controls.
Free cancellation until 9am on the day, no deposit held, taken from the restaurant's own policy record. I can hand this booking to the reservation step now.
The merchant layer is not theoretical for us
Already operating the merchant reality layer.
Dining readiness is not a concept pitch. Obenan already governs merchant truth on the public surfaces where agents look, so AI systems can find, describe, and act on a restaurant correctly.
What the operating layer already does in production
Online and offline restaurant truth
One governed record for identity, hours, and service windows that stays true in the dining room and across every surface a guest or agent reaches.
Found and read correctly by AI
Structured so assistants describe the restaurant, its cuisine, and its policy accurately, not approximately.
Merchant-controlled updates across channels
Hours, menu, seating, and policy move from the restaurant outward, continuously, without per-channel rework.
Now extended toward agent-committable dining
Merchant truth exposed in the shape an agent needs before any booking begins.
Clear scope, clear boundaries
What Obenan does, and what Obenan does not do.
What Obenan does
- Keeps identity, hours, and service windows governed and current
- Structures menu, cuisine, seating, and policy for agent queries
- Reflects freshness and confidence in what an agent can rely on
- Gives restaurants a controlled path into agent-assisted booking
What Obenan does not do
- Does not process payments
- Does not host checkout
- Does not handle card data
- Does not replace your POS or booking system
How early participation works
Three steps, no rebuild.
Make the restaurant readable
Identity, locations, cuisine, and hours become governed and queryable.
Make merchant state current
Tables, menu, seating, and policy stay fresh with confidence signals.
Make the handoff clean
Agents reach booking and payment on truth the restaurant already controls.
Early dining readiness partner
The restaurants that shape agent-assisted dining will be the ones moving before the category catches up.
This is not an open sign-up. A small number of restaurant teams will help define how merchant readiness works in practice, and the window to be one of them is the period before the shift becomes obvious to everyone else.
Twelve months from now, the question is not whether your restaurant is agent-ready. It is whether your restaurant helped define what agents can trust.
By industry
Next step
Talk to us about becoming a restaurant an agent can book.
The next conversation is short and specific. Restaurant and hospitality leaders use it to understand where their merchant truth currently sits and what an early pilot could look like.