No. Zendesk has no native, purpose-built integration with Tock, and the workarounds that exist still cannot check availability or create a booking inside the conversation. Zendesk is a customer-service helpdesk. Tock is a reservation platform built around prepaid and deposit-backed bookings, ticketed events and tasting menus, used by fine-dining rooms, chef's counters and wineries. They were built for different jobs, and on a deposit-led booking the gap between them is expensive.
The short answer
Zendesk can receive a Tock enquiry as a ticket. It cannot do anything with it in Tock. Checking the calendar, moving a prepaid seat, changing a menu selection, handling the deposit: all of that still happens by hand, in Tock, by a person.
Zendesk + Tock | |
|---|---|
Native integration | None |
Best available workaround | A Zapier or custom-API bridge that copies enquiry text into a ticket |
What the workaround still can't do | Check availability, move or amend a prepaid reservation, handle the deposit, read the guest's Tock history |
Tock is one of the few booking systems in this category that gives you something to work with. It offers an API and webhooks, and it works with Zapier. That is a genuine credit. The catch is the ceiling, not the connection.
What actually happens to a booking enquiry
Tock's model raises the stakes on every amendment, because money has usually already changed hands. Here is the real journey of one enquiry when Zendesk and Tock do not talk to each other.
A guest emails to ask whether their prepaid tasting-menu booking for four can move from Friday to the following Thursday, and whether one cover can switch to the vegetarian menu. The message becomes a Zendesk ticket.
An agent opens the ticket and reads it.
The agent opens Tock in another tab, because Zendesk cannot see the calendar.
They check whether Thursday has a table of four at the right seating, and what the deposit and cancellation terms allow this close to the date.
They move the booking in Tock, adjust the menu selection, and work out whether the price difference needs a refund, a top-up, or nothing at all.
They switch back to Zendesk and write the reply, explaining the change and the money.
They mark the ticket solved.
The guest replies: "Actually can we make it six, and one guest is coeliac." The agent repeats steps 3 to 7, and the deposit maths changes again.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. On a prepaid booking the double-handling is not just slow, it is where mistakes get expensive: 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," because the work happened in tabs and tickets that no report could see.
The sharper cost is the enquiry you never hear about again. A booking enquiry is only worth something if you answer it before the guest books elsewhere, and tasting-menu enquiries often arrive in the evening, from people planning at home after work. 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." Zendesk did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Zendesk actually connects to
Zendesk has a large marketplace: CRMs, e-commerce platforms, telephony, analytics, workforce tools. What it does not have is a connection to restaurant booking systems, because those are not the tools its core market runs. Zendesk sells into software, retail and financial services. Search the Zendesk Marketplace and you will find Salesforce and Shopify, not Tock.
Tock is more open than most of its peers, which makes the ceiling clearer rather than higher. Its data API and webhook programme exists, but it is gated to Premium and Premium Unlimited plans and provisioned on request rather than self-serve. Tock also works with Zapier, so a zap that raises a Zendesk ticket when something happens in Tock is genuinely buildable, without engineering.
Build it and look at what you have. A new reservation or a change in Tock can create or update a ticket in Zendesk. That is one-directional notification. It does not let an agent see the calendar, hold a seat, move a prepaid booking, or adjust a deposit from inside the ticket. Zendesk AI, the platform's answer bot and agent copilot, can suggest a reply from your knowledge base and past tickets, but it has no line into the calendar and cannot take a single action inside Tock. So the workaround makes the enquiry visible in a second system, and the actual booking work, steps 3 to 7 above, is unchanged.
One piece of context worth having before you invest in any of this. 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. If you are scoping a custom bridge to Tock right now, scope it knowing the platform underneath it is consolidating.
Why this matters for booking enquiries
A support ticket and a booking enquiry look similar and behave nothing alike. A support ticket 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.
The helpdesk can write a polished reply. It cannot book the table. The transaction, the part that actually earns the cover, still lands on your team, one enquiry at a time. This is why most groups that run Zendesk for customer service (vouchers, refunds, complaints that need finance) still run their booking enquiries through a shared Gmail or Outlook inbox. The helpdesk never solved the booking side, so the old inbox stayed, and with it the double-handling and the black box.
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 a ticket queue that treats every site the same.
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 Zendesk 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. Zendesk reports on tickets and satisfaction scores, 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. That is the honest status. For now, groups run an email-only pilot that 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 you are weighing the two, the fuller comparison is in RevVue vs Zendesk, and whether the helpdesk fits a multi-site operator at all is covered in is Zendesk right for restaurant groups. If you are consolidating onto Resy, the same question applies there: does Zendesk 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 Zendesk integrate with Tock?
No. Zendesk has no native integration with Tock. Because Tock offers an API and works with Zapier, you can build a bridge that raises a Zendesk ticket when a booking changes in Tock, but it only moves information one way. It cannot check availability, move a prepaid reservation, adjust a deposit, or create a booking in Tock. That work still has to be done by hand.
Can I connect Tock and Zendesk with Zapier?
Partly. Tock works with Zapier, so a zap can create or update a Zendesk ticket from a Tock event. What that gives you is notification, not capability. The agent still has to open Tock in another tab to check the calendar, move the seat, and sort out the deposit. Tock's fuller data API and webhooks are gated to Premium and Premium Unlimited plans and provisioned on request rather than self-serve.
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 run booking enquiries through a shared Gmail or Outlook inbox even when they use Zendesk for customer service, because the helpdesk never 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.
