Agent template
Takes bookings and deposits, handles cancellations and refunds, and asks the owner when a decision is theirs. The example shop is a salon on WhatsApp.
Agents that handle bookings and money meet these. A rule written in a prompt is a suggestion.
Told “booked”, but the calendar is empty
The calendar save failed silently. The agent still said booked.
Not booked until the calendar shows it
“Booked” only when the calendar shows it. If the save fails, the customer isn’t told “booked”, the owner gets a one-word retry, and the deposit stays on record.
The customer paid twice
A reply from the payment service gets lost, so the agent sends a second link, and the customer pays both.
One link, one payment
One link per booking, even when a reply is lost. If a deposit is paid twice anyway (two phones), the second payment is refunded and the owner is told.
Two people, one chair
Both are told “Booked!” One of them arrives to a full chair.
One slot, one customer
The slot is held in the calendar while the first customer pays. The second is told that time is taken and asked for another.
₹150 below your price
“My friend paid ₹300.” The agent agrees, because the price was a sentence in its prompt.
Asked twice. The price held both times.
The price floor sits outside the AI. Below ₹450 the answer is no. Refunds above the owner’s limit, or after a late cancellation, wait for the owner’s OK.
Vibe-code the agent. Geometer checks it and holds the limits.
Each line is a limit in the shop’s settings or a check against the records, outside the AI.