Regulars Call. Calls Got Missed.
Chef Vola's doesn't take online reservations. Regulars call. Calls got missed, the room's real capacity lived in the owner's head, and nobody kept a record of guests. A booking platform priced by the cover could not fix any of that, because the problem was never the booking form — it was that nobody was answering the phone.
- Requests come in by phone, at any hour.
- The owner checks the app one-handed, mid-service, in a dark room.
- The kitchen can only take so many tables at once.
The Guest Never Sees a Screen. The Owner Never Answers a Phone.
One system, two front doors, and almost nothing shared between how they look. That split is the whole design, and it decided everything after it.
A voice and twelve keys
No app, no form, no link to tap. Everything the guest can do has to be sayable, and everything they hear has to be remembered long enough to answer. There is no back button on a phone call.
One hand, in a dark room
Read at arm's length during service, between tables. Big targets, type that survives a dim room, and every screen opens with the verdict, not with the data you'd have to dig through to get there.
What they do share is the one thing that matters: the same capacity rules. The line reads them mid-call and the app reads them on screen, so a guest and the owner are never told two different things about the same table.
The Conversation Is the Product
The design work was the conversation: which question comes next, what counts as an answer, how long to wait for one, and what the line says when it does not get one.
Every turn the line can take, the keys that move between them, and what happens when a seating is full. Drawn against the running code, not from memory.
Every Line Written, Including the Ones for Going Wrong
A voice interface has no empty state you can look at, so the script is the screen. It carries the prompt, what counts as an answer, how long the line waits, and the sentence it says when the answer does not come — which is most of the writing, because most of a phone call is recovery.
“What time works best, {name}? Enter it, then press pound. For seven o’clock, press 7. For seven thirty, press 7 3 0.”
Not a time “My apologies, I didn’t catch that time. Our seatings run from four thirty to ten P M.” — the correction teaches the range rather than repeating the question.
Silence Asks this question again. It never drops the caller back to the greeting.
Nine turns, each with its recovery lines and the business rules it has to say out loud. Kept against the deployed code — it drifted once, and the drift is noted on the page.
How I Trained It to Listen
A few of these were settled before a line was written. Most were learned from the line getting it wrong, in production, on real calls — a spelled name coming back as “tea” and “eye,” a pocket dial looping all night, a trailing pound landing in the next question. Training a voice is mostly listening to what it mishears, then writing the sentence that fixes it.
- Spoken for the name, the keypad for every number. A phone line mishears digits, and nobody can key a name.
- The alphabet goes in the recognizer’s hints. Callers with an unusual name spell it, and without the letters in there, T A I T Z comes back as “tea,” “eye.”
- The better speech model on one field only. The name is the only answer where a mis-hear books the wrong person.
- Pound means “I’m done” on every question, with no digit cap — so a habitual trailing pound never bleeds into the next question as a stray keypress.
- Silence re-asks the same question. Waiting too long, or a late pound, never restarts the call.
- Longer to answer where there is more to weigh: four seconds for the party size, twelve for the read-back, ten for a list of alternatives.
- The correction teaches instead of repeating. A bad time is answered with the range, not with the same question again.
- The read-back changes its words when the table can be taken on the spot — “to confirm” rather than “a request, not confirmed until we contact you.” The line never promises what it cannot hold.
- A caller who spelled their name hears it spelled back. They spelled it because they expected to get misheard.
- Full is not a dead end: the nearest open times, the waiting list, or another date. No version of that turn ends the call empty-handed.
- Three silent passes and the line says goodnight. A pocket dial used to loop here forever.
The consent line moved too. It used to play the moment someone pressed one, before there was anything to consent to. Now it plays at the close, on every outcome. That is the only version that is true.
Every Request Opens With a Verdict
This is where the owner's half begins. Requests are sorted into open, conflicts, and booked. Each one says whether the time works — open, nearly full, or full — with the tables that would seat the party and other times to offer. A name the line only heard is flagged to check the spelling.
Tonight, and the Room Behind It
The owner can add a walk-in or a call-in from the same screen, and the seating times on offer are the real ones. The room is set in the app — how many tables of each size, night by night — so availability matches the floor, and the phone line inherits it without being told twice.
Guests and Voicemail
Each guest has a private rating, notes like allergies or a favorite table, and their visit history — the record nobody was keeping before. Messages left on the line arrive transcribed, with Call back and Mark handled on the card.
Rules First, Then the Voice, Then the Screens
- Modeled the business rules first: hours, slots, caps, and how a request becomes a booking.
- Worked out capacity in one place, so the app and the phone line give guests the same answer.
- Wrote the conversation before any of it was built, and kept the script against the deployed line afterwards.
- Designed big tap targets and type you can read at arm’s length in a dark room.
- Wrote the specs and made every design call. AI agents wrote the code. I reviewed every screen before it shipped.
The phone line and the iOS app are live. They replaced a $30,000 a year OpenTable contract the owner had been using for the backend only. Every call becomes a request the owner can see, and the room's capacity is written down for the first time.