The real problem: missed calls and messages during peak season

In winter, a Costa del Sol restaurant can run perfectly well with a small team and the owner on the floor. There's time to answer the phone, reply to WhatsApp messages and handle reservations manually. The volume is manageable.

June arrives and the first tourists follow. By July and August, the restaurant goes from 30 covers to filling 80 every evening, with a waiting list at weekends. That's when things start to break down:

  • The phone rings during service and no one can answer it.
  • WhatsApp messages pile up until someone has a free moment — which is sometimes too late.
  • Reservations that do get confirmed often have no reminder sent, so the no-show rate climbs.
  • Large groups — families of eight, corporate events — need disproportionate amounts of coordination time.

According to TheFork, the average no-show rate in Spain settled at around 3.3% in 2025. That average stays low thanks to active no-show policies: in high season with no reminders at all, many Costa del Sol restaurants see it climb to 8-12%. For a venue with 80 covers across two sittings, a 10% rate means roughly 16 empty seats per night that could have been reallocated.

What a WhatsApp booking automation actually does

A well-built automation isn't a chatbot that replies "hello, how can I help you?". It's a system that understands context, manages the conversation and closes the booking without anyone on the team having to intervene — except in genuine edge cases.

The basic flow works like this:

WhatsApp booking flow

01Customer messagesRequests a table on WhatsApp: date, party size, preferences.
→
02AI processesInterprets the request and checks real-time availability.
→
03Diary / PMSBooking registered directly — no manual copying.
→
04Confirmation sentAutomatic message with booking details and cancellation policy.
→
05ReminderAlert 24 h and 2 h before. Customer confirms or cancels from the message.
From message to confirmation — no team intervention at each step
  1. The customer writes on WhatsApp — could be "I'd like to book for two on Saturday" or something informal like "hi, do you have a table tomorrow evening for four?".
  2. The AI processes the request — identifies date, party size, special preferences (terrace, inside, allergies) and checks real-time availability against your booking system.
  3. It proposes options and confirms — if there's availability, it confirms the booking directly. If not, it offers alternative times or dates and asks if they'd like to join a waitlist.
  4. It sends a confirmation with all details — name, date, time, party size and the cancellation policy if the restaurant has one.
  5. It sends automatic reminders — typically 24 hours and 2 hours before the sitting. The customer can confirm or cancel directly from the message.
  6. It manages cancellations — if someone cancels, the system frees the slot and can automatically offer it to customers on the waitlist.

Key figure: With well-configured automated reminders, no-shows can drop noticeably compared to sending no reminder at all. For a restaurant with 80 covers during high season, recovering even some of those seats each evening has a direct impact on revenue.

Integration with TheFork and CoverManager: no need to start from scratch

This is where many restaurant owners hesitate: "I already use TheFork — do I have to change everything?" The answer is no.

The automation acts as a layer on top of whatever system you already use. TheFork and CoverManager remain your booking management platform, with their own apps and dashboards. What we do is connect WhatsApp to that availability database so that bookings arriving through that channel are registered directly, without anyone having to copy them across manually.

The integration stack — without changing what already works

TheFork and CoverManager connect via API on top — no data migration. Representative platform logos for the hospitality sector.

Practical differences between the two platforms:

  • TheFork: Has a public API and is the most widely used on the Costa del Sol. Webhook integration is straightforward. The catch is that TheFork charges a commission per cover for bookings managed through their platform, so some restaurants prefer to handle direct WhatsApp bookings outside their system — using a separate calendar (Google Calendar, Airtable or similar).
  • CoverManager: Designed specifically for higher-volume restaurants. It gives more control over table management, waitlists and analytics. Its API integration is more comprehensive. If you're already using it, connecting with WhatsApp Business API is the cleanest route.

If you're not using either, the simplest starting point is connecting WhatsApp to a shared Google Calendar that acts as your reservations diary. It's not the most powerful setup, but it works and is quick to implement.

Keeping it personal: how AI can sound like you

The biggest fear when restaurant owners hear "chatbot" is that customers will notice they're talking to a machine and feel the restaurant has become impersonal. That's a legitimate concern, especially on the Costa del Sol, where quality tourism expects a personalised experience.

The answer lies in the conversation design. A well-configured system:

  • Uses the customer's name from the first message if they're a returning guest.
  • Adopts the restaurant's tone — a casual beach bar in Torremolinos is a very different voice from a Michelin-starred spot in Marbella. The message templates are written accordingly.
  • Knows when to hand off to a human: if the request is ambiguous, if the customer seems frustrated, or if there's something the system genuinely can't handle (a private event with a bespoke menu, for example), the conversation passes to the team with full context already visible.
  • Doesn't spam: proactive messages (reminders, waitlist updates) are sent at sensible intervals, not aggressively.

Most customers who book via WhatsApp have no idea whether there's a person or a system on the other end. What they notice is whether they get a quick response and whether the booking is handled properly. That's what matters.

A day in service — bot active 24 h

