NeverMissed
How an AI receptionist actually takes an order — and when it hands over to a human
Not a demo reel. The actual mechanics of the call: what the AI is allowed to do, what it reads back before it hangs up, and the moments it deliberately stops and gets a person involved.
People assume "AI receptionist" means a chatbot with a voice bolted on, guessing its way through a phone call. It doesn't work like that, and it shouldn't. A takeaway order is a small, specific transaction — items, quantities, collection or delivery, a total — and the whole point of building NeverMissed was to make that transaction reliable, not to make the AI sound impressive. So this is the plumbing: what happens between the ring and the ticket printing in your kitchen, and exactly where the system stops guessing and gets a human involved instead.
The call never leaves your number
Nothing changes for the customer. They ring the number that's on your window, your Google listing and the box on the counter. What changes is what happens when that call isn't picked up in the shop, or the line is already busy. It diverts, in a couple of seconds, to the NeverMissed line, and the AI answers using your shop's name. Some owners choose to have it answer every call as a matter of course; most set it as a safety net for the moments the shop genuinely can't get to the phone. Either way, it's a divert on your existing line, not a new number to advertise, and setting it up takes a couple of minutes with your provider.
The menu is a guardrail, not a suggestion
This is the part that actually matters. The AI isn't reasoning from general knowledge about what a takeaway might sell. It's working from your menu, loaded in with your real items, sizes and prices, and it only offers what's on it. If a customer asks for something that isn't there, it says so and offers what's closest, rather than inventing a dish or a price to keep the call moving. When you change your menu — a price goes up, something's off tonight, there's a new special — you text the change and it's live the same day. That matters more than it sounds: a system that can quietly drift from what you actually sell is worse than no system at all, so the design choice is to keep it boxed in by your real menu rather than clever about working around it.
The whole point of building this was to make the transaction reliable, not to make the AI sound impressive.
Taking the order
A typical call runs in roughly the same shape every time, which is deliberate — consistency is what makes it trustworthy:
- Greeting with your shop's name, and a question: collection or delivery.
- The order itself, taken item by item, with sizes and any extras confirmed as they're added.
- Anything the customer says that doesn't match a menu item gets clarified in the moment, not guessed at.
- A full read-back — every item, the total, and the collection or delivery time — before the call ends.
- The order prints in your kitchen the second the call finishes: name, items, total, time.
That read-back step is the one I'd least want to cut. It's the moment the customer hears their own order said back to them and can correct it there and then, on the call, rather than finding out something was wrong when the food arrives. It slows the call down by a few seconds and saves considerably more time than that in remakes and refunds.
Where it deliberately stops
An AI that tries to handle everything is more dangerous than one that knows its limits. NeverMissed is built to hand over rather than improvise the moment it's out of its depth. In practice that's five kinds of moment:
- An item it can't confidently match. If what the customer describes doesn't clearly correspond to anything on the menu, it says so and takes a callback number rather than guessing at what they meant.
- A complaint or an unhappy caller. Someone ringing about a previous order, or clearly frustrated, gets taken seriously: it takes their number so someone from the shop rings back, rather than talking at them with a script.
- Allergy or dietary detail beyond what's flagged on the menu. A simple "no onion" is fine. Anything that sounds like a genuine allergy concern goes to a person, because that's not a call worth an AI getting confidently wrong.
- A price or payment dispute. Questions about a previous charge, a refund, or "that's not what I was quoted" are handed off rather than argued with.
- A caller who simply asks for a person. If someone says they'd rather speak to someone in the shop, it takes their number for a call back rather than deflecting them.
In every one of those cases the aim is the same: recognise the edge of what the system should be trusted with, and hand it to a human cleanly, with the customer's number, rather than push on and risk getting it wrong with more confidence than it's earned.
What lands in your hand
The output of a successful call is deliberately boring: a ticket prints in the kitchen with the customer's name, the full order, the total, and the time it's due, the moment the call ends. No app to open, no dashboard to check mid-service. If you also want it texted to your phone, or shown on a kitchen screen, that's a setup option, not a different product. The point is that the order arrives the same way whether it's the AI or a person who answered, so nothing changes about how the kitchen actually works.
Why this beats a rushed answer
The honest comparison isn't AI versus a calm, attentive member of staff with nothing else to do. It's AI versus the phone being answered by whoever's nearest, mid-service, half-listening while they plate an order. A rushed order taken standing at the fryer, on a scrap of paper, with no read-back, is where the wrong pizza comes from far more often than a system built specifically to take one order at a time, properly, every time. That's not a claim I can put a precise number on, and I won't pretend otherwise — it's the reason the read-back exists at all, and it's the difference the design is built around.
None of this replaces your judgement about your shop. Some owners want every call answered by the AI; some want it purely as backup for the moments the phone can't be reached. Both are reasonable, and it's a setting, not a rebuild. What doesn't change is the shape of the call itself: your menu, your prices, a clean read-back, and a human the moment it matters.
AVOLUTION.