No. Intercom has no native, purpose-built integration with Tock. You can connect the two loosely through Zapier, and the result still cannot check availability, move a prepaid seat or resolve a deposit inside the conversation. Intercom is a customer-messaging platform built around web chat and its AI agent, Fin. Tock is a reservation platform built around prepaid bookings, deposits, ticketed events and tasting menus. Fin can explain your deposit policy beautifully. It cannot refund one.
The short answer
Intercom can receive a Tock enquiry as a conversation. It cannot do anything with it in Tock. Checking the calendar, rescheduling a prepaid booking, releasing or transferring a deposit: all of that still happens by hand, in Tock, by a person.
Intercom + Tock | |
|---|---|
Native integration | None |
Best available workaround | A Zapier or custom-API bridge that copies enquiry text into a conversation |
What the workaround still can't do | Check availability, reschedule a prepaid booking, move or refund a deposit, read booking history |
Both ends here are reachable, which makes the ceiling clearer. Intercom has a developer platform and Zapier support. Tock offers an API and webhooks and works with Zapier. The limitation is not connectivity. It is that a messaging platform has no concept of a reservation.
What actually happens to a booking enquiry
Before the workflow, one mismatch worth naming. Intercom is chat-first, and genuinely good at it. Tasting-menu and event bookings are researched and negotiated by email, often days or weeks ahead, by people who want the details in writing because they have paid up front. A chat widget is not where that conversation naturally happens.
Here is the real journey of one enquiry when Intercom and Tock do not talk to each other.
A guest messages to ask whether the deposit on their tasting-menu booking for two is refundable, because they need to move from the 14th to the 21st. The message becomes an Intercom conversation.
An agent picks it up and reads it.
The agent opens Tock in another tab, because Intercom cannot see the calendar or the payment.
They find the booking, check the deposit terms against how close the original date is, and look at whether the 21st has a table of two at the right seating.
They move the booking in Tock and carry the deposit across, or refund and re-take it if the terms require that.
They switch back to Intercom and write the reply, being precise about what happened to the money.
They close the conversation.
The guest replies: "Can we make it four, and one is pescatarian." Party size changes the deposit total, so the agent repeats steps 3 to 7 and reworks the payment.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. On a prepaid platform the double-handling has a financial edge to it: a deposit refunded that should have been transferred, a seat released that should have been held. 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.
The sharper cost is the enquiry you never hear about again. Chat promises an instant answer that a kitchen-side team cannot deliver during service, and the enquiries that arrive by email in the evening wait until morning. 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." Intercom did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Intercom actually connects to
The Intercom App Store is substantial: CRMs, analytics, developer tools, billing platforms, marketing automation. It reflects Intercom's core market, which is software and SaaS companies running support and engagement at scale. No restaurant booking system appears in it, and Tock is no exception.
Tock is more open than most of its peers, and that is worth stating accurately. It offers a data API and webhooks, gated to Premium and Premium Unlimited plans and provisioned on request rather than self-serve, and it works with Zapier. So a zap that opens or updates an Intercom conversation when something happens in Tock is genuinely buildable without engineering.
Then look at what you have. A Tock booking event can create or update an Intercom conversation. That is one-directional notification. It does not let an agent see the calendar, hold a seat, reschedule a prepaid booking, or move a deposit from inside the conversation. Fin, Intercom's AI agent, is genuinely strong: it answers from your help content and past conversations, resolves routine queries end to end, and hands off cleanly. It has no line into the calendar. Fin can quote the deposit terms. It cannot check the 21st or move the money. Any actions Fin performs are limited to systems you have already wired up, which brings you back to a gated API and a custom build.
There is also a multi-site fit issue. Intercom is built around one product and one brand voice, and a group running several venues with different menus and policies has no native concept of which venue an enquiry belongs to.
One piece of context before investing. American Express announced in February 2026 that Tock is merging into Resy, with venues unifying on Resy through summer 2026 and the consumer Tock app and exploretock.com being retired. Tock's restaurant-facing management software continues to operate as part of Resy, and API key requests already route through a Resy address.
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 seat is held in the calendar, and on Tock, usually paid for. That difference is the whole problem.
The messaging platform 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. This is why most groups that run Intercom for customer messaging still run their booking enquiries through a shared Gmail or Outlook inbox. The platform never solved the booking side, so the old inbox stayed, and with it the double-handling and the black box.
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 a chat inbox that closes the conversation and moves on.
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 Intercom 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. Intercom reports on conversations and resolution rates, 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. 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."
If you are weighing the two, the fuller comparison is in RevVue vs Intercom, and the wider options are covered in Intercom alternatives for restaurant groups. If you are consolidating onto Resy, the same question applies there: does Intercom integrate with Resy. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes.
Frequently asked questions
Does Intercom integrate with Tock?
No. Intercom has no native integration with Tock. Because Tock offers an API and works with Zapier, you can build a bridge that opens or updates an Intercom conversation when a Tock booking changes, but it only moves information one way. It cannot check availability, reschedule a prepaid booking, or move a deposit. That work still has to be done by hand in Tock.
Can Fin handle a deposit or reschedule a Tock booking?
No. Fin is one of the stronger AI agents available and can answer from your help content, resolve routine questions and escalate cleanly. It has no connection to a reservation system. Fin can quote your deposit and cancellation terms accurately, but it cannot check another date, move the booking, transfer the deposit or issue a refund. Fin's actions are limited to systems you have already connected, and Tock's API is gated to Premium plans and provisioned on request.
Is Tock shutting down now that it has merged with Resy?
The consumer side is being retired, not the venue software. American Express announced in February 2026 that Tock is merging into Resy, with venues unifying on Resy through summer 2026 and the Tock app and exploretock.com being wound down. Tock's restaurant-facing management software continues to operate as part of Resy. If you are planning a custom integration, factor in that the platform underneath is consolidating.
What do restaurant groups use instead for booking enquiries?
Most run booking enquiries through a shared Gmail or Outlook inbox even when they use Intercom for customer messaging, because the platform 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 Tock integration is on the roadmap, with an email-only pilot available now.
