No. Freshdesk has no native, purpose-built integration with Resy, and unlike most booking systems Resy gives you nothing to build one with: no public API, no Zapier app. Freshdesk is a customer-service helpdesk, positioned as the simpler and lower-cost alternative to Zendesk. Resy is a reservation, waitlist and guest-CRM platform owned by American Express, built for restaurants where the diary sells out. The gap between them is where booking enquiries go quiet.
The short answer
Freshdesk can receive a Resy enquiry as a ticket. It cannot do anything with it in Resy. Checking the book, adding someone to the waitlist, holding a table, reading what the guest spent last time: all of that still happens by hand, in Resy, by a person.
Freshdesk + 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, add to the waitlist, create or amend a reservation, read the guest's Resy history |
That middle row is unusually bleak, and it is specific to Resy. For SevenRooms or OpenTable you can at least reach for Zapier and assemble something crude. Resy is not on Zapier. It publishes no OpenAPI specification and runs no self-serve developer signup. Access goes to approved partners in defined categories (point of sale, CRM, loyalty, marketing, discovery) under a direct agreement. Everything else gets the embeddable "Book with Resy" widget, which is a booking button for your website, not a way for a helpdesk to read your diary.
What actually happens to a booking enquiry
Freshdesk tends to be the choice of groups watching cost per agent, which usually means a small team covering a lot of ground. That is precisely the team the manual workflow punishes. Here is the real journey of one enquiry when Freshdesk and Resy do not talk to each other.
A guest emails asking whether there is any chance of a table for two this Saturday, and if not, whether they can go on the waitlist and whether the counter takes walk-ins. The message becomes a Freshdesk ticket.
An agent opens the ticket and reads it.
The agent opens Resy in another tab, because Freshdesk cannot see the book.
They check Saturday, confirm it is full, look at whether any holds are due to release, and check the counter's walk-in policy for that service.
They add the guest to the Resy waitlist by hand, re-keying the name, contact details, party size and date from the email.
They switch back to Freshdesk and write the reply, explaining the waitlist and the walk-in position.
They mark the ticket resolved.
The guest replies: "If Saturday frees up, we could do four instead of two." The agent repeats steps 3 to 7, and the waitlist entry has to be edited rather than created.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. 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. Freshdesk will happily report on ticket volume and resolution time. It cannot tell you how many enquiries turned into covers, because it never sees a cover.
The sharper cost is the enquiry you never hear about again. Waitlist and availability questions are perishable in a way support tickets are not: answer on Monday and it is worthless. 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 everything else in 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 Resy and you will find nothing.
Normally the fallback is a Zapier zap, and Freshdesk is well served on Zapier. The problem is the other end of the connection. Resy is absent from Zapier entirely, so there is no zap to build. That leaves a custom development project against Freshdesk's API and Resy's partner API, which first requires persuading Resy to grant partner access for a use case that does not fit its published partner categories. For most operators the project dies there, before any code is written.
Suppose it did not. What you would have is a pipe that copies enquiry text into a ticket, moving information one way and treating a reservation request as a support case. Freddy, Freshdesk's AI assistant, can suggest replies, categorise tickets and read sentiment, but it is trained on support data and has no line into the book. It cannot take a single action inside Resy. So the "integration" is a copy of the enquiry sitting in a second system, and the actual booking work, steps 3 to 7 above, is unchanged.
Worth knowing if you are planning ahead: Resy is currently absorbing Tock's venues under American Express, roughly doubling its library to more than 25,000 restaurants. If you run both, you are consolidating onto Resy, and this question consolidates with it.
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 table is held in the book. 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 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 a ticket list that treats every site the same.
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 Freshdesk 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. Freshdesk reports on tickets and SLA compliance, 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. 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 most of your enquiries arrive from booking networks rather than your own site, automating third-party booking emails covers that specific problem. 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 Resy?
No. Freshdesk has no native integration with Resy, and there is no self-serve way to build one. Resy publishes no public API and is not on Zapier, so a bridge requires partner API access granted directly by Resy plus a custom development project. Even then it only copies enquiry text into a ticket. It cannot check availability, add a guest to the waitlist, or create a reservation in Resy.
Is there a Resy app in the Freshworks Marketplace?
No. The Freshworks Marketplace covers CRM, e-commerce, telephony, billing and productivity tools, because Freshdesk sells into general customer support rather than hospitality operations. No restaurant booking system appears in it. Resy's own integration partners are point-of-sale, CRM, loyalty, marketing and discovery platforms, and no customer-service helpdesk is among them.
Can Zapier connect Freshdesk and Resy?
No. Freshdesk is well supported on Zapier, but Resy is not on Zapier at all, so there is no zap to build. Resy also runs no self-serve developer portal and publishes no OpenAPI specification, which means the only route is a direct partnership agreement plus custom development. In practice that puts it out of reach for most restaurant groups.
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 Resy integration is on the roadmap, with an email-only pilot available now.
