A Restaurant Owner Asked Me to Automate His Bookings. I Ended Up Changing His Whole Week.

He called me because he was tired of answering the phone.

Not in a rude way. He loved his restaurant, loved his customers, loved what he had built. But the phone rang constantly. Reservations, cancellations, people asking if they could bring a dog, people asking about the menu, people calling to say they were running 10 minutes late. From 11am until close, the phone was always ringing.

Him or one of his staff was always dealing with it. Nobody could focus on anything else. The person taking a booking was the same person who should have been training the new chef or doing the end of month accounts or just having a quiet moment to think.

We started with bookings because that was the most obvious thing. But here is what most people get wrong when they try this themselves: they bolt a system onto their existing chaos. They add a tool without changing the process. So they get a booking form on their website, but it dumps everything into an email inbox that nobody checks, or worse, into a spreadsheet that gets out of sync with reality.

What we did was different. We built it step by step. First, I met with him and his team for two hours. Not to sell them something. To understand. I watched them take reservations the old way. I saw where they wrote things down (on paper scraps), where they double-booked tables (Tuesday evenings were chaos), where they lost information (cancellations that came through via text messages to the manager's phone). I saw that they had no way to know if someone had called three times to modify their booking.

Then we built something simple. A booking form on their website that connected to a calendar. People could see real-time availability. No more "let me check and call you back." The system sent automatic confirmations by email and SMS. The day before the reservation, customers got a reminder. And here is the part that matters: if someone needed to reschedule or cancel, they could do it themselves through a link in that reminder. The table went back into the available slots immediately.

The second piece was training. Not a two-hour training where everyone forgets everything. But small things. I showed the host how to handle the few edge cases the system could not solve alone. I showed the owner where to find the reservation data if they needed it. I answered questions for the first three weeks whenever they came up. People resist automation because they are afraid they will break something. My job was to show them I had their back.

Phone calls dropped by about 60 percent in the first month. That was good. But then something else happened that I did not expect.

He started taking Wednesday afternoons off.

He told me this about two months in. He said he had not had a Wednesday afternoon to himself in six years. Six years of being in that building every single day. But now that the team was not constantly interrupted by the phone, they could actually run the lunch service without him there watching everything. His front-of-house manager had time to train new staff properly. His head chef could focus on the line instead of being interrupted by "can we accommodate this large group next Friday?" His accountant could actually get an answer from him about invoices instead of just getting voicemails.

So he started leaving at 2pm on Wednesdays.

He said he goes to the market. Walks around. Finds ingredients he wants to cook with. Gets ideas. He said some of his best new dishes have come from those Wednesday afternoons. More importantly, he said he remembered why he had opened a restaurant in the first place. Not to answer phones. Not to apologize for overruns. But to cook. To create. To connect with people through food.

Within six months, I noticed other changes. The reservation cancellation rate went down. When people book online and get a confirmation and a reminder, they actually show up. He had more predictable staffing because he knew three days ahead exactly how many covers each service would have. His team morale improved because nobody was burned out from constant interruptions. He even started a loyalty program for repeat customers, something he said he never had time to think about before.

Here is the mistake I see most restaurant owners make: they think automation is about doing more. Opening more tables. Taking more reservations. Squeezing more profit out of every hour. That is the wrong approach. Automation is about reclaiming time. About choosing what matters instead of letting urgency choose for you.

I did not overcomplicate this. We did not add a phone bot that confused customers. We did not integrate seventeen different systems. We built one thing well and we made sure people understood it. Start small. Measure what changes. Then decide what is next.

That is the thing about this work that I did not fully understand when I started fifteen years ago. You think you are solving a problem. And you are. But sometimes what you are really doing is giving someone space. Space to think. Space to be creative. Space to remember why they started the thing in the first place.

The phone is still there. It still rings sometimes. But it does not own him anymore.

That is what I am really building. Not workflows. Not automations. Not integrations. Space. For people who have forgotten what it feels like to have some.

Questions I hear a lot:

What if customers prefer calling? Some do, and that is fine. The system handles 60-70% of booking requests online. The remaining 30-40% that need a phone call are actually easier to handle now because the team is not drowning in simple requests. Plus, the calls that do come in are usually from customers who have genuine needs: large groups with special requests, accessibility questions, or dietary concerns. Those calls actually matter.

Doesn't automation cost a lot to set up? It depends on what you automate, but for booking systems there are now solid, affordable platforms that cost less than hiring someone part-time to answer phones. What costs more is doing it wrong: building something complicated, not training your team, and then watching them go back to the old way because they don't trust the new system. Do it simple. Do it right. Do it gradually.

What if I want to add more later? You will. And that is when you make changes. But start with the bottleneck that is actually killing your time. For restaurants it is usually reservations. For other businesses it might be email, scheduling, or data entry. Fix that first. Watch what happens. Then the next priority becomes obvious.