Waiter!
I’m used to things being lame. What I’m often confused by is things staying lame. With such rapid progress in technology, culture, and to a lesser degree social and political matters, I find myself just assuming that any particular detail of the human world, given a few years, will always improve. But occasionally, that’s not the case. In particular: why the hell haven’t more restaurants equipped themselves with a method to call for your server?
In software, the terminology for the approaches I’m about to discuss are event-driven and polling. For non-geeks, you might recognize the phrase “Don’t call us, we’ll call you.”
The polling approach - that is, your server coming over to check on your table every so often - sucks for everyone. It’s lame for the server because they make a lot more trips than necessary (you don’t always need something right that minute). It’s lame for you, the customer, in two ways: 1. the server is bothering you when you don’t need them (the proverbial waitress who shows up just as you’ve taken a bite), and 2. they may not come at the moment that you do need something. It’s haphazard, inefficient, and all around dumb.
I’ve been in a few restaurants that take an event-driven approach, and it’s great. One of them, a ribs place in Chino (can’t recall the name offhand) has little flags at each table that can be slid up a pole to call the server. Another, the Russian Teahouse in Glendale, recently added small wireless remotes. You push a button and the servers are alerted somehow, probably a panel of lights or some sort of monitor in the back room. They can sit back and relax when no one is calling them, secure in the knowledge that they aren’t neglecting their customers. And the customers don’t need to tap their foot impatiently, waiting for the server to come back so they can get some napkins to clean up the coffee they just dumped down the front of their date’s shirt, or whatever.
The servers still check on you in these places, but I think that’s because most customers are not yet used to the event-driven approach. Once this becomes more commonplace, though, I would hope that the whole process would get even more streamlined. You would seat yourself, and a server would not even come over until you had pressed the button to summon them, allowing you time to peruse the menu. (Just imagine the energy savings for all the servers of the world if they didn’t have to say the phrase “Do you need a few minutes to look at the menu then?” fifty gazillion times a day.) Then they would not return at all - with the exception of bringing the food when it’s ready - unless you specifically summoned them. That would rule.
May 14th, 2006 1:51 pm
Hi Adam,
I enjoyed reading your entry and the use of software terminology to describe the two different approaches to restaurant customer service.
I offer U.S. restaurants an “event-driven” solution called WaiterBell which is successfully used overseas. We also see the system as a complement to a restaurant’s customary table service, but at the same time giving the customers the option to choose a more event-driven dining experience.
Thank you for your post.
May 14th, 2006 7:17 pm
Nice. This page sums up the whole process pretty succinctly, plus answers the question of what the monitor looks like to the servers.
Randy, do me a favor and have your salespeople call up all the restaurants in the Glendale & Burbank areas of California and get them to buy your product.
May 17th, 2006 12:08 am
We’ll try Adam.
We’re working our way down from the Bay Area. In the meantime, please feel free to write our URL on the receipt
Take care.
June 6th, 2006 1:30 am
Wait.. and then some sort of device that would let people see what the restaraunt sells and for how much so that people could point and grunt at it… but with buttons.