Restaurant terrace season 2026: why your +30% covers triple your lost bookings

“We just had our best week of the year, and I spent every service with the phone in my hand.” That is a terrace owner, late June, on a Monday morning call with me.

I hear it every summer, almost word for word. Always with the same pride and the same exhaustion in it.

The terrace opens, covers go up 30%. Nobody warns you that requests climb a good deal faster than that. Or that a large share of them will never get an answer. Here is where they go, what it costs over a season, and how you close the tap.

€12,936 per summer. The average value of terrace requests lost over a 4-month season for an 80-cover city-centre restaurant.

Why your terrace multiplies requests, and misses them

The moment the thermometer passes 22°C, your book switches worlds. Tourists, last-minute afterworks, spontaneous birthdays, walk-in groups. It all lands on the same day.

And it all lands at the worst moment. The phone rings while you are on the floor. Instagram DMs pile up at peak. Emails arrive at 11 pm, after you have closed. The weather flips in 6 hours and sends you 25% more requests than you planned for.

• A spike in inbound requests between June and August, well above the annual average
• 62% of restaurant calls go unanswered in this period (Heep, 38 restaurants tracked, summer 2025)
• 25% demand swing over 6 hours depending on weather (Heep observations, typical summer weekend)

The 3 leaks that cancel out your +30%

On a terrace, requests do not get lost at random. They get lost in the same three places, every time.

• The evening leak. 71% of calls placed after 8 pm are never returned. Yet that is the slot where couples decide “hey, let us try a terrace tomorrow”.
• The multilingual leak. One in three tourists writes in English, Italian, German or Spanish. Without a reply in their language within 5 minutes, they go next door.
• The weather leak. A shower at 6 pm triggers 40% cancellations on the terrace. With no follow-up, those tables stay empty, even though your lunch waitlist wanted to come back for dinner.

The exact bill: €12,936 vanished per summer

I am not here to sell you a spreadsheet. But the maths fits in three lines, and it is worth doing once. 80-cover restaurant in a tourist district, open 6 days a week from June to September.

• 28 inbound requests per day (all channels: phone, DM, WhatsApp, email)
• 11 requests lost daily (39% no-response rate on average)
• €35 average ticket per lost cover (INSEE Commercial Catering 2024)

Over 120 summer days: 11 lost requests × 2.8 average covers × €35 = €12,936 left on the table. Not counting the word-of-mouth, or the regulars who never became regulars.

You already know what it looks like on the team side. The waiter takes calls between services. Instagram DMs get read the next day. Emails sleep for eighteen hours. Groups call three times before they reach anyone. +30% covers served, and a brigade that ends the season flat.

How many terrace requests slip past you every day, in your own venue? Estimate your recoverable volume

The system that closes every request, 24/7

Heep replies for you on WhatsApp, Instagram DM, email and SMS, and recovers your missed calls by message. In English, French, Italian, German, Spanish, Japanese: in whichever language the guest writes.

Across a terrace season, three of those things matter more than the rest.

• Missed-call recovery. Every unanswered call gets a WhatsApp within seconds, or an SMS if the number is not on WhatsApp. The conversation continues in writing and the booking is written into your Zenchef, SevenRooms or TheFork.
• Weather follow-up. When the shower lands and the cancellations come in, the freed-up slots go back out to your waitlist. One table of 4 recovered is €140 that is not lost.
• Multilingual handover. A tourist writing in Italian gets an Italian reply, in under a minute.

One objection comes up in every training session: “my team won't keep up with that on top of service.” They have nothing to keep up with. They open the inbox when a request is handed to them, and only then.

Case study

92-cover bistro, Le Marais: a terrace season with no lost enquiry

Before Heep: a dozen terrace requests lost every day between 7 pm and 11 pm. After setup: every request gets a reply, the ones outside the rules go to the team, and extra bookings show up daily. The revenue attached is estimated at your average spend, on your own volumes.

• A summer with no lost enquiry on the written channels
• 0 extra hires
• A few days go-live timeline

Your 4-step action plan

1. 15-min terrace audit.

   Count your missed calls over 7 days (carrier report), your unread Instagram DMs, your unanswered emails.

2. Connect your channels.

   Missed calls forwarded to Heep, WhatsApp Business, Instagram DM, work email. No technical work on your side.

3. Brief Heep in 30 min.

   Menu, opening hours, house rules, closing days, group policy. One video call is enough.

4. Switch on terrace mode.

   Waitlist, follow-ups after a cancellation, multilingual handover. Measure impact from week 1.

If you only do one thing after reading this, do the first one. Ask your carrier tomorrow morning for the log of your last seven days, and count the unanswered calls between 7 pm and 11 pm. It is free, it takes fifteen minutes, and you will finally know what we are talking about. After that, look at the no-show cost calculator or at how Heep answers every email request in under a minute.