Concept build. This is internal work by SaltQuill Labs, made to show our approach. The brand is fictional and the figures shown inside the interface are illustrative — but everything pictured is a real, working build you can click through. Nothing here is presented as a client result.
The problem
- Reservations arrived by phone during service, when every hand was busy.
- Cancellations went unfilled because nobody had time to call the waitlist.
- No-shows ran high with nothing reminding guests.
- Regulars' preferences lived in one staff member's memory.
What we built
A 20-second reservation flow
Party size, live time slots, confirm. No account, no app, no phone call.
Confirmation and reminder by text
Sent automatically the moment a table is booked and again on the day.
Waitlist that refills itself
A cancellation is offered to the next party in order, without anyone lifting a finger.
An owner's dashboard
Tonight's covers, deposits, guest notes and waitlist on one screen.
Menu, hours and location marked up
So Google — and AI assistants — can answer questions about the restaurant directly.
What it changes
- Bookings taken without interrupting service
- Cancelled tables refilled automatically rather than lost
- Reminders sent to every booking, consistently
- Guest notes captured at the moment of booking
- Front-of-house attention returned to the room
Under the hood
Custom front end · booking state machine · SMS/email automation hooks · Restaurant & Menu structured data · privacy-safe session analytics
More work: Trades & contractors · Clinics & practices · Freight & logistics · Professional services