
Luc Fernandez
Co-founder, sales and customer supportHe is usually the one who connects your restaurant, trains the floor team and answers when you write in. He runs support Monday to Friday.
We spent years inside restaurants and groups, watching the same bookings slip away in the middle of service. We built Heep for exactly that.
Heep started at Fyce, the collective we worked with on the acquisition, the tools and the data of restaurants and groups. Everywhere, the same problem.
Calls missed during service. WhatsApp and Instagram messages read too late. Group enquiries left without an answer. Bookings lost without anyone noticing.
Not because the teams are careless. Because they are doing their job: they are on the floor, with the guests who are already there.
So we built Heep. An assistant that answers your guests on WhatsApp, text, Instagram, Messenger or email when you cannot, writes the booking into your software and hands you the wheel the moment it matters. Without changing the way your restaurant already works.
Independent restaurants and groups running several addresses, in France and abroad.
Heep does not replace your team. It takes the requests they cannot take, at the moment they cannot take them.
A missed call, a WhatsApp or Instagram message, an email: Heep replies within seconds, in the guest's language, with the details of your restaurant.
Guest messagingThe booking is written into your software, whether that is Zenchef, SevenRooms, TheFork or another. Date, time, covers, the guest's notes.
BookingsYou choose what Heep handles alone and what it passes on. Large tables, allergies, complaints: your team picks the thread back up with one tap.
What you keep in handCalls recovered, bookings, revenue estimated: you see what Heep brings back, per venue and across the group.
The analyticsThe same people run the demos, the onboarding, the support and the product. What you tell us in a demo goes straight to the people building Heep.

He is usually the one who connects your restaurant, trains the floor team and answers when you write in. He runs support Monday to Friday.

He decides what Heep does and what it does not do. What you ask us for goes through him before it becomes a feature.

He builds the platform and its connections to reservation software and messaging channels. He is the one who decides where the automation stops.

He is the one you meet on the demo call. He starts from your reservation software and your channels before talking about Heep.
Everything we build comes out of real services, in real restaurants. Not out of theory.
Heep is designed around what actually happens during service, not around what software imagines. Every feature starts with a restaurateur asking for it.
We work on what saves time and generates bookings. Not on options nobody uses.
Heep supports your teams, it does not replace them and it does not get in the way of service. You keep the wheel: time windows, thresholds, handover to the team.
A setup you can read, honest answers about what Heep does and does not do, no hidden logic. When there is something we cannot do yet, we tell you.
Independent restaurants and groups running several addresses, in France and abroad. The case studies show what it looks like during service.
No. Heep takes the requests nobody can take: during service, at night, on your closing day. You decide its hours, what it handles alone and what it passes to you. Your team can take any conversation back at any moment.
Heep sends the guest a WhatsApp message within seconds, then a text if WhatsApp does not get through. The conversation carries on in writing: a question, a booking, a group enquiry. The booking is written into your software.
In the United States, with named subprocessors. Secrets are encrypted, access is role-based with two-factor authentication, retention is configurable and a DPA is available on request.
Heep is published by Heep SAS and built by its four founders. The same people run the demos, the onboarding, the support and the product.
Heep is published by Heep SAS, a French company.
Hosting, subprocessors, encryption, two-factor authentication, retention. Details on request.
Thirty minutes on a video call with one of the founders. We start from your reservation software and your channels, and show you what Heep handles alone and what it leaves to you.