No. Re:amaze has no native, purpose-built integration with TheFork, and no restaurant booking system appears anywhere in its integration list. Re:amaze is a multi-channel helpdesk for small and mid-sized e-commerce businesses, owned by GoDaddy. TheFork is Tripadvisor's European booking network plus TheFork Manager, the venue-side reservation software. TheFork is the best documented booking system in this comparison, and that makes the ceiling clearer instead of higher.
The short answer
Re:amaze can gather a TheFork-related enquiry from email, chat, SMS or a social DM and give it an owner and a response time. It cannot act on it inside TheFork Manager. Checking availability, seating a party of ten, adding the note about a quiet table and confirming back to the guest all still happen by hand, by a person, in another system.
Re:amaze + TheFork | |
|---|---|
Native integration | None |
Best available workaround | A custom build on TheFork's B2B API |
What the workaround still can't do | Check live availability, create or amend a booking, or answer inside the conversation |
The detail that decides this pairing is in TheFork's own documentation. It publishes a B2B API developer portal aimed at CRM platforms and large restaurant groups, and it describes the API as data synchronisation "without the need for real-time updates." That sentence is the whole answer. It is a batch sync surface built for point-of-sale and CRM systems, not a live availability-and-booking interface for a support conversation. TheFork has no Zapier connector either, so there is no low-code route.
What actually happens to a booking enquiry
Give Re:amaze the credit it is owed. A restaurant taking covers from a network gets inbound from several directions at once: the network's own messaging, direct email, WhatsApp, Instagram and the chat widget. Consolidating that into one queue with an owner and a response time, cheaply, is a real improvement for a small group.
Here is one enquiry, all the way through.
A guest books through the network, then emails the venue directly in French to add a highchair and ask about parking. Re:amaze queues and assigns it.
An agent opens it and reads it, possibly running it through a translation first.
The agent opens TheFork Manager in another tab, because Re:amaze cannot see the booking.
They find the reservation that came in through the network, confirm the table can take a highchair, and check what the venue tells people about parking that night.
They add the note to the booking in TheFork Manager, re-keying the request.
They switch back to Re:amaze and reply, in French.
They close the conversation.
The guest replies: "We are now ten, not six, and we would like the set menu." Ten is a different table and may not be available through the network allocation at all. The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person copying details between screens. There is an extra tax in this pairing, which is language: a European network sends you guests who write in their own, and the person who can answer in French may not be the person on shift. Re:amaze made sure the email was seen. It has no idea whether the party of ten was seated, because the covers live in TheFork Manager. One operations director described the inbox behind this workflow as "a black hole, no KPIs, no response rate, nothing."
The commercial edge here is specific. Covers that arrive through the network carry commission. Covers that arrive by direct email do not. So the enquiries sitting unanswered in a slow inbox are precisely the ones with the best margin, and they are the ones a busy team gets to last. 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."
What Re:amaze actually connects to
Re:amaze's integration list states its market clearly: Shopify, BigCommerce, Magento, WooCommerce, WordPress, Stripe, Google Workspace, Slack, Jira, Aircall, JustCall, RingCentral and Pipedrive, plus Zapier. More than 5,000 e-commerce brands across more than 100 countries use it, and it rates highly on the Shopify and BigCommerce app stores.
No restaurant booking system appears in it. Re:amaze is built and priced for e-commerce businesses, and a European restaurant group taking covers from a booking network is not the customer it was designed around.
The workaround deserves care here, because TheFork's openness invites the wrong conclusion. Its documented B2B API is genuinely more accessible than SevenRooms' closed partner API or Resy's absent one, and a competent developer could build against it. What they would build is a data sync: bookings and covers copied between systems on a schedule. TheFork's own framing, synchronisation without real-time updates, rules out the thing a booking enquiry needs, which is a live answer to "is this available right now." A well-documented batch API does not become a booking engine because you connect a helpdesk to it. And with no Zapier connector on TheFork's side, even the cheap version of this is unavailable.
Re:amaze's AI drafts replies, summarises conversations and powers chatbots, with much of the suite carrying a beta label. It is real, less mature than the AI in the pricier tools, and grounded in past conversations and help-centre content. It can help draft a reply in another language. It cannot tell you whether ten people can be seated on Saturday.
One more gap matters for a group. Re:amaze can manage multiple businesses in one place, which separates brands rather than the availability behind them, and it reports on conversations rather than covers, so you cannot see which site is converting its direct, commission-free demand.
Why this matters for booking enquiries
A support conversation and a booking enquiry look alike and behave nothing alike. A support conversation is resolved by a reply. A booking enquiry is resolved only when a table is held. An API that syncs data on a schedule serves the first definition and not the second.
Re:amaze gets the message to a person on whatever channel it arrived, in whatever language. It cannot seat the party. The work that turns a direct enquiry into a commission-free cover stays manual, in another system, and slow.
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 one multi-channel queue that still treats every site the same.
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 Re:amaze 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. Re:amaze reports on conversations, response times and volume per channel, 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 not live. That is the honest status. Restaurants run an email-only pilot now, which already delivers the inbox value shown above: location-aware routing, instant acknowledgement, AI-drafted replies, high-value bookings surfaced and held for a person, and reporting by location. 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."
Since a good share of these enquiries arrive from the booking network and from third-party sites, automating third-party booking emails is the most relevant read next, and shared inbox software for restaurants is the wider category view. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes.
Frequently asked questions
Does Re:amaze integrate with TheFork?
No. Re:amaze has no native integration with TheFork, and no restaurant booking system appears in its integration list. TheFork has no Zapier connector either, so the only route is a custom build on its B2B API. TheFork documents that API as data synchronisation without the need for real-time updates, which is exactly what a booking enquiry cannot use.
TheFork publishes an API. Why is that not enough?
Because of what the API is for. It is aimed at CRM platforms and large groups, and TheFork's own documentation frames it as batch synchronisation rather than real-time access. A booking enquiry needs a live answer to whether a table is available at a specific time, and then the ability to hold it. Syncing yesterday's covers into a helpdesk on a schedule does not provide either.
Is Re:amaze a good choice for a restaurant taking network covers?
It is a fair, affordable answer to scattered channels, which is a genuine problem when guests message through the network, by email and by DM. It is a poor answer to booking enquiries. It is built and priced for e-commerce businesses, it has no line into TheFork Manager, and it has no concept of which venue an enquiry belongs to.
What do TheFork restaurants use instead for booking enquiries?
Most keep a shared inbox alongside TheFork Manager and accept that every enquiry is handled twice, which is costly given that direct enquiries carry no commission. 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.
