No. Intercom has no native, purpose-built integration with TheFork, and TheFork's own B2B API will not close the gap, because it is built for batch data synchronisation rather than live booking. Intercom is a customer-messaging platform built around web chat and its AI agent, Fin. TheFork is a booking network owned by Tripadvisor and, through TheFork Manager, the reservation software behind it. Fin can answer a guest's question about your restaurant. It cannot hold them a table.
The short answer
Intercom can receive a TheFork enquiry as a conversation. It cannot do anything with it in TheFork Manager. Checking the shift, holding a table, confirming a promotion, recording an access requirement: all of that still happens by hand, in TheFork Manager, by a person.
Intercom + TheFork | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Intercom's API and TheFork's B2B API |
What the workaround still can't do | Check live availability, create or amend a booking, apply a promotion or set menu |
TheFork deserves credit on that middle row. It is the most openly documented booking platform in this comparison, running a public developer portal for its B2B API aimed at CRM systems and large restaurant groups. It is still the wrong shape for handling enquiries, for a reason TheFork sets out itself.
What actually happens to a booking enquiry
One mismatch first, because it shapes the rest. Intercom is chat-first and excellent at chat. Enquiries from a European booking network arrive by email, frequently in the guest's own language, often about details a family wants confirmed in writing before they travel. A chat widget on your website is not where those enquiries land.
Here is the real journey of one enquiry when Intercom and TheFork do not talk to each other.
A guest writes in Italian asking whether you have highchairs, whether a pram can be brought into the dining room, and whether a table for five including two small children is possible for Sunday lunch. The message becomes an Intercom conversation.
An agent picks it up and reads it, translating as they go.
The agent opens TheFork Manager in another tab, because Intercom cannot see the shift.
They check Sunday lunch availability for five, look at which tables can take a pram without blocking a service route, and confirm the highchair count for that sitting.
They create the booking in TheFork Manager, re-keying the name, date, time, party size and the access notes from the message.
They switch back to Intercom and write the reply, in Italian if anyone on shift can, in English if not.
They close the conversation.
The guest replies: "Grandparents are joining, so seven." Seven changes which tables work and whether the pram still fits. 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. Paying commission on network covers while being unable to measure what happens to network enquiries is an uncomfortable combination.
The sharper cost is the enquiry you never hear about again. A guest browsing a booking network has a dozen comparable restaurants one tap away, and a family planning Sunday lunch will simply book the one that answers. 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." Intercom did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Intercom actually connects to
The Intercom App Store is substantial: CRMs, analytics, developer tools, billing platforms, marketing automation. It reflects Intercom's core market, which is software and SaaS companies running support and engagement at scale. No restaurant booking system appears in it, and TheFork is no exception.
TheFork's side is more open, and worth crediting properly. It publishes a B2B API developer portal and integrates with serious point-of-sale partners including Lightspeed, Oracle and Trivec. For a group wanting reservation data in its CRM, that is a real answer.
It is not an answer to this problem, and TheFork's own documentation says why: the API is framed around data synchronisation without the need for real-time updates. It is a batch sync surface. A booking enquiry needs the opposite, a live availability check at the moment the agent is typing and the ability to write a real booking back into the shift immediately. TheFork is also not on Zapier, so there is no low-code shortcut. Fin, Intercom's AI agent, is genuinely strong at answering from your help content and resolving routine queries, but it has no line into the diary. Fin can describe your highchair policy. It cannot see Sunday's shift or hold the table. Its actions are limited to systems you have already connected, which returns you to a custom build against a sync-oriented API.
There is also a multi-site fit issue worth flagging. Intercom is built around one product and one brand voice, and a group running several venues with different menus, policies and tones has no native concept of which venue an enquiry belongs to.
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 diary. That difference is the whole problem.
The messaging platform 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 Intercom for customer messaging still run their booking enquiries through a shared Gmail or Outlook inbox. The 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 diary are the same surface, so a direct enquiry gets the same handling as a booking the network sends. This is what RevVue does, and it is easier to show than to describe.
Enquiries are tagged to the right venue on arrival, which matters for groups whose sites sit in different cities and sometimes different countries. Nobody works out which restaurant a message is about before answering it, because the team works from one queue, by location, rather than a chat inbox that closes the conversation and moves on.
Every enquiry routed to its venue automatically, across cities and sites.
The AI drafts the reply in that venue's voice, using its menus, its policies and its own way of answering. For a group taking enquiries in more than one language, the draft is a starting point rather than a blank page.
A reply drafted in the venue's voice, waiting for the team to approve it.
Because it connects to the booking system, the AI does the step Intercom cannot: it checks availability and prepares the booking inside the same thread. The routine requests clear themselves, and the group bookings and private-hire enquiries, the ones the network does not send you, are acknowledged instantly and held for a person.
Group and private-hire enquiries acknowledged and prepared, ready for someone to close.
And because every enquiry is tracked by location, direct demand becomes as visible as network demand. Response rates and conversion by site, so you can see what your own inbox is worth next to the covers you pay commission on. Intercom reports on conversations and resolution rates, which cannot be compared with the covers the network reports.
Response rate, volume and conversion by location, measured against network-sourced covers.
An honest note on where RevVue is today
RevVue's TheFork 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 Intercom, and the wider options are covered in Intercom alternatives for restaurant groups. Since most of these enquiries arrive from the network rather than your own site, automating third-party booking emails covers that specific problem in depth. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes.
Frequently asked questions
Does Intercom integrate with TheFork?
No. Intercom has no native integration with TheFork, and TheFork is not on Zapier. Bridging the two means a custom development project against Intercom's API and TheFork's B2B API. Even when built, it copies enquiry data into a conversation. It cannot check live availability, create a booking, or amend one in TheFork Manager.
Can Fin book a table in TheFork?
No. Fin is a strong conversational AI agent that answers from your help content and past conversations and resolves routine queries end to end. It has no connection to a reservation system. Fin can answer questions about your menu, access or opening hours, but it cannot see the shift, hold a table, or create a booking in TheFork Manager. Fin's actions are limited to systems you have already connected.
Can TheFork's API connect it to a messaging platform?
Not usefully for booking enquiries. TheFork publishes a B2B API developer portal, which is more open than most booking systems offer, and it is a genuine answer for syncing reservation data into a CRM. But TheFork frames it around data synchronisation without the need for real-time updates. Handling an enquiry needs the opposite: a live availability check while the agent is replying, and the ability to write a booking back immediately.
What do restaurant groups use instead for booking enquiries?
Most run booking enquiries through a shared Gmail or Outlook inbox even when they use Intercom for customer messaging, because the platform 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 TheFork integration is on the roadmap, with an email-only pilot available now.
