No. Front 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. Front is a collaborative shared inbox and customer-operations platform. TheFork is a booking network owned by Tripadvisor and, through TheFork Manager, the reservation software behind it. Front is a good place for the enquiry to land and a dead end for the booking.
The short answer
Front can receive a TheFork enquiry as a conversation. It cannot do anything with it in TheFork Manager. Checking the shift, holding a table, applying a set menu, recording a request: all of that still happens by hand, in TheFork Manager, by a person.
Front + TheFork | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Front'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 the middle row. It is the most openly documented booking platform in this comparison, publishing a developer portal for its B2B API aimed at CRM systems and large restaurant groups. That is more than most competitors offer. It is still the wrong shape for handling enquiries, for a reason TheFork states itself.
What actually happens to a booking enquiry
Front's strengths make the gap sharper rather than softer. Shared visibility, assignment, internal comments beside the message, SLA rules and response-time reporting are genuinely good, and a group taking a steady flow of network enquiries feels the benefit. What Front cannot do is take a single step of the booking off the team.
Here is the real journey of one enquiry when Front and TheFork do not talk to each other.
An enquiry arrives in German from a business traveller asking about a working lunch for six next Wednesday, whether there is a quiet table suitable for a meeting, and whether the restaurant can invoice their company. The message lands in the shared inbox as a Front conversation.
An agent picks it up and reads it, translating as they go.
The agent opens TheFork Manager in another tab, because Front cannot see the shift.
They check Wednesday lunch for six, work out which tables are away from the noise at that sitting, and check what the group and payment terms allow.
They create the booking in TheFork Manager, re-keying the name, company, date, time, party size and the seating request from the email.
They switch back to Front and write the reply, in German if someone on shift can, in English if not.
They archive the conversation.
The guest replies: "Can we move to Thursday and make it eight?" Thursday is a different shift and eight is a different table plan. 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. Front will report response times precisely. It cannot tell you which of those responses became covers.
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 business traveller planning a working lunch will book the one that confirms. 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." Front did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Front actually connects to
Front is the most interesting case here, because it cannot be accused of ignoring verticals. Its App Store carries more than 160 integrations, with dedicated categories for logistics and maritime and for travel, built for a customer base in freight forwarding, shipping and travel operations. Front will build deep, industry-specific connections when it decides a market matters. It has chosen freight over hospitality, and no restaurant booking system appears in the App Store.
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 flowing into its CRM, that API is a real answer.
It is not an answer to this problem, and TheFork's own documentation explains why: the API is framed around data synchronisation without the need for real-time updates. It is a batch sync surface for moving records between systems. 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 into the shift immediately. TheFork is also not on Zapier, so Front's Zapier app is no help here, and the realistic route is a custom project against Front's API and TheFork's B2B API. Front AI is a capable suite: Copilot drafts and answers from past conversations, help content and connected systems, Autopilot resolves routine requests, and Smart QA and Topics analyse the queue. All conversation-grounded, none of it with a line into the diary. Copilot can write the German reply. It cannot see Wednesday's shift.
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 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. Front gives you the best-organised version of the old workflow: everyone sees the enquiry, everyone knows who owns it, and the booking still gets typed into another system by hand.
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 tags standing in for venues.
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 Front 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. Front reports on conversations and response times, 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, 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. 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 Front integrate with TheFork?
No. Front has no native integration with TheFork, and no restaurant booking system appears in the Front App Store. TheFork is not on Zapier either, so Front's Zapier app does not help. Bridging the two means a custom development project against Front's API and TheFork's B2B API, and even then it only copies enquiry data into a conversation. It cannot check live availability or create a booking.
Can TheFork's API connect it to a shared inbox?
Not usefully for booking enquiries. TheFork does publish 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.
Why does Front integrate with logistics and travel tools but not booking systems?
Because Front has picked its verticals and hospitality is not among them. Front's App Store carries dedicated categories for logistics and maritime and for travel, reflecting a strong base of freight, shipping and travel-operations customers. That shows Front will build deep vertical integrations when it decides a market matters. It has not made that decision for restaurant booking systems.
What do restaurant groups use instead for booking enquiries?
Most run booking enquiries through a shared inbox and accept the double-handling, because no horizontal tool 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.
