No. Intercom has no native, purpose-built integration with OpenTable, and any workaround you build still cannot check availability or create a booking inside the conversation. Intercom is a customer-messaging platform. OpenTable is a high-volume front-of-house diary and consumer reservation network. They were built for different jobs, and the gap between them is exactly where a busy multi-site 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. An OpenTable 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 high-chair note, moving a party from 6pm to 7pm: all of that still happens by hand, in OpenTable, by a person.
Intercom + OpenTable | |
|---|---|
Native integration | None |
Best available workaround | A Zapier or custom-API bridge that copies enquiry text into a conversation |
What the workaround still can't do | Check availability, create or amend a booking, read the guest's OpenTable 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 OpenTable do not talk to each other, at the volume a busy group actually runs.
A guest emails a high-volume multi-site group to ask about a table for 12 next Friday at the city-centre site. The message lands as an Intercom conversation, one of dozens that hour.
An agent opens it and reads it.
The agent opens OpenTable 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 OpenTable, re-keying the guest's name, date, time, party size, and the note about a high chair from the email.
They switch back to Intercom and write the reply.
They close the conversation.
The guest replies: "Can we make it 14, and one is in a wheelchair." The agent 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. At high volume that is not a rounding error, it is a role, or several. 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 at volume the double-handling above means enquiries queue, especially 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 OpenTable 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 OpenTable diary, 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. At high volume, that handoff is where the queue builds.
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 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 many sites cannot give each venue its own tone and knowledge inside Intercom's single-product model, so the replies drift toward one generic voice.
Teams who want the two to talk usually try one of two things. The first is a Zapier bridge that watches an inbox or a form and opens an Intercom conversation. The second is a custom build on the OpenTable API. Both move information in one direction and treat it as a support conversation. Neither lets an agent see live availability or write a booking back to OpenTable. So the "integration" is really a copy of the enquiry sitting in a second system, and the actual booking work, steps three to seven above, is unchanged.
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, and at high volume it compounds.
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, while the next 50 wait. This is why most high-volume 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 12 at the city-centre site is never answered with another site's availability. The team works from one queue, by location, instead of a folder maze, which is what makes volume manageable.
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 agent reviews and sends with one click rather than retyping from scratch, which is how a small team keeps up with a large inbox.
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 behind 50 others.
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 OpenTable integration is in active development. That is the honest status. Where the direct booking-system link is not yet live for a group, they run an email-only pilot that 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, it does not gate it.
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 OpenTable?
No. Intercom has no native integration with OpenTable. You can build a Zapier or custom-API bridge that copies an enquiry into an Intercom conversation, but it cannot check availability, create a booking, or amend one in OpenTable. That work still has to be done by hand in OpenTable.
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 OpenTable.
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 high-volume multi-site group. The reply is good, but the booking still falls to the team.
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 OpenTable integration is in development, with an email-only pilot available now that delivers value on the inbox first.
