Voice agent · shared state
One brain,
two surfaces.
An AI agent answers the restaurant's phone and books tables. The floor watches those bookings land on screen while the call is still happening, because both are reading the same database.
What happens during the call
The phone rings
A voice agent picks up as the restaurant. It recognises returning numbers and greets them by name.
It checks the floor
Before it promises anything, the agent queries real table capacity for that slot and offers alternatives when nothing fits.
It writes to Postgres
The booking is committed inside a transaction that re-checks availability, so two callers can't take the same table.
The floor sees it
The change streams to the service sheet over Postgres replication. The row lands while the caller is still on the line.
Sixty seconds, one call
A real call to a real number, booking a real table, with the service sheet open beside it.
median tool round-trip — measured across the agent's live calls
Why a shared brain, and not four bots
Calls go unanswered
The phone rings hardest at 7pm, which is exactly when nobody can stop to answer it. Those covers don't come back.
The same table, twice
A booking taken on the phone and one taken by email don't know about each other until two parties are standing at the door.
No single view of the night
The book, the inbox, and the widget each hold part of the truth, and the host reconciles them from memory.
Each of those is the same failure: a booking surface that doesn't know what the others have promised. Fixing it isn't a matter of adding agents. It's a matter of pointing them all at one source of truth.