No. Gorgias has no native, purpose-built integration with OpenTable, and no restaurant booking system appears in its App Store. Gorgias is a helpdesk built for e-commerce, wired deeply into Shopify. OpenTable is the front-of-house diary and the consumer reservation network that fills covers. The interesting part is not that Gorgias says no. It is that Gorgias will happily resolve the shop half of an email on its own and then stop dead at the booking half.
The short answer
Gorgias can receive an OpenTable enquiry as a ticket. It cannot do anything with it in OpenTable. Checking the diary, holding a table, seating a large party, noting a high chair: all of that still happens by hand, in OpenTable, by a person.
Gorgias + OpenTable | |
|---|---|
Native integration | None |
Best available workaround | A Zapier or custom-API bridge that copies enquiry text into a ticket |
What the workaround still can't do | Check availability, create or amend a reservation, seat a party, read the guest's dining history |
Both ends are reachable. Gorgias has a Zapier app, a developer API and a Gorgias MCP server on Zapier. OpenTable is on Zapier too, with deeper API access partner-gated. Connectivity is not the constraint, which is what makes this pairing worth looking at closely.
What actually happens to a booking enquiry
The clearest way to see the gap is a single email that asks two things, which happens constantly once a restaurant group sells anything online.
A guest emails to cancel the hamper they ordered from your online shop yesterday, and in the same message asks to book Sunday lunch for six, whether the roast is a set menu at that size, and whether you have a high chair. The message becomes a Gorgias ticket.
Gorgias handles the first half by itself. AI Agent looks up the order, confirms it has not shipped, cancels it and tells the guest the refund is on its way. No human touched it.
The second half waits for a person. An agent opens OpenTable in another tab, because Gorgias cannot see the diary.
They check Sunday for six, work out whether that is one table or two, look at what the kitchen takes at that sitting, and check high-chair availability.
They create the reservation in OpenTable, re-keying the name, date, time, party size and the high-chair note from the email.
They switch back to Gorgias and write the second half of the reply.
They mark the ticket closed.
The guest replies: "Two more are coming, so eight, and can we push to 1.30pm?" Eight changes the table plan and 1.30 may be a different turn. The agent repeats steps 3 to 7.
Read step two and step three next to each other, because that is the whole article. The same tool, in the same ticket, resolved a commercial transaction without human involvement and then could not answer a question 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.
The sharper cost is the enquiry you never hear about again. A guest who found you through the OpenTable network has a page of alternatives in the same postcode, so a slow reply is not a delay, it is a lost Sunday table. 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 diary is a different system of record, and Gorgias has no line into one. Search the Gorgias App Store for OpenTable and you will find nothing.
The workaround exists and is thin. Gorgias is on Zapier, OpenTable is on Zapier, and Gorgias publishes a developer API with endpoints for creating and retrieving integrations. So a zap that raises a Gorgias ticket from an OpenTable event, or pushes enquiry data across, is buildable without engineering. What it produces is notification, moving one direction, treating a reservation request as a support case. It does not let the agent see the diary, hold a table, create the reservation, or read what the guest ordered last visit. AI Agent will not close that gap either: its action library comes from your connected e-commerce systems, so it can cancel the hamper and cannot book the table.
One honest credit worth giving. If your group runs a real online shop, gift cards, vouchers, merchandise or hampers, Gorgias is genuinely good at that side and the AI Agent will resolve a lot 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 exactly what a helpdesk looks like when somebody builds it around the transaction an industry actually 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 one surface, so an enquiry that arrives by email is worth the same as one that arrives through the network. This is what RevVue does, and it is easier to show than to describe.
Every enquiry is tagged to the venue it is for the moment it lands. A group with sites in several cities stops relying on whoever recognises the address in the signature, and the team works from one queue, by location, rather than a helpdesk organised around a shop instead of a diary.
Enquiries arrive already sorted by venue, so nothing waits to be forwarded.
The AI drafts the reply in that venue's voice, using its menus, its policies and its own answers to the questions guests keep asking. The team reviews and sends instead of retyping the same explanation about set menus for the fourth time that week.
A drafted reply the team approves in one click, instead of writing the same answer again.
Because it connects to the booking system, the AI takes the step Gorgias cannot: it checks availability and prepares the booking in the same thread. The everyday requests resolve on arrival, and the large parties and private-hire enquiries are acknowledged immediately and queued for a person, so the slowest reply is no longer the biggest booking.
The bookings worth a person's time, acknowledged instantly and prepared for approval.
And because every enquiry is tied to a location, email covers become countable. You can see response times and conversion by site next to the covers the network sends you, and compare the two honestly for the first time. Gorgias reports on tickets and the revenue its agents influence, which tells you nothing about how many tables those conversations produced.
Volume, response rate and conversion by location, sitting alongside the covers the network delivers.
An honest note on where RevVue is today
RevVue's OpenTable integration is in active development. 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."
The wider category view is in shared inbox software for restaurants. Since a good share of these enquiries arrive from the booking network rather than your own site, automating third-party booking emails covers that specific problem. 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 OpenTable?
No. Gorgias has no native integration with OpenTable, and no restaurant booking system appears in the Gorgias App Store. Because both tools are on Zapier, and Gorgias publishes a developer API, a bridge is buildable that copies enquiry data into a ticket. It cannot check availability, create or amend a reservation, seat a party, or read the guest's dining history. OpenTable's deeper API access is partner-gated.
Gorgias AI Agent can cancel an order, 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 diary is a different system of record, and Gorgias has no connection to one. The capability is real, the scope is e-commerce.
What happens when one email asks about an order and a booking?
Gorgias resolves the order half well, often autonomously, and leaves the booking half for a person. The agent has to open the booking system in another tab, check availability, create the reservation and then come back to finish the reply. It is the clearest illustration of the gap, because the same ticket shows the tool at its best and at its limit.
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 OpenTable integration is in active development, with an email-only pilot available now.
