Every pizza place knows the hour. The line of walk-ins is six deep, the printer is spitting tickets, and the phone starts ringing at the exact moment nobody can pick it up.
Three ways an order dies
The first caller hears a busy signal and calls the next place on the list. The second gets picked up, put on hold, and hangs up after a minute of listening to the kitchen. The third gets through, and the order is written on a napkin by someone with one hand on the register: large pepperoni, extra cheese, two of something. The napkin says two lemonades. The caller said two Cokes.
None of those three is a bad employee. They are what a phone does to a counter at 6:40.
What three at once changes
When the phone is answered by an agent that can hold three conversations at the same time, the busy signal goes away. Nobody waits on hold, because nobody at the counter stops to pick up. The order is taken against the menu, item by item, with the sizes and the choices read back, and it is priced by the menu, not by whoever is writing fastest.
Then it is texted to the caller with the total and the pickup time. The caller reads it, replies YES, and only then does it reach the kitchen, as a tile on the screen by the pass with the name, the time, every change, and a timer that turns red if it sits too long.
What the counter gets back
The people in front of them. The Friday rush does not get smaller, but the phone stops being a third line that nobody is staffed for. The orders that used to go to the next place on the list come in, and the napkin goes back to being a napkin.
If you want to hear what that sounds like, call the demo restaurant from your browser. It knows its menu, it will take your order, and the text will land on your screen when you hang up.