No. Gorgias has no native, purpose-built integration with Resy, and this is the hardest pairing in the whole comparison, because Resy publishes no public API and is not on Zapier. Gorgias is a helpdesk built for e-commerce, wired deeply into Shopify. Resy is a reservation, waitlist and guest-CRM platform owned by American Express, used by restaurants where the diary sells out. Gorgias can complete a real transaction inside a conversation. Resy will not let it anywhere near the book.
The short answer
Gorgias 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 the guest's history: all of that still happens by hand, in Resy, by a person.
Gorgias + 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 |
Most cells in this comparison at least give you a bad option. This one barely does. Gorgias is well served on Zapier and publishes a developer API, so its half of the bridge is ready. Resy is absent from Zapier, runs no self-serve developer portal and publishes no OpenAPI specification. Access goes to approved partners in defined categories (point of sale, CRM, loyalty, marketing, discovery) under a direct agreement, and a helpdesk is not one of them.
What actually happens to a booking enquiry
Resy restaurants are usually the ones under the most booking pressure, and once you also sell online, one email carries both jobs.
A guest emails to say they were given one of your gift cards for their birthday, asks whether it can be used on a Friday, and wants a table for four this Friday if anything is left. The message becomes a Gorgias ticket.
Gorgias handles the gift-card half well. The card sits alongside the message because it lives in Shopify, and AI Agent can confirm the balance, the expiry and the terms without a human.
The booking half waits for a person. An agent opens Resy in another tab, because Gorgias cannot see the book.
They check Friday for four, confirm it is full, look at whether any holds are due to release, and check the walk-in position.
They add the guest to the Resy waitlist by hand, re-keying the name, contact details, party size and date.
They switch back to Gorgias and write the reply, covering the gift card and the waitlist position.
They mark the ticket closed.
The guest replies: "If Friday frees up we could do six, or we could take Thursday." Two new questions, both about the book. 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 are the contrast that matters: the same tool answered a question about money on its own account and could not tell the guest whether a table existed. 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. Availability and waitlist questions are perishable in a way an order question is 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." 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 diary is a different system of record, and Gorgias has no line into one. Search the Gorgias App Store for Resy and you will find nothing.
What makes this pairing the bleakest in the comparison is the other side. There is no zap to build, because Resy is not on Zapier. There is no self-serve API to build against, because Resy does not publish one. The only route is a direct partnership agreement with Resy for a use case that does not fit its published partner categories, followed by a custom development project. For almost every operator, the conversation ends before any code is written. Even if it did not, what you would get is enquiry text copied into a ticket, one direction, treated as a support case. AI Agent cannot help either, because its action library comes from your connected e-commerce systems. It can confirm the gift-card balance and cannot check Friday.
One honest credit worth giving. If you sell 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.
Worth knowing for planning: Resy is currently absorbing Tock's venues under American Express, roughly doubling its library to more than 25,000 restaurants.
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 table is held in the book. 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 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 helpdesk organised around a shop instead of a diary.
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 Gorgias 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. Gorgias reports on tickets and the revenue its agents influence, 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, 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, and if you are weighing helpdesks generally, the best Zendesk alternatives for restaurant groups covers the field. 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 Resy?
No. Gorgias has no native integration with Resy, and there is no self-serve route 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 custom development. 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.
Can I connect Gorgias and Resy with Zapier?
No. Gorgias is on Zapier and publishes a developer API, so its half is ready. Resy is not on Zapier at all, runs no self-serve developer portal and publishes no OpenAPI specification. That leaves a direct partnership agreement plus custom development, which in practice puts it out of reach for most restaurant groups.
Gorgias AI Agent can process a gift card, so why can't it book a table?
Because its actions come from the systems Gorgias was built around. AI Agent performs real transactions such as order lookups, cancellations, address edits and subscription changes, because Gorgias is wired into Shopify and the e-commerce stack. A reservation diary is a different system of record, and Gorgias has no connection to one. The capability is real, the scope is e-commerce.
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 Resy integration is on the roadmap, with an email-only pilot available now.
