A Restaurant Owner Told Me: 'I Don't Need a Chatbot.' He Was Wrong.

"My restaurant is full most nights. I don't need a chatbot."

That's what Marco told me when I pitched him. He wasn't wrong about being full. His Italian restaurant in the suburbs had great reviews, loyal regulars, and a waitlist on weekends.

He was wrong about not needing help.

The Numbers He Didn't Know

I asked Marco if he knew how many people visited his website each month. He guessed maybe 100-200.

He checked Google Analytics: 800 visitors per month.

Then I asked how many online reservations he got per month. He checked: about 50.

800 visitors. 50 reservations. Where did the other 750 go?

The Invisible Drop-Off

Marco's website was decent. Nice photos of food, the menu as a PDF, a phone number, and a reservation widget. Standard restaurant website.

But here's what visitors were experiencing:

• They'd check the menu PDF (which took 10 seconds to load on mobile)
• They'd wonder about dietary options: "Do you have gluten-free pasta?"
• They'd want to know about group bookings: "Can you seat 12 for a birthday?"
• They'd check if there's parking nearby
• They'd wonder about the dress code

None of these were answered on the website. The only option was to call - and most people browsing at 9 PM on a Tuesday aren't going to call a busy restaurant.

The Experiment

Marco agreed to try DropBot for a month. "If it doesn't work, I'll remove it."

He added 12 Q&A pairs. The usual stuff plus restaurant-specific questions:

• Do you have vegetarian/vegan/gluten-free options?
• Can you accommodate large groups?
• Do you have a private dining area?
• What's the parking situation?
• Do you take walk-ins or reservations only?
• What's the dress code?
• Do you have a kids' menu?
• Can I see the wine list?

Each answer included a "Make a Reservation" link at the end.

One Month Later

Conversations handled by the chatbot: 127.

Most common question: dietary restrictions (people wanted to confirm before booking).

Second most common: group bookings and private dining.

Online reservations that month: 73. Up from 50. A 46% increase.

Marco did some back-of-napkin math. Average table spend is about $85. Those 23 extra reservations meant roughly $2,000 in additional revenue. For a chatbot he set up in 15 minutes.

What Marco Says Now

"I thought my restaurant was doing fine because the dining room was full. I didn't realize how many people were interested but dropping off before they booked."

He paused.

"The chatbot didn't bring new people to my website. Google did that already. The chatbot just stopped them from leaving."

That's the part most business owners miss. You might not have a traffic problem. You might have an answer problem.