No. Gorgias has no native, purpose-built integration with Tock. 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 inside the conversation. Gorgias is a helpdesk built for e-commerce, wired deeply into Shopify. Tock is a reservation platform built around prepaid bookings, deposits, ticketed events and tasting menus. Both platforms handle money. Only one of them will let Gorgias touch it.
The short answer
Gorgias can receive a Tock enquiry as a ticket. It cannot do anything with it in Tock. Checking the calendar, moving a prepaid booking, transferring a ticket, adjusting a deposit: all of that still happens by hand, in Tock, by a person.
Gorgias + 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 booking, transfer a ticket, handle the deposit |
This is the most connectable pairing in the Gorgias set. Gorgias has a Zapier app, a developer API and a Gorgias MCP server on Zapier. 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 is worth naming precisely.
What actually happens to a booking enquiry
Tock's prepaid model means money has usually changed hands before the guest ever writes to you, and if you also sell online, one email can involve two separate payments.
A guest emails about next month's wine dinner. They prepaid two seats through Tock and also bought a bottle bundle from your online shop to collect on the night, and now they need to move to a later date and return the bundle. The message becomes a Gorgias ticket.
Gorgias handles the shop half by itself. The bundle order sits alongside the message because it lives in Shopify, and AI Agent can look it up, confirm it has not been collected and process the return without a human.
The prepaid-seat half waits for a person. An agent opens Tock in another tab, because Gorgias cannot see the event calendar or the Tock payment.
They find the booking, check the transfer terms against how close the original date is, see whether the later event has two seats at the right seating, and work out whether the deposit transfers or has to be refunded and re-taken.
They move the booking in Tock and carry the payment across.
They switch back to Gorgias and write the reply, being precise about two different pots of money.
They mark the ticket closed.
The guest replies: "Can we make it four for the new date?" Four changes the seating and the amount paid. The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. Steps two and three make the point better than any argument: within one ticket, Gorgias processed a refund on its own and could not move a booking it had no sight of. One operations director described the inbox behind this workflow as "a black hole, no KPIs, no response rate, nothing," because the booking work happened in tabs and tickets that no report could see.
The sharper cost is the enquiry you never hear about again. Event and 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." Gorgias did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Gorgias actually connects to
Gorgias is the counter-example that proves the rule, so it deserves a fair and precise description.
Most helpdesks in this comparison cannot take real actions on anything. Gorgias can. Its App Store is organised around e-commerce, shipping, marketing, loyalty, analytics and support channels, with Shopify at the centre and apps like Magento, NetSuite, Klaviyo, Recharge and Tapcart alongside. Its AI Agent, the Automate product, is an autonomous support and sales agent for e-commerce brands: it answers order questions, recommends products, and performs genuine transactions such as looking up an order, cancelling one, editing a delivery address or changing a subscription. That is a helpdesk completing work inside the conversation, which is rare and real.
So the argument here is not that a helpdesk cannot act. It is that Gorgias can act because it was purpose-built around one system of record, and that system of record is Shopify. A reservation platform is a different system of record, and Gorgias has no line into one. Search the Gorgias App Store for Tock and you will find nothing.
The workaround is genuinely available here, which makes the ceiling unusually clear. Both tools are on Zapier, so a zap that raises a Gorgias ticket when a Tock booking is created or changed is buildable in an afternoon. What it produces is notification, moving one direction. It does not let the agent see the calendar, hold a seat, transfer a ticketed booking, or move a deposit from inside the ticket. AI Agent cannot bridge it either, because its action library comes from your connected e-commerce systems. It can refund the bottle bundle and cannot move the seats.
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.
One honest credit worth giving. If you sell wine, gift cards, vouchers or merchandise online, Gorgias is genuinely good at that side and the AI Agent will resolve much of it without a human. The gap is bookings, not the whole tool.
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, or in Gorgias's case sometimes by an autonomous action. 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.
Gorgias proves the point rather than escaping it. It shows what a helpdesk looks like when someone builds it around the transaction an industry runs on. Nobody has done that for restaurant bookings inside Gorgias, so the transaction that 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 a helpdesk organised around a shop instead of a diary.
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 Gorgias 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. Gorgias reports on tickets and the revenue its agents influence, 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."
The wider category view is in shared inbox software for restaurants. If you are consolidating onto Resy, the same question applies there: does Gorgias 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 Gorgias integrate with Tock?
No. Gorgias has no native integration with Tock, and no restaurant booking system appears in the Gorgias App Store. Because both tools are on Zapier you can build a bridge that raises a Gorgias ticket when a Tock booking changes, but it only moves information one way. It cannot check availability, move a prepaid booking, transfer a ticket, or handle a deposit.
Can I connect Gorgias and Tock with Zapier?
Yes, and this is the most connectable pairing in the Gorgias set. Both are on Zapier, so a zap can create or update a Gorgias ticket from a Tock event. That gives you notification, not capability. The agent still opens Tock in another tab to check the calendar, move the seating 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 run booking enquiries through a shared inbox even when a helpdesk covers customer service and the online shop, 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.
