Online reservations for your restaurant: less WhatsApp, fewer empty tables
Online reservations keep you from losing tables because you couldn't get to WhatsApp during the rush. Describe your restaurant to Proyecta and out comes a page with a reservation form, published this same week, no agency and no third-party apps.
It’s 2:30 in the afternoon. The kitchen is slammed, you’ve got eight tickets going, and your phone won’t stop buzzing. “Do you have a table for 6 on Saturday at 9?” You see it 40 minutes later, once the rush dies down. You reply. No answer. They already booked somewhere else.
An online reservation is exactly that: a form on your own page where the customer picks the day, the time, and the party size, and the table is held without you having to be glued to the phone. It’s not that WhatsApp is bad — it’s that WhatsApp is a conversation, and what you need is a schedule. Conversations need you to be there. A schedule doesn’t.
The problem isn’t the phone, it’s that a table doesn’t come back
A shirt you don’t sell today, you sell tomorrow. A table sitting empty on Saturday at 9 pm never comes back. That slot is just gone.
That’s why a missed reservation stings so much, and why notebook mistakes cost more than they look like they do:
- You reply late. The customer asks at 2:30, you see the message at 3:10. By then they’ve already asked two other places.
- You said yes and didn’t write it down. They show up at 9, there’s no table, and now you’ve got a problem in front of other customers.
- You don’t know how many tables are already booked. To figure out how Saturday looks, you have to scroll through three different chats.
- Double booking. Two people, same table, same time. Someone’s going to be upset.
- The 11 pm question. Someone’s deciding where to have dinner on Friday while you’re asleep. A notebook can’t catch that. A page can.
That last point is the one that convinces people: the page works when you can’t.
What does a reservations page actually need to be useful?
You need five things — not an expensive restaurant-grade system.
1. Party size. 2, 4, 6. Anything above 8, have them call you — those need special seating arrangements, and you’re the one who knows how to handle that, not a form.
2. Day and time — but only yours. This is the important part: don’t set up an open calendar. If you’re closed Mondays, Monday shouldn’t show up as an option. If your last table seating is 9:30, don’t offer 10:30. A time slot you offer but don’t actually have is worse than not offering online booking at all.
3. Name and phone number. Nothing else. No “create an account,” no password, no email confirmation. Every extra field loses you people. Name and phone, done.
4. Instant confirmation. The customer needs to see “confirmed: table for 4, Saturday 9:00 pm” on the screen and get a message. If you don’t confirm it, they won’t trust it, and they’ll call you anyway to double-check — and then you haven’t gained anything, you’ve just got both.
5. It has to land where you actually check. The reservation should hit your WhatsApp or your email. If you have to log into a dashboard to see them, you’re not going to check it. You know that, and so do I.
How do you set up online reservations for your restaurant this week?
You describe your restaurant to Proyecta the way you’d explain it to someone over the phone, and out of that comes a real, published page, with its own link and its own reservation form.
I have a restaurant called La Parrilla de Anita, in Monterrey, Colonia Del Valle, Río Missouri 340. It’s a grill, steaks and cuts. I’m open Tuesday to Sunday, 1 pm to 11 pm; closed Mondays. I have 12 tables: eight for 4 people and four for 2. I want people to be able to book online by choosing day, time and party size, in 30-minute slots from 1 pm to 9:30 pm, which is my last seating. Groups of more than 8 should call me at 81 1234 5678. I want the reservation to reach me on WhatsApp. And it needs to look good on mobile.
That’s the same link you put in your Instagram bio and send to anyone who asks.
If something doesn’t feel right, you just say so: “the last seating should be at 9, not 9:30,” “take out Sunday nights.”
What mistakes cost you reservations?
The one that costs the most is offering time slots you don’t actually have: the customer books for 10:30, you close the kitchen at 10, and now you have to call and cancel. You’ve lost the customer and you’ve also looked bad. It’s better to offer less than you can deliver.
Asking for too much information. Every field is someone dropping off halfway through. Name and phone number.
Not confirming. Silence makes the customer book somewhere else too, just in case. Then they don’t show, and you’re left holding an empty table.
Not accounting for no-shows. People don’t show up because they forget, not because they’re rude. A same-day reminder — “we’ll see you today at 9, La Parrilla de Anita” — cuts no-shows quite a bit. It’s not magic, it’s just a memory jog.
When do you NOT need online reservations?
You don’t need them if you’ve got six tables and people just walk in, sit down, and eat. You don’t need them either if you’re a quick-turnover spot — tacos, tortas, comida corrida —: nobody books ahead for tacos.
They’re worth it when Saturdays fill up and you’re turning people away, or when your average check is high enough that an empty table really stings. If you’re not in either of those situations, skip it: focus on your menu, your address, and your WhatsApp button being solid. That’ll get you further.
How much do online reservations cost for a restaurant?
The page itself: nothing. The only optional cost is your own domain, which runs somewhere between 200 and 500 pesos a year — start with the free link you get and buy the domain once you see people actually using it.
Compare that to the alternatives: an agency will charge you 8,000 pesos and up, then charge you again every time you change your hours. Reservation platforms charge a monthly fee or a per-cover fee — which can make sense if you’re a big restaurant, but for 12 tables, that’s paying for something you can just have yourself.
The phone test
Before you publish, open it on your phone and book a table yourself, as if you were the customer:
- Did I book in under 30 seconds?
- Did I only see time slots I actually have?
- Did the customer confirmation come through?
- Did I get the reservation, somewhere I’ll actually see it?
- Can I read it without zooming in?
- Does Monday show up blocked, since that’s my day off?
If all of that checks out, publish it.
Wrapping up
Next Saturday you’re going to be in the kitchen, not on your phone. The question is whether that Saturday’s reservations are booking themselves — or walking across the street to your competitor.
Describe your restaurant to Proyecta, see what comes out, and publish it if you like it. If it doesn’t convince you, don’t publish it — but at least now you know how long it takes to find out.