No. Gorgias 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. Gorgias is a helpdesk built for e-commerce, wired deeply into Shopify. TheFork is a booking network owned by Tripadvisor and, through TheFork Manager, the reservation software behind it. Gorgias can complete a real transaction inside a conversation, and holding a table is not one of them.
The short answer
Gorgias can receive a TheFork enquiry as a ticket. It cannot do anything with it in TheFork Manager. Checking the shift, holding a table, applying a promotion or set menu, noting a request: all of that still happens by hand, in TheFork Manager, by a person.
Gorgias + TheFork | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Gorgias'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. It is still the wrong shape for handling enquiries, for a reason TheFork states itself.
What actually happens to a booking enquiry
Groups on TheFork take a steady flow of enquiries from the network, often in another language, and once you also sell online, one email carries two jobs.
A guest writes in French. They bought a gift voucher from your online shop, ask whether it can be combined with the promotion they saw on TheFork, and want a table for eight this Saturday evening. The message becomes a Gorgias ticket.
Gorgias handles the voucher half well. The order sits alongside the message because it lives in Shopify, and AI Agent can confirm the balance, the expiry and the terms without a human.
The booking half waits for a person. An agent opens TheFork Manager in another tab, because Gorgias cannot see the shift or the promotion rules.
They check Saturday availability for eight, confirm which sessions the promotion covers and whether it excludes peak slots or large parties, and work out whether it can stack with a voucher at all.
They create the booking in TheFork Manager, re-keying the name, date, time, party size and the notes from the email.
They switch back to Gorgias and write the reply, in French if someone on shift can, in English if not, and covering both the voucher and the promotion.
They mark the ticket closed.
The guest replies: "Can we push it to 9pm?" The promotion may not cover 9pm. The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. Steps two and three are the ones to read together: Gorgias answered a question about its own commercial record instantly and had nothing to offer about a table. One operations director described the inbox behind this workflow as "a black hole, no KPIs, no response rate, nothing," because the booking work happened in tabs and tickets that no report could see. When you pay commission on network covers, being unable to measure what happens to those enquiries is an expensive blind spot.
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, so a slow reply is not a delay, it is a lost cover to a competitor on the same platform. 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." Gorgias did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Gorgias actually connects to
Gorgias is the counter-example that proves the rule, so it deserves a fair and precise description.
Most helpdesks in this comparison cannot take real actions on anything. Gorgias can. Its App Store is organised around e-commerce, shipping, marketing, loyalty, analytics and support channels, with Shopify at the centre and apps like Magento, NetSuite, Klaviyo, Recharge and Tapcart alongside. Its AI Agent, the Automate product, is an autonomous support and sales agent for e-commerce brands: it answers order questions, recommends products, and performs genuine transactions such as looking up an order, cancelling one, editing a delivery address or changing a subscription. That is a helpdesk completing work inside the conversation, which is rare and real.
So the argument here is not that a helpdesk cannot act. It is that Gorgias can act because it was purpose-built around one system of record, and that system of record is Shopify. A reservation platform is a different system of record, and Gorgias has no line into one. Search the Gorgias App Store for TheFork and you will find nothing.
TheFork's side is more open than most, 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. 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 Gorgias's Zapier app has nothing to connect to, and the realistic route is a custom project against both APIs. AI Agent will not fill the gap, because its action library comes from your connected e-commerce systems. It can confirm the voucher and cannot see Saturday.
One honest credit worth giving. If you sell gift vouchers, gift cards or merchandise online, Gorgias is genuinely good at that side and the AI Agent will resolve much of it without a human. The gap is bookings, not the whole tool.
Why this matters for booking enquiries
A support ticket and a booking enquiry look similar and behave nothing alike. A support ticket is resolved by a reply, or in Gorgias's case sometimes by an autonomous action. A booking enquiry is only resolved when a table is held in the diary. That difference is the whole problem.
Gorgias proves the point rather than escaping it. It shows what a helpdesk looks like when someone builds it around the transaction an industry runs on. Nobody has done that for restaurant bookings inside Gorgias, so the transaction that earns the cover still lands on your team, one enquiry at a time.
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 helpdesk organised around a shop instead of a diary.
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 Gorgias 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. Gorgias reports on tickets and the revenue its agents influence, 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 Gorgias integrate with TheFork?
No. Gorgias has no native integration with TheFork, and no restaurant booking system appears in the Gorgias App Store. TheFork is not on Zapier either, so Gorgias's Zapier app does not help. Bridging the two means a custom development project against Gorgias's API and TheFork's B2B API, and even then it only copies enquiry data into a ticket. It cannot check live availability or create a booking.
Can TheFork's API connect it to a helpdesk?
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.
Gorgias AI Agent can confirm a voucher, so why can't it book a table?
Because its actions come from the systems Gorgias was built around. AI Agent performs real transactions such as order lookups, cancellations, address edits and subscription changes, because Gorgias is wired into Shopify and the e-commerce stack. A reservation platform is a different system of record, and Gorgias has no connection to one. The capability is real, the scope is e-commerce.
What do restaurant groups use instead for booking enquiries?
Most run booking enquiries through a shared inbox even when a helpdesk covers customer service and the online shop, because the helpdesk 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.
