Graveyard Shift Digital

Home › Free guides

The Best Chatbot for Restaurants Answers the Phone at 7 PM on a Friday

A restaurant lives or dies on Friday at 7 PM. The host stand is three deep, the phone is ringing, and every caller wants the same five things. How long is the wait. Do you have a table for six. Is the patio open. Do you take reservations or is it walk-in only. A chatbot that cannot answer those five in under ten seconds is decoration.

The real questions are messier than people expect. Guests ask about the gluten-free options, and they mean it, because one of them has celiac. They ask if the fryer is shared. They ask whether the patio is dog friendly, whether you validate parking, whether the private room holds fourteen people for a birthday, and whether you sell gift cards in denominations that do not exist. A good bot knows the actual answers. A bad bot invents a brunch menu you stopped serving in March.

Allergy handling is where most restaurant bots quietly fail. The bot should list what you actually offer and then hand the hard questions to a human. It should never promise a dish is safe for someone with a severe allergy. That line has to be written into the bot's behavior on purpose, not left to chance, because a confident wrong answer about peanuts can end in an ambulance.

Reservations are the second trap. If you take bookings through OpenTable, Resy, or a phone list, the bot should push people to that one place and stop. Bots that try to "hold" a table in chat create double bookings and angry regulars. The job of the bot is triage, not the reservation book. Take the party size, the date, and hand over a link. Done.

Menu prices are the third trap. Restaurants change prices more than any other small business. If your bot quotes $18 for the salmon and the menu board says $22, you have a guest who feels lied to before they sit down. Whoever runs the bot has to update prices the same day the menu changes, or the bot should not quote prices at all and should send people to the online menu instead.

The best restaurant chatbots do a few unglamorous things well. They quote the current wait during rush. They answer hours, including the holiday hours that always confuse people. They handle the catering inquiry with a real form instead of a dead end, because a corporate lunch order is worth forty covers. They know the difference between the lunch menu and the dinner menu. And at 11 PM when someone asks if the kitchen is still open, they give a straight yes or no.

Takeout and delivery are their own world. Guests ask whether you deliver directly or only through the apps, what the delivery radius is, and why the DoorDash menu has different prices. If you run direct online ordering, the bot should push people there, because every order that skips the app's commission is found money. If you do not deliver, the bot should say so in the first reply instead of letting someone build a whole cart and find out at checkout.

Large parties and private events deserve their own handling. A table for twelve is not a reservation, it is a negotiation: set menus, deposits, room fees. The bot should collect the date, headcount, and occasion, then hand it to whoever books events, with the details attached. Same with gift cards. People ask about them every December. The bot should say where to buy them and whether they work for catering.

Set it up for the Friday rush and it pays for itself by the second weekend. Set it up to sound clever and it becomes one more thing the host has to apologize for. If you want to build it yourself this weekend, the AI Chatbot Launch Kit walks you through it: https://graveyard-shift-digital.pages.dev/store/

Want this handled?

Not into tinkering? There's a $99 done-for-you version of everything this guide covers. One email, a few answers from you, and it's live on your site.

More free guides