No. Freshdesk has no native, purpose-built integration with Tock. You can wire the two together loosely through Zapier, and the result still cannot check availability, move a prepaid seat or handle a deposit inside the conversation. Freshdesk is a customer-service helpdesk, positioned as the simpler and lower-cost alternative to Zendesk. Tock is a reservation platform built around prepaid bookings, deposits, ticketed events and tasting menus. On a booking where money has already changed hands, the gap between them costs real money.
The short answer
Freshdesk can receive a Tock enquiry as a ticket. It cannot do anything with it in Tock. Checking the calendar, transferring a ticketed booking, changing a menu, refunding or moving a deposit: all of that still happens by hand, in Tock, by a person.
Freshdesk + 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 |
Both ends of this connection are unusually reachable, which is what makes the limitation instructive rather than just annoying. Freshdesk has a mature Zapier presence. Tock offers an API and webhooks and works with Zapier too. The problem is not access. It is what a helpdesk is capable of once connected.
What actually happens to a booking enquiry
Tock's prepaid model turns every amendment into an admin task with a financial consequence attached. Here is the real journey of one enquiry when Freshdesk and Tock do not talk to each other.
A guest emails to say they bought two tickets to next month's wine dinner but can no longer attend, and asks whether they can transfer them to a friend or get a credit. The message becomes a Freshdesk ticket.
An agent opens the ticket and reads it.
The agent opens Tock in another tab, because Freshdesk cannot see the event or the payment.
They find the booking, check the event's transfer and refund terms, see how many seats remain unsold, and decide whether a transfer, a credit or a straight refund is right.
They make the change in Tock, re-keying the new guest's name and contact details and adjusting the payment record.
They switch back to Freshdesk and write the reply, explaining exactly what has happened to the money.
They mark the ticket resolved.
The friend emails separately to ask about a dietary requirement for the same event. That arrives as a brand new ticket with no connection to the first, and the agent repeats steps 3 to 7 from scratch.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. Step eight is the one that stings on a prepaid platform: the ticket and the booking are separate records, so the context of who paid, who is attending and what was agreed lives in the agent's head rather than anywhere the next agent can see it. 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. Event and tasting-menu enquiries arrive in the evening, from people planning at home, and a slow answer sends them to a different 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." Freshdesk did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Freshdesk actually connects to
The Freshworks Marketplace is real and reasonably deep: CRM, e-commerce, telephony, billing, project tools, plus the rest of the Freshworks suite. What it does not contain is a restaurant booking system, because Freshdesk sells into general customer support for small and mid-market businesses, not hospitality operations. Search it for Tock and you will find nothing.
Tock is more open than most of its peers, and it is worth crediting accurately. Tock offers a data API and webhooks, gated to Premium and Premium Unlimited plans and provisioned on request rather than self-serve, and it works with Zapier. So a zap that raises a Freshdesk ticket when a Tock booking is created or changed is genuinely buildable, with no engineering involved.
Now look at what you actually have. A booking event in Tock can create or update a ticket in Freshdesk. That is one-directional notification. It does not let an agent see the calendar, hold a seat, transfer a ticketed booking, or move a deposit from inside the ticket. Freddy, Freshdesk's AI assistant, can suggest replies, categorise and read sentiment, but it is trained on support data, has no line into the calendar, and cannot take a single action inside Tock. So the zap makes the enquiry visible in a second system, and the actual booking work, steps 3 to 7 above, is unchanged.
One piece of context 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 bridge to Tock, scope it knowing the platform underneath 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 Freshdesk 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 list 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 Freshdesk 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. Freshdesk reports on tickets and SLA compliance, 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 Freshdesk, and the wider options are covered in Freshdesk alternatives for restaurant groups. If you are consolidating onto Resy, the same question applies there: does Freshdesk 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 Freshdesk integrate with Tock?
No. Freshdesk has no native integration with Tock. Because Tock offers an API and works with Zapier, you can build a bridge that raises a Freshdesk ticket when a booking is created or changed in Tock, but it only moves information one way. It cannot check availability, move a prepaid booking, transfer a ticket, or handle a deposit. That work still has to be done by hand in Tock.
Can I connect Tock and Freshdesk with Zapier?
Yes, loosely, and it is worth understanding what you get. Both tools are on Zapier, so a zap can create or update a Freshdesk ticket 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 sort out 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 Gmail or Outlook inbox even when they use Freshdesk 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.