09:00First messagesWhatsApp starts receiving requests. Bot replies instantly.
→
13:00Lunch serviceTeam on the floor. Bot keeps closing bookings without interrupting.
→
14:0024 h reminderAutomatic alert for tomorrow's bookings. Customer confirms or cancels.
→
20:00Evening serviceTeam on the floor. 2 h reminder sent. Waitlist managed automatically.
→
23:00Bot still activeAccepts bookings for tomorrow. Team rests.
Team steps in only for edge cases — bot handles the rest

Common mistakes when setting this up

After seeing how this plays out across various hospitality businesses, these are the mistakes that come up most often:

  • Starting with the wrong channel. WhatsApp Business API requires a dedicated phone number and Meta approval. Many restaurants try to use their existing number, which already has the personal WhatsApp app or the free Business app. This needs to be clear from the start: API and the free app are not the same thing and are not interchangeable.
  • Not defining the business rules. The system needs to know what to do in every scenario: what's the cut-off time for same-day reservations? Is there a cancellation policy, and from when does it apply? Do you accept a waitlist? What happens with groups of more than eight people? If these aren't defined, the system will make default decisions that don't match how the restaurant actually operates.
  • Ignoring language. On the Costa del Sol, customers write in Spanish, English, German, French and sometimes other languages. The system needs to be set up to reply in the customer's language from the outset, not always in Spanish. AI handles this well when it's configured correctly from the start.
  • Not reviewing the metrics. Once live, the system generates data: how many bookings are handled automatically, how many escalate to the team, what's the confirmation rate on reminders, how many customers cancel after the 24-hour reminder. Without reviewing those numbers, there's no way to improve.

Before and after automating

Without automation
  • ✕Calls go unanswered during service
  • ✕WhatsApp backlog until closing time
  • ✕No reminders — high no-show rate
  • ✕Empty seats that could be reallocated
  • ✕Large groups eat up disproportionate staff time
With automation
  • ✓Instant reply, 24 h a day
  • ✓Booking closed on the spot
  • ✓Auto 24 h reminder — fewer no-shows
  • ✓Active waitlist managed automatically
  • ✓Team free to focus on the floor
Impact of automation on WhatsApp booking management

Where to start: a four-step process

If you want to implement this at your restaurant, the natural order is:

  1. Get a WhatsApp Business API number. You need an official Meta partner (BSP): 360dialog is the most cost-effective starting point, Twilio is more robust for high volumes. Meta's approval process takes between 3 and 10 working days.
  2. Define your business rules. Booking hours, minimum and maximum group sizes, cancellation policy, the maximum response time you're comfortable with before escalating to the team.
  3. Connect to your booking system. TheFork, CoverManager, Google Calendar, or whatever you use. This is the technical part we handle.
  4. Design and test the conversation flows. Write templates in your restaurant's voice, configure the reminders and test the system before peak season arrives. August is not the time to be troubleshooting technical issues.

Launch checklist

  • ✓WhatsApp Business API number approved by Meta (BSP: 360dialog or Twilio · 3–10 working days)
  • ✓Business rules defined — hours, group sizes, cancellation policy, waitlist
  • ✓Connected to TheFork, CoverManager or Google Calendar (no data migration)
  • ✓Conversation flows tested before peak season, in the restaurant's voice and multilingual
The four steps to complete before going live

Is your restaurant on the Costa del Sol?

At Zerolagia we configure WhatsApp booking systems tailored to local hospitality, with integration into TheFork, CoverManager or your current setup. Without changing what already works.

Let's talk — no commitment

Frequently asked questions

Can I automate WhatsApp bookings if I already use TheFork or CoverManager?

Yes. The automation sits on top of whatever system you already use. TheFork or CoverManager remain your booking management platform, but the WhatsApp conversations with customers and automated reminders are handled by AI. Nothing needs to be changed or migrated.

Does automating WhatsApp make the service feel cold or robotic?

It depends on how it's set up. A poorly configured chatbot sounds like a machine. But with AI trained on your restaurant's tone and message templates personalised with the customer's name, most diners can't tell whether there's a person behind it or not. The design of the conversation flow is everything.

How long does it take to set up an automated WhatsApp booking system?

For a single-location restaurant, between one and three weeks from initial contact. The main bottleneck is usually Meta's approval process for the WhatsApp Business API account, which can take several working days.

What happens when a customer makes a special request the bot can't handle?

The system is designed to escalate to a human when it detects a complex or ambiguous request. The bot handles 80–90% of standard conversations and passes the rest to the team with full conversation context, so staff don't have to read everything from scratch.

How much does a WhatsApp booking automation cost for a restaurant?

Cost depends on message volume and the level of integration required. For a mid-sized restaurant on the Costa del Sol during high season, monthly tooling costs typically fall between €80 and €200, plus initial setup. The return from recovered bookings and reduced no-shows usually covers the investment within the first month of peak season.

You might also like

Automation for hospitality on the Costa del Sol All articles