The phone line and the QR chat on site
Picking up is the easy part.
The call ends with a time held, an order placed with its options, or a job with a name on it. Anything you have not written down goes to staff.
Request early accessWhat the calls are about
One line. Every kind of call.
Not four kinds of business. One number takes a booking, an order and a job in the same afternoon, and answers questions all day underneath.
Bookings
A place in your schedule. A specific time, or a stretch of days.
Cut and colour
Orders
Things off your list, with the choices that go with each one.
- 1×Margherita· family size
- 2×Still water
Enquiries & Jobs
Something needs doing. They hang up knowing who has it.
No hot water in 204
Outbound
A list of numbers and one thing you want from each call.
Not shipping yet
- Consent attested
- Calling hours set
- Do-not-call checked
Answering questions ships with all of them. It cannot be switched off.
RESERVED · product plate · 2400×1029 (21:9) webp · the operator board with a booking, an order and a job landing in it
Words per turn, median
Words per turn fell from 154 to 90.
Eleven seconds of talking became six. What made calls feel slow was the AI lecturing.
Check it yourself
Asked whether the crown was included, it said no.
It quotes the price exactly from the source, then refuses the follow-up rather than rounding it into a yes.
It reads back what you typed.
Prices and hours come from your own data, never from the model.
It would rather wake a human.
Not in your data means it says so.
What we can stand behind.
Security- Isolation
- Row-level security in the database, not a filter in app code.
- Zero-PII surface
- The QR chat needs no account, no number, no login.
- Provenance, not badges
- Each provider published as measured or undisclosed.
- Answers from your data
- The truth firewall applies on the phone too.