No. Re:amaze has no native, purpose-built integration with Tock, 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. Tock is a reservation platform built around prepaid bookings, deposits, ticketed events and tasting menus. Both platforms handle money. Only one of them will let Re:amaze near it.
The short answer
Re:amaze can gather a Tock enquiry from email, chat, SMS or a DM and give it an owner and a status. It cannot act on it inside Tock. Checking what is available, moving a prepaid seat, changing a menu selection or working out what a refund costs all still happen by hand, in Tock, by a person.
Re:amaze + Tock | |
|---|---|
Native integration | None |
Best available workaround | A Zapier or custom-API bridge that copies enquiry data into a conversation |
What the workaround still can't do | Check availability, amend a prepaid booking, change a menu selection or process a refund |
One piece of current context belongs on this page. American Express announced in February 2026 that Tock is merging into Resy, with venues moving onto Resy through summer 2026. The consumer Tock app and exploretock.com are being retired, while Tock's restaurant-facing software continues to operate as part of Resy. API key requests already route to a resy.com address. If you are choosing support software around Tock right now, that transition is worth factoring in, and it makes a bespoke integration a riskier thing to commission.
What actually happens to a booking enquiry
Give Re:amaze the credit first. A tasting-menu restaurant gets a specific kind of inbound: detailed, high-value, and arriving on whatever channel the guest prefers. Re:amaze pulls email, chat, SMS and social into one queue with an owner and a response time, at a price a single-site operator can afford. For a small team that is a real gain over checking four apps.
Here is one enquiry, all the way through.
An email arrives about a prepaid tasting-menu booking for six, asking to swap two seats to the vegetarian menu and move the date by a week. Re:amaze queues and assigns it.
An agent opens it and reads it.
The agent opens Tock in another tab, because Re:amaze cannot see the booking or the payment.
They find the reservation, check whether the new date has six seats at that sitting, check whether the vegetarian menu is priced differently, and work out what the change does to the amount already paid.
They amend the booking in Tock, adjust the menu selections, and either take a further payment or process a partial refund.
They switch back to Re:amaze and write the reply explaining the money.
They close the conversation.
The guest replies: "One of the six can't make it now." That is a cancellation inside a prepaid booking, with its own refund rule. The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person moving between screens. What makes a Tock site different is that the second system holds money. A mistake in step five is not an inconvenience, it is a wrong refund or an unpaid seat. Re:amaze made sure the email was answered quickly and has no record of what the change cost. One operations director described the inbox behind this workflow as "a black hole, no KPIs, no response rate, nothing."
The sharper cost is the guest who never books at all. A six-cover tasting menu is a significant sum, and someone deciding between two restaurants will take the one that answers the awkward question first. 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 plainly: Shopify, BigCommerce, Magento, WooCommerce, WordPress, Stripe, Google Workspace, Slack, Jira, Aircall, JustCall, RingCentral and Pipedrive, plus Zapier. More than 5,000 e-commerce brands in more than 100 countries use it.
There is an irony worth naming. Re:amaze integrates deeply with Stripe and Shopify, so it is thoroughly comfortable showing an agent a customer's payment history. It simply has no line into the one payment system that matters for a Tock restaurant, which is Tock itself. A helpdesk that can show you a Shopify refund cannot show you a deposit on a tasting menu.
Both Re:amaze and Tock are on Zapier, so a bridge is possible here. Re:amaze's connector authenticates with the API credentials in its settings and offers triggers for new conversations and messages plus actions to create contacts and add messages. Tock's own API and webhook programme is gated to Premium and Premium Unlimited plans and provisioned on request. Build the bridge and be clear about the ceiling: enquiry or booking data can create and update a conversation, one direction. It cannot check what is available, move a prepaid seat, change a menu or touch a refund. And with venues moving onto Resy through 2026, anything bespoke you build has a shelf life.
Re:amaze's AI drafts replies, summarises conversations and powers chatbots, and a good part of that suite has carried a beta label. It is real, it is less mature than the AI in the pricier platforms, and it works from past conversations and help-centre content. It can draft the sentence explaining the change. It cannot calculate what the change costs.
One more gap matters for a group. Re:amaze can manage multiple businesses in one place, which separates brands rather than the availability or the payments behind them, and it reports on conversations rather than covers or revenue.
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 prepaid booking enquiry is resolved only when the diary and the payment both change. That second clause is what makes this pairing expensive.
Re:amaze routes the message to a person quickly. It cannot amend the booking, and it certainly cannot handle the money. Every amendment stays a manual job in a system the inbox cannot see, at a restaurant where amendments are most of the inbound volume.
What it looks like when the tool is built for booking enquiries
The gap closes when the enquiry and the booking are handled in one place, so a question about a prepaid seat does not turn into an admin job. This is what RevVue does, and it is easier to show than to describe.
Every enquiry is tagged to the venue it concerns, which matters for a group where each site sells a different ticketed experience. A question about one tasting menu is never answered with another restaurant's seating times, because the team works from one queue, by location, rather than one multi-channel queue that still treats every site the same.
Enquiries sorted by venue, so each ticketed experience is answered with its own detail.
The AI drafts the reply in that venue's voice, grounded in its menu, its cancellation terms and its prepayment rules. Those terms are the substance of most of these enquiries, and getting them into the first reply is most of the work.
The draft arrives carrying the venue's own terms, ready for one-click approval.
Because it connects to the booking system, the AI takes the step Re:amaze cannot: it checks availability and prepares the booking in the thread. Simple questions resolve on arrival, and anything touching money, a party growing by four seats or a date moving, is acknowledged instantly and queued for a person, because those are the ones with a payment attached.
Amendments and high-value bookings held for approval, since each one carries a payment.
And because every enquiry is tracked per venue, the admin around prepaid bookings becomes measurable. How many amendments each site handles, how fast it replies, and how much of that work is repeating itself. Re:amaze reports on conversations, response times and volume per channel, which does not tell you what the amendment work cost.
Volume, response rate and conversion by location, including the amendment traffic behind prepaid covers.
An honest note on where RevVue is today
RevVue's Tock integration is on the roadmap and not live. That is the honest status, and the Resy transition is a live factor in how that work is sequenced. 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."
If your amendments and enquiries arrive at all hours, handling booking enquiries 24/7 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 Tock?
No. Re:amaze has no native integration with Tock, and no restaurant booking system appears in its integration list. Both are on Zapier, so a bridge can be built that copies enquiry or booking data into a conversation, but it moves information one way. It cannot check availability, amend a prepaid booking, change a menu selection or process a refund.
Is Tock still a going concern after the Resy merger?
The venue-facing software is. American Express announced in February 2026 that Tock merges into Resy, with venues unified on Resy through summer 2026, and the consumer Tock app and exploretock.com are being retired while the restaurant management software continues as part of Resy. API key requests already route to a resy.com address. It is a live transition rather than a completed one, and it makes commissioning a bespoke integration around Tock a riskier investment.
Why does the missing integration cost more on a prepaid system?
Because every amendment carries money. On a standard diary a mistake means a wrong table. On Tock it means an incorrect refund, an unpaid seat or a menu billed at the wrong price. When the person answering the message cannot see the booking or the payment, each change becomes a manual reconciliation between two systems, and that is where the errors and the delays come from.
What do tasting-menu restaurants use instead for booking enquiries?
Most run a shared inbox next to Tock and absorb the double-handling. A purpose-built option is RevVue, which is location-aware and whose AI checks availability and prepares the booking inside the conversation, with high-value bookings acknowledged instantly and held for a person. Its Tock integration is on the roadmap, with an email-only pilot available now.
