No. Intercom has no native, purpose-built integration with ResDiary, and any workaround you build still cannot check availability or create a booking inside the conversation. Intercom is a customer-messaging platform. ResDiary is a reservations, table-management and yield-management system used widely by independent restaurants and mid-market groups across the UK and Europe. They were built for different jobs, and the gap between them is exactly where a small group's booking enquiries fall, and where they get lost.
The short answer
Intercom is built around web chat and a genuinely good AI agent called Fin. Neither of those is the same as a held table. A ResDiary booking is only real once it exists in the diary, and Intercom has no way to put it there. Checking the table, creating the booking, adding the allergy note, moving a party from 7pm to 8pm: all of that still happens by hand, in ResDiary, by a person.
Intercom + ResDiary | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Intercom's API and the ResDiary API |
What the workaround still can't do | Check live availability, create or amend a booking, read the guest's booking history |
What actually happens to a booking enquiry
Numbers on a table do not show the cost. The workflow does. Here is the real journey of a single enquiry when Intercom and ResDiary do not talk to each other, and for an independent group with a small central team every one of these steps is time no one has to spare.
A guest emails an independent mid-market group to ask about a table for 10 next Friday at one of its three sites. The message lands as an Intercom conversation.
The one person covering the inbox opens it and reads it.
They open ResDiary in another tab, because Intercom cannot see the diary.
They check availability for that date, party size, and venue, by hand.
They enter the booking into ResDiary, re-keying the guest's name, date, time, party size, and the allergy note from the email.
They switch back to Intercom and write the reply.
They close the conversation.
The guest replies: "Can we make it 12, and one of us has a nut allergy." The same person repeats steps three to seven.
Every enquiry is handled twice, in two systems, by a person copying the same fields from one screen to another. For an independent group that person is often also doing three other jobs, so the enquiry waits. One operations director described the inbox behind this as "a black hole, no KPIs, no response rate, nothing," because the work all happened in tabs and conversations that no report could see.
The sharper cost is the one you never find out about. A booking enquiry is only worth anything if you answer it before the guest books elsewhere, and the double-handling above takes time a lean team often does not have out of hours. A roughly 40-venue entertainment group lost a single booking worth £40,000 because the enquiry arrived outside working hours and no one 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." Intercom did not cause those losses. But routing bookings through a tool that cannot book anything is what makes the delay inevitable.
What Intercom actually connects to
Intercom's App Store is deep in the tools its core market uses: CRMs, product analytics, billing, developer and SaaS platforms. It is built for software companies running large support and engagement operations. Restaurant booking systems are not part of that world, so there is no ResDiary connector to switch on.
Its AI agent, Fin, is the reason many groups reach for Intercom in the first place. Fin is strong. It resolves questions from conversation history and support content, and it holds a natural conversation. What it has no awareness of is a booking system. Fin cannot open the ResDiary diary, read a guest's history, hold a table, or write a booking back. It can qualify and answer up to the point a reservation is needed, then a person has to place it by hand.
There are two further mismatches worth naming. Booking enquiries in UK hospitality are still mostly email, and Intercom is built web-chat-first, so a small central team that has lived in Outlook or Gmail for years is being asked to move to a chat-style interface for a job that is not chat-shaped. And a group running several sites cannot give each one its own tone and knowledge inside Intercom's single-product model, so the replies drift toward one generic voice.
A tech-forward operator might attempt a custom bridge between Intercom's API and the ResDiary API. Even done well, it becomes a data-sync project to build and maintain, which is a lot to ask of an independent group, and it still stops short of the thing that matters: Fin cannot open the diary, hold the table, and write the booking back mid-conversation. The enquiry moves. The booking does not.
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 booking system. That difference is the whole problem.
Intercom can write a polished reply. It cannot book the table. The transaction, the part that actually earns the revenue, still lands on your team, one enquiry at a time, which for an independent group is often one person. This is why most mid-market groups that run a messaging tool for support still run their booking enquiries through a shared Gmail or Outlook inbox. The messaging platform 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 booking system are the same surface, so the enquiry is answered and booked in one place. This is what RevVue does, and it is easier to show than to describe.
Every enquiry is tagged to the right venue automatically, so a table for 10 at one site is never answered with another site's availability. The team works from one queue, by location, instead of a folder maze.
Every enquiry lands in one place, tagged to the venue it is for, instead of scattered across conversations and tabs.
The AI reads each enquiry and drafts the reply in that venue's own tone, grounded in its menu, policies, and FAQs. The person on the inbox reviews and sends with one click rather than retyping from scratch, which is how a lean team keeps response times short.
The AI drafts the reply in the venue's voice and waits for one-click approval, so the team reviews instead of re-keying.
Because it connects to the booking system, the AI does the step Intercom cannot: it checks availability and prepares or creates the booking inside the same thread. Routine bookings are handled on arrival, and the high-value ones, the large parties and private hires, are acknowledged instantly and held in a prioritised queue for a person to nurture, so the £40,000 enquiry is never the one that sits unseen.
High-value bookings the AI has acknowledged and prepared, waiting in a queue the team actually works rather than buried in an inbox.
And because every enquiry is tracked by location, the black box becomes a dashboard: response rates, volumes, and conversion by site, the numbers the tabs-and-conversations workflow could never produce.
Response rate, volume, and conversion by location, so the inbox stops being a black box and starts being something you can manage.
An honest note on where RevVue is today
RevVue's ResDiary integration is on the roadmap, and the group runs an email-only pilot now. That is the honest status. The pilot already delivers the inbox value shown above: location-aware routing, instant acknowledgement around the clock, AI-drafted replies in each venue's voice, high-value bookings surfaced, and reporting by location. The UK AI is in pilot. The booking-system connection deepens that later, it does not gate the value today.
This is the move the Brasilia Group made, off a horizontal tool 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 messaging-first tools, the fuller picture is in the Intercom alternative for restaurant groups and RevVue vs Intercom, and the category overview is in shared inbox software for restaurants. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes or email karan@revvue.ai.
Frequently asked questions
Does Intercom integrate with ResDiary?
No. Intercom has no native integration with ResDiary. A custom build on Intercom's API and the ResDiary API can sync some data, but it cannot check availability, create a booking, or amend one in ResDiary. That work still has to be done by hand in ResDiary.
Can Intercom's Fin AI make a booking?
No. Fin is a strong conversational agent that resolves questions from conversation history and support content, but it has no connection to a restaurant booking system, so it cannot check the diary or create a reservation. It can hold the conversation up to the point a booking is needed, then a person has to place it in ResDiary.
Is Intercom a good fit for restaurant booking enquiries?
It is a strong fit for a software company's support and engagement, less so for restaurant bookings. It is web-chat-first while booking enquiries are mostly email, it has no booking-system integration, and its single-product model makes per-venue tone hard for a multi-site group. The reply is good, but the booking still falls to the team, which for an independent group is often one person.
What do restaurant groups use instead for booking enquiries?
A purpose-built option is RevVue, which is email-first, location-aware, and gives each venue its own tone and knowledge, with an AI that checks availability and creates the booking in the conversation. Its ResDiary integration is on the roadmap, with an email-only pilot available now that delivers value on the inbox first.
