The guest asks for a table
On WhatsApp, Instagram, SMS, email or after a missed call. Heep understands the date, time, number of covers and the guest's notes, in their language. It asks for whatever is missing.
A guest asks for a table on WhatsApp, Instagram, SMS or email. Heep checks your real availability, writes the booking into Zenchef, SevenRooms or your reservation software, then follows it through to service. Nothing to type in again.
The guest writes on WhatsApp at 10pm. Someone reads it, replies “yes, noted”, then heads back to the floor. The next day, the table is in no software at all. Or it is in there twice. The floor plan no longer tells the truth.
Three steps, nothing for your team to do.
On WhatsApp, Instagram, SMS, email or after a missed call. Heep understands the date, time, number of covers and the guest's notes, in their language. It asks for whatever is missing.
It queries your reservation software the moment the request comes in and only offers slots that are genuinely available. The booking is created with the name, the covers, the note for the kitchen and, if your rules call for it, your software's card guarantee link.
Day-before reminder, confirmation or cancellation in a single message, table released in your software if the guest cancels. An unfinished booking is followed up. You see every step in your inbox.
Heep has no reservation book of its own. It reads yours and writes into it. A table taken on WhatsApp at 10pm appears in Zenchef, SevenRooms or your software as if your team had typed it in, with the name, the covers and the note for the kitchen. Your capacity and card guarantee rules apply, because it is your software that applies them.
The day before, or at the timing you choose, the guest receives a message in your restaurant's name. They confirm or cancel in a word. If they cancel, the table is released in your software and can be given away again. If they do not reply, the booking stays and your team is told.
A card guarantee link opened but not completed, a question left unanswered: Heep follows up with the guest a few minutes later, then flags whatever did not go through. You decide whether to call back or give the table away.
Every booking written by Heep is counted and tied to its conversation. You see the slots requested, the changes and cancellations handled, and an estimated revenue based on your average spend.
We would rather tell you before the demo.
Every booking appears in your Heep inbox with a card: what Heep asked your software, and what your software answered.
If your software turns down a slot, Heep does not invent one. It offers another time, the waiting list if there is one, or hands over to you.
Slots, capacity, card guarantee conditions, cancellation policy: nothing to copy into Heep. You change a rule in your software, Heep applies it to the next request.
You tell Heep the number of covers above which it no longer books on its own. Beyond that, the request is qualified and passed to whoever handles groups and private hire.
If your venue is fully booked, Heep can offer a table at another restaurant in your group, with its own availability.
Zenchef, SevenRooms, TheFork, OpenTable, Resy, Guestonline, Resengo, Tock, Servme and Zomato. Heep reads the availability and writes bookings into the software you already use. Your team carries on working in its usual tool. If yours is not on the list, tell us during the demo.
Heep still works, but it does not confirm a table on its own. It collects the date, time, number of covers, name and phone number, then passes the request to your team, who confirm. The guest knows their request has been taken into account, and by whom.
Heep only offers what your software shows as available at the moment of the request, and re-checks the slot just before writing the booking. It checks the date and the guest's name and refuses to create a duplicate for the same guest. If your software says no, Heep offers an alternative or hands over to you.
Heep sends the guest the card guarantee link generated by your reservation software, within the conversation. The conditions (from how many covers, what timing, what amount) are the ones you have set in your software. Heep takes nothing upfront: a card guarantee, not a payment. If the guest opens the link without completing it, Heep follows up.
The booking stays as it is in your software. Heep only releases the table when the guest cancels explicitly. With no reply, the booking is flagged in your inbox and your team decides: call back, keep the table or give it away.
Access to your software (an account with the API enabled, provided by the vendor; for SevenRooms, this access depends on your contract and your region). If you use Zen Call with Zenchef, it needs to be switched off so your guests do not receive two messages after a missed call. We handle the connection with you.
Zenchef, SevenRooms, TheFork, OpenTable, Resy, Guestonline, Resengo, Tock, Servme and Zomato. Heep checks your availability and writes the booking straight into your software, following your venue's rules: services, rooms, table sizes, card guarantee if you use one.
Each entry on our Integrations page sets out the prerequisites and exactly what Heep does. Your software is not on the list? Tell us: we will give you an honest answer on what is possible.
Yes. With no software connected, Heep does not confirm a table itself: it qualifies the request (date, time, number of covers, occasion, contact details) and passes it to your team, who confirm. The guest is told that someone will come back to them.
That is how event venues and private-hire spaces usually work, on a diary or by email. With software connected, Heep books, changes and cancels directly.
Heep writes to you on WhatsApp exactly as it would write to your guests, with your hours and your rules. You judge it on the evidence, then start whenever you are ready.