No. Hiver has no native, purpose-built integration with Tock, and no restaurant booking system appears in Hiver's app library. You can wire the two together loosely through Zapier, because both are on it, and the result still cannot check availability, move a prepaid seat or resolve a deposit. Hiver turns Gmail into a helpdesk, so your bookings@ address stays where it is and gains assignment, notes and SLA tracking. Tock is a reservation platform built around prepaid bookings, deposits, ticketed events and tasting menus.
The short answer
Hiver can receive a Tock enquiry in your shared Gmail inbox and make it accountable. It cannot do anything with it in Tock. Checking the calendar, splitting a prepaid booking, transferring a seat, adjusting a deposit: all of that still happens by hand, in Tock, by a person.
Hiver + Tock | |
|---|---|
Native integration | None |
Best available workaround | A Zapier or custom-API bridge that copies enquiry data into the conversation |
What the workaround still can't do | Check availability, move or amend a prepaid booking, transfer a seat, handle the deposit |
This is the most connectable pairing in the Hiver set. Hiver has a Zapier connector and its own API. Tock offers a data API and webhooks, gated to Premium and Premium Unlimited plans and provisioned on request, and works with Zapier too. Nothing blocks the wire, which is why the limit deserves naming precisely.
What actually happens to a booking enquiry
Give Hiver full credit first. If your restaurant 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. On prepaid bookings that ownership matters, because a thread about money should never be ambiguous.
Here is the real journey of one enquiry once you have done that.
A guest emails
bookings@about their prepaid tasting-menu booking for six next month. Two of the party have dropped out, and they ask whether the booking can be split into two tables of three at different times, or whether the two seats can be refunded. The message lands in Gmail and Hiver assigns it.An agent opens it in Gmail and reads it.
The agent opens Tock in another tab, because Hiver cannot see the calendar or the payment.
They find the booking, check whether the seating allows two tables of three at different times, look at the refund and transfer terms this close to the date, and work out what happens to the money in each option.
They make the change in Tock and reconcile the payments.
They switch back to Gmail and write the reply, being precise about what has happened to each part of the deposit.
They close the conversation in Hiver.
The guest replies: "Could the second three come the following week instead?" That is a new date and a new deposit 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. On a prepaid platform the double-handling is where money goes wrong: a seat released that should have been held, a deposit refunded that should have been transferred. 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 booking or the money.
The sharper cost is the enquiry you never hear about again. Tasting-menu enquiries arrive in the evening from people planning at home, and a slow answer sends them to a restaurant with a similar menu. 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 platform. So Hiver has not ignored hospitality. It has not built for the diary.
Here the zap route is genuinely open, which makes the ceiling unusually clear. Both tools are on Zapier, so a zap that opens or updates a Gmail conversation when a Tock booking changes is buildable in an afternoon. What it produces is notification and workflow, moving one direction. It does not let the agent see the calendar, split a booking, transfer a seat, or move a deposit from inside the conversation. Harvey helps with the writing rather than the booking: it can surface the right deposit-terms template and cannot reconcile what the guest has paid.
One piece of context before investing. American Express announced in February 2026 that Tock is merging into Resy, with venues unifying on Resy through summer 2026 and the consumer Tock app and exploretock.com being retired. Tock's restaurant-facing management software continues to operate as part of Resy, and API key requests already route through a Resy address. Scope any bridge knowing the platform underneath is consolidating.
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, so there is no native routing by site, no per-venue tone and no reporting by location.
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 seat is held in the calendar, and on Tock, usually paid for. That difference is the whole problem.
Hiver makes the email accountable. It cannot book the table or move the money. The transaction, the part that actually earns the cover, still lands on your team, one enquiry at a time.
What it looks like when the tool is built for booking enquiries
The gap closes when the enquiry and the booking are handled in one place, so a question about a prepaid seat does not turn into an admin job. This is what RevVue does, and it is easier to show than to describe.
Every enquiry is tagged to the venue it concerns, which matters for a group where each site sells a different ticketed experience. A question about one tasting menu is never answered with another restaurant's seating times, because the team works from one queue, by location, rather than labels standing in for venues.
Enquiries sorted by venue, so each ticketed experience is answered with its own detail.
The AI drafts the reply in that venue's voice, grounded in its menu, its cancellation terms and its prepayment rules. Those terms are the substance of most of these enquiries, and getting them into the first reply is most of the work.
The draft arrives carrying the venue's own terms, ready for one-click approval.
Because it connects to the booking system, the AI takes the step Hiver cannot: it checks availability and prepares the booking in the thread. Simple questions resolve on arrival, and anything touching money, a party growing by four seats or a date moving, is acknowledged instantly and queued for a person, because those are the ones with a payment attached.
Amendments and high-value bookings held for approval, since each one carries a payment.
And because every enquiry is tracked per venue, the admin around prepaid bookings becomes measurable. How many amendments each site handles, how fast it replies, and how much of that work is repeating itself. Hiver reports on mailbox SLAs and response times, which does not tell you what the amendment work cost.
Volume, response rate and conversion by location, including the amendment traffic behind prepaid covers.
An honest note on where RevVue is today
RevVue's Tock 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. If you are consolidating onto Resy, the same question applies there: does Hiver integrate with Resy. 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 Tock?
No. Hiver has no native integration with Tock, and no restaurant booking system appears in Hiver's app library. Because both tools are on Zapier you can build a bridge that opens or updates a Gmail conversation when a Tock booking changes, but it only moves information one way. It cannot check availability, split or move a prepaid booking, transfer a seat, or handle a deposit.
Can I connect Hiver and Tock with Zapier?
Yes, and this is the most connectable pairing in the Hiver set. Both are on Zapier, so a zap can create or update a Gmail conversation from a Tock event. That gives you notification, not capability. The agent still opens Tock in another tab to check the calendar, make the change and reconcile the money. Tock's fuller data API and webhooks are limited to Premium and Premium Unlimited plans and provisioned on request.
Is Tock shutting down now that it has merged with Resy?
The consumer side is being retired, not the venue software. American Express announced in February 2026 that Tock is merging into Resy, with venues unifying on Resy through summer 2026 and the Tock app and exploretock.com being wound down. Tock's restaurant-facing management software continues to operate as part of Resy. If you are planning a custom integration, factor in that the platform underneath is consolidating.
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 Tock integration is on the roadmap, with an email-only pilot available now.
