No. Help Scout has no native, purpose-built integration with Resy, and Resy offers no public API and no Zapier app to build one with. Help Scout is a shared inbox and email-first help desk for small teams. Resy is a reservation, waitlist and guest-CRM platform owned by American Express, used by restaurants where the diary is the scarce resource. Help Scout is closer to how booking enquiries actually arrive than most tools in this category, which makes what it cannot do stand out more sharply.
The short answer
Help Scout can receive a Resy enquiry as a conversation. It cannot do anything with it in Resy. Checking the book, holding a table, requesting a specific area, reading what the guest spent last time: all of that still happens by hand, in Resy, by a person.
Help Scout + 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, create or amend a reservation, request a table area, read the guest's Resy history |
The middle row is unusually restrictive, and that is about Resy rather than Help Scout. 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. The only surface open to everyone is the embeddable "Book with Resy" widget, a booking button for your website rather than a way for an inbox to read your diary.
What actually happens to a booking enquiry
Give Help Scout its due first. Most booking enquiries arrive by email, and Help Scout is built for email, with assignment, saved replies, internal notes and a shared view that stops two people answering the same guest. Compared with a shared Gmail account it is a real step up in accountability. The problem starts at the point where answering stops and booking begins.
Here is the real journey of one enquiry when Help Scout and Resy do not talk to each other.
A PA emails to book a work dinner for eight in three weeks and asks whether the private area is available, whether there is a set menu at that size, and whether they can be invoiced. The message becomes a Help Scout conversation.
An agent opens it and reads it.
The agent opens Resy in another tab, because Help Scout cannot see the book.
They check the date for eight, look at whether the private area is already committed, and check what the group menu and payment terms are for a party that size.
They create the booking in Resy, re-keying the name, company, date, time, party size and the private-area request from the email.
They switch back to Help Scout and write the reply with the menu and invoicing detail.
They close the conversation.
The PA replies: "It is ten now, and two are gluten free." Ten may not fit the private area. The agent repeats steps 3 to 7.
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 conversations that no report could see. Help Scout will report on conversations and response times. It cannot report on covers, because it never sees one.
The sharper cost is the enquiry you never hear about again. Corporate bookers work to a deadline and send the same email to three restaurants, so a reply on Monday morning to a Friday evening enquiry is usually too late to matter. 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." Help Scout did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Help Scout actually connects to
Help Scout's apps directory covers what its market needs: CRM, e-commerce, billing, chat, project tools and analytics, aimed at small businesses, SaaS companies, agencies, nonprofits and online retailers. No restaurant booking system appears in it, and Resy is no exception.
The usual fallback is not available here. Help Scout is well supported on Zapier, but Resy is absent from Zapier entirely, so there is no zap to build. That leaves a custom development project against Help Scout's API and Resy's partner API, which first requires Resy to grant partner access for a use case outside its published partner categories. For most restaurant groups that ends the project before it starts.
Help Scout AI is worth describing honestly, because it is genuinely useful within its remit. It drafts replies, summarises long threads and helps an agent write more quickly and consistently. All of that operates on your conversations and knowledge base. None of it has a line into a reservation system. Help Scout AI can produce a beautifully written reply about the private area. It cannot look at the book to find out whether the private area is free.
There is one more gap that matters for a multi-site group. Help Scout is built around mailboxes, and a mailbox is not a venue. There is no native concept of which site an enquiry belongs to, no per-venue tone, and no reporting by location, so a group running six restaurants ends up either with six mailboxes to watch or one mailbox where nobody can see which site is falling behind.
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 conversation and a booking enquiry look similar and behave nothing alike. A support conversation 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 shared inbox 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. Help Scout gets you a tidy, accountable inbox and leaves the booking work exactly where it was.
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 mailboxes standing in for venues.
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 Help Scout 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. Help Scout reports on conversations and happiness scores, 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, Help Scout alternatives for restaurants covers the comparison in full, and shared inbox software for restaurants is the wider category view. 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 Help Scout integrate with Resy?
No. Help Scout 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 conversation. It cannot check availability, create a reservation, or amend one in Resy.
Can Help Scout AI check availability or book a table?
No. Help Scout AI drafts replies, summarises threads and helps agents write faster and more consistently, all based on your conversations and knowledge base. It has no connection to a reservation system. It can write an excellent reply about your private dining area, but it cannot open the book to see whether that area is free, hold it, or create the booking.
Is Help Scout good for restaurant booking enquiries?
It is a real improvement on a shared Gmail account, because it adds assignment, internal notes, saved replies and response-time visibility to the email channel where most enquiries actually arrive. Two gaps remain. It cannot touch your booking system, so every enquiry is still handled twice. And it is built around mailboxes rather than venues, so a multi-site group gets no native routing, per-venue tone or reporting by location.
What do restaurant groups use instead for booking enquiries?
Most run booking enquiries through a shared inbox even when they use a help desk for customer service, because the help desk 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.
