AI phone answering
the phone answers itself.
in your name.
every call is three minutes of someone not cooking, at rush. when nobody picks up, that customer orders somewhere else tonight. this answers in your name, takes the order from your menu, and prints it in the kitchen.
live on our demo restaurant's line today · English today · you keep your number
how a call goes
it sounds like your counter on a good day.
it knows your menu, your hours, and your name. it asks the questions your staff would ask, reads the order back, and hangs up with a name and a pickup time. the ticket prints in the kitchen the moment the caller says yes.
- 📞answers in your name. your restaurant, your hours, your menu. no hold music, no voicemail at rush.
- 🧾takes the order from your menu. items, sizes, spice level, special requests. it reads it back before it confirms.
- 🖨️prints in the kitchen. the moment the caller confirms, the ticket is on the handheld, marked as a phone order.
- 📋leaves a name behind. the caller's name and number are on the order, and on your list.
an illustrative call. the real line's wording varies. a ticket for this order is what's printing in the photo above.
what it does today
here's the honest list.
the parts that work, the parts that are built but waiting, and the parts it doesn't do yet. we'd rather you read this than find it on a Friday night.
the checklist
checked against the demo line on 2026-09-05.
| answers in your name, with your hours and menu | yes |
| takes items, sizes, spice, special requests | yes |
| reads the order back before confirming | yes |
| prints the ticket in the kitchen at confirm | yes · about 2 seconds |
| caller pays at pickup | yes |
| texts a link to pay ahead | built · waiting on carrier approval |
| combos that need two choices at once (“half and half”) | not yet |
| hands the call to a person on request | not yet |
| languages | English today |
what you see
one switch in settings. the line, the greeting, the voice. phone orders land in the same queue as everything else, marked as phone orders.
where it stands
it takes real calls. real orders print.
- live on our demo restaurant's line since August
- real calls from real phones, about three minutes each. the order is on the kitchen printer within seconds of the caller saying yes
- when a call hit a menu item it couldn't match, we fixed it the same day. that's how it should work
- call it yourself. the number is right here
demo restaurant, checked 2026-09-05.
a fictional chicken-and-pizza joint in Koreatown. order something. the ticket prints on our desk, and nobody cooks it.
three questions owners ask
“my customers want a real person.”
some do, and today the line can't hand a call over. that's on the honest list above. what it does well is the call nobody was going to answer: the one that comes in at 6:40 on a Friday while everyone is cooking.
“what if it gets the order wrong?”
it reads every order back before confirming, and it only takes items that exist on your menu. if it can't match what the caller said, it says so and offers the options. every call is logged next to the order it created, so you can check.
“do I need a new phone number?”
no. you keep your number. we set up a line for the AI and you forward to it when you want it answering: rush hours only, or all day. turn it off and your phone rings like before.
what we do with you
a paid add-on. you set the terms with us.
this isn't part of the standard setup. if you want it on your line, say so. we load your menu, record your greeting, run test calls with you, and you keep your number.
- we load your menu and hours
the same menu your ordering site uses, with how your staff say the dish names - test calls, together
you call it, you try to break it, we fix what breaks - forward your line when you want
rush hours first. all day if you like it
want to see your restaurant on it?
tell me your restaurant's name. I'll send back a sample ordering page with your logo and info. no meeting, no sales call.
get your free demolive on our demo restaurant's line today