No. Hiver has no native, purpose-built integration with Resy, no restaurant booking system appears in Hiver's app library, and Resy is the hardest platform in this category to bridge because it publishes no public API and is not on Zapier. Hiver turns Gmail into a helpdesk, so your bookings@ address stays where it is and gains assignment, notes and SLA tracking. Resy is a reservation, waitlist and guest-CRM platform owned by American Express, used by restaurants where the diary sells out.
The short answer
Hiver can receive a Resy enquiry in your shared Gmail inbox and make it accountable. It cannot do anything with it in Resy. Checking the book, moving a table, adding a high chair, reading the guest's history: all of that still happens by hand, in Resy, by a person.
Hiver + Resy | |
|---|---|
Native integration | None |
Best available workaround | A custom build, and only if Resy grants you partner API access |
What the workaround still can't do | Check availability, create or amend a reservation, read the guest's Resy history |
That middle row is the bleakest in the Hiver set, and the reason is entirely on the Resy side. Hiver has a Zapier connector and its own API, so its half is ready. Resy is absent from Zapier, runs no self-serve developer portal and publishes no OpenAPI specification. Access goes to approved partners in defined categories (point of sale, CRM, loyalty, marketing, discovery) under a direct agreement, and a shared inbox is not one of them.
What actually happens to a booking enquiry
Give Hiver full credit first. If your group is on Google Workspace and enquiries arrive at a shared Gmail address, Hiver is the lowest-friction improvement available: no migration, no new interface, and immediate assignment, internal notes, SLA rules and reporting on that mailbox.
Here is the real journey of one enquiry once you have done that.
A guest emails
bookings@asking to move their booked table for four this Saturday from 8pm to 7pm, and to add a high chair for a toddler. The message lands in Gmail and Hiver assigns it.An agent opens it in Gmail and reads it.
The agent opens Resy in another tab, because Hiver cannot see the book.
They find the reservation, check whether 7pm has a table of four, look at what moving it does to the turn behind, and check whether the table they would move to takes a high chair without blocking a walkway.
They amend the booking in Resy, re-keying the new time and adding the high-chair note to the reservation.
They switch back to Gmail and write the reply.
They close the conversation in Hiver.
The guest replies: "Actually could we do 6.30 and make it five?" Both changes reopen the whole question. The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. Amendments like this are the volume problem for a busy restaurant: individually small, endlessly repeated, and each one costs a tab switch. One operations director described the inbox behind this workflow as "a black hole, no KPIs, no response rate, nothing." Hiver gives you the response rate and the ownership. It cannot show you the covers, because it never sees one.
The sharper cost is the enquiry you never hear about again. Same-week amendment requests and availability questions are perishable, and a restaurant with a full book has the least slack to answer quickly. A roughly 40-venue entertainment group lost a single booking worth £40,000 because the enquiry arrived outside working hours and nobody replied in time. A three-site pizza group put it more bluntly about a 30 to 40 cover enquiry: "It just sat there. No one saw it. They went somewhere else." Hiver did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Hiver actually connects to
Hiver integrates with more than 100 apps, and the named ones tell you who it sells to: Salesforce, HubSpot, QuickBooks, Okta, Jira, Slack, NetSuite, Shopify and Asana. It also offers a Zapier connector and the Hiver API for custom builds, and Harvey, its AI bot, suggests relevant templates, closes conversations and marks spam.
None of those is a restaurant booking system. This is worth stating carefully, because Hiver publishes a hospitality help-desk page that mentions integrating with booking engines and guest-management systems. That is general copy aimed largely at hotels, and what backs it is the 100-plus business apps, Zapier and the API rather than any named restaurant diary. So Hiver has not ignored hospitality. It has not built for the diary.
With Resy, even the two usual routes narrow to one that most operators cannot take. There is no zap to build, because Resy is not on Zapier. There is no self-serve API to build against, because Resy does not publish one. That leaves a direct partnership agreement with Resy for a use case outside its published partner categories, followed by custom development. For almost every restaurant group the conversation ends there. Harvey helps with the writing rather than the booking: it can surface the right amendment template and cannot tell you whether 7pm is free.
There is one more gap for a multi-site group. Hiver's structure is Gmail's structure: mailboxes, labels and rules. A label is not a venue. There is no native concept of which site an enquiry belongs to, no per-venue tone, and no reporting by location.
Worth knowing for planning: Resy is currently absorbing Tock's venues under American Express, roughly doubling its library to more than 25,000 restaurants.
Why this matters for booking enquiries
A support conversation and a booking enquiry look similar and behave nothing alike. A support conversation is resolved by a reply. A booking enquiry is only resolved when a table is held in the book. That difference is the whole problem.
Hiver makes the email accountable. It cannot move the table. The transaction, the part that actually earns the cover, still lands on your team, one enquiry at a time. Hiver is best understood as the most graceful way to keep the old workflow rather than a way out of it.
What it looks like when the tool is built for booking enquiries
The gap closes when the inbox and the diary are the same surface, so the enquiry is answered and booked in one place instead of two. This is what RevVue does, and it is easier to show than to describe.
Enquiries are tagged to the right venue as they arrive, so a group with several restaurants stops triaging by hand. That matters more when demand is high, because the enquiries that arrive by email are usually the ones the online book already turned away. The team works from one queue, by location, rather than labels standing in for venues.
One queue, sorted by venue, for the enquiries that never fitted into the online book.
The AI drafts the reply in that venue's voice, using its menus, its policies and the answers it gives most often. Guests who write after missing a slot want a real answer about alternatives, and the draft already contains them.
A drafted reply in the venue's voice, ready for the team to approve or adjust.
Because it connects to the booking system, the AI does the step Hiver cannot: it checks availability and prepares the booking inside the conversation. Everyday requests are handled on arrival, and the high-value ones, the celebration tables and the large parties, are acknowledged instantly and held in a queue the team works.
High-value enquiries acknowledged and prepared, waiting for a person rather than for attention.
And because every enquiry is tracked by venue, you can finally see the demand that never made it into the book. Response rates, volumes and conversion by site: the part a reservations platform cannot show you. Hiver reports on mailbox SLAs and response times, which never connects a reply to a seated table.
Enquiry volume, response rate and conversion by location, including the demand the book never recorded.
An honest note on where RevVue is today
RevVue's Resy integration is on the roadmap, and the honest position today is an email-only pilot. That pilot already delivers the inbox value shown above: location-aware routing, instant acknowledgement, AI-drafted replies, high-value bookings surfaced, and reporting by location. The direct booking-system connection will deepen that when it lands, but it does not gate the value you get today. The UK AI is in pilot.
This is the move the Brasilia Group made, off a horizontal helpdesk and onto an inbox built for the job. Their founder, Nikolaos Kiosses, put it plainly: "The transition from Zendesk to RevVue has been a game changer."
If your enquiries currently live in a shared Gmail account, replacing a shared Gmail inbox for a restaurant group is the most relevant read next, and shared inbox software for restaurants is the wider category view. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes.
Frequently asked questions
Does Hiver integrate with Resy?
No. Hiver has no native integration with Resy, and no restaurant booking system appears in Hiver's app library. Resy publishes no public API and is not on Zapier, so a bridge requires partner API access granted directly by Resy plus custom development. Even then it only copies enquiry text into a Gmail conversation. It cannot check availability, amend a reservation, or read the guest's Resy history.
Can I connect Hiver and Resy with Zapier?
No. Hiver has a Zapier connector, so its half is ready, but Resy is not on Zapier at all, runs no self-serve developer portal and publishes no OpenAPI specification. That leaves a direct partnership agreement plus custom development, which in practice puts it out of reach for most restaurant groups.
Hiver's website mentions booking engines. Does that include restaurant diaries?
Not in any named sense. Hiver publishes a hospitality help-desk page that refers to booking engines and guest-management systems, which is general copy aimed largely at hotels, and it is backed by Hiver's 100-plus business apps, its Zapier connector and its API rather than by any named restaurant diary. With Resy, neither of those routes is even available without partner access.
What do restaurant groups use instead for booking enquiries?
Most stay on a shared inbox and accept the double-handling, because no general-purpose tool solved the booking side. A purpose-built option is RevVue, which is location-aware and whose AI checks availability and prepares the booking inside the conversation. Its Resy integration is on the roadmap, with an email-only pilot available now.
