No. Intercom has no native, purpose-built integration with Collins, and any workaround you build still cannot check availability, hold an area, or create a booking inside the conversation. Intercom is a customer-messaging platform. Collins, by DesignMyNight, is the venue-management and booking software that late-night, competitive-socialising and events-led venues run for large-party enquiries, deposits, pre-orders, and package and area bookings. They were built for different jobs, and the gap between them is exactly where a venue's most valuable private-hire enquiries fall, and where they get lost.
The short answer
Intercom is built around web chat and a genuinely good AI agent called Fin. Neither of those is the same as a held area. A Collins booking is only real once the area is held, the deposit is logged, and the package is attached in the diary, and Intercom has no way to do any of that. Checking the space, holding it, adding the pre-order, taking the deposit, moving a party from 8pm to 9pm: all of that still happens by hand, in Collins, by a person.
Intercom + Collins | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Intercom's API and the Collins API |
What the workaround still can't do | Check live availability, hold an area, take a deposit, create or amend a package booking |
What actually happens to a booking enquiry
Numbers on a table do not show the cost. The workflow does. Here is the real journey of a single enquiry when Intercom and Collins do not talk to each other, and for a competitive-socialising venue these are the enquiries worth the most.
A guest emails a late-night competitive-socialising venue to ask about private hire of a room for 30 next Saturday, with a drinks package and a food pre-order. The message lands as an Intercom conversation.
An events coordinator opens it and reads it.
They open Collins in another tab, because Intercom cannot see the diary, the areas, or the packages.
They check availability of the space for that date and party size, and price the package, by hand.
They set up the enquiry in Collins, re-keying the guest's name, date, time, party size, the package, and the pre-order note from the email, then raise the deposit request.
They switch back to Intercom and write the reply.
They close the conversation.
The guest replies: "Can we make it 36, and add a second round of the sharing platters." The coordinator repeats steps three to seven.
Every enquiry is handled twice, in two systems, by a person copying the same fields from one screen to another. For a venue whose revenue leans on private hire, that double-handling sits on exactly the enquiries that matter most. One operations director described the inbox behind this as "a black hole, no KPIs, no response rate, nothing," because the work all happened in tabs and conversations that no report could see.
The sharper cost is the one you never find out about. A private-hire enquiry is only worth anything if you answer it before the party books another venue, and the double-handling above takes time you often do not have out of hours, which is precisely when late-night enquiries arrive. A roughly 40-venue entertainment group lost a single booking worth £40,000 because the enquiry arrived outside working hours and no one 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. But routing high-value hires through a tool that cannot hold an area is what makes the delay inevitable.
What Intercom actually connects to
Intercom's App Store is deep in the tools its core market uses: CRMs, product analytics, billing, developer and SaaS platforms. It is built for software companies running large support and engagement operations. Venue-management systems like Collins are not part of that world, so there is no Collins connector to switch on.
Its AI agent, Fin, is the reason many venues reach for Intercom in the first place. Fin is strong. It resolves questions from conversation history and support content, and it holds a natural conversation. What it has no awareness of is a booking system. Fin cannot open the Collins diary, hold an area, attach a package, take a deposit, or write a booking back. It can qualify and answer up to the point a hire needs confirming, then a person has to build it by hand.
There are two further mismatches worth naming. Private-hire and large-party enquiries in UK hospitality are still mostly email, and Intercom is built web-chat-first, so an events team that has lived in Outlook or Gmail is being asked to move to a chat-style interface for a job that is not chat-shaped. And a group running several venues cannot give each one its own tone, packages, and knowledge inside Intercom's single-product model, so the replies drift toward one generic voice.
A tech-forward operator might attempt a custom bridge between Intercom's API and the Collins API. Even done well, it becomes a data-sync project to build and maintain, and it still stops short of the thing that matters: Fin cannot open the diary, hold the area, log the deposit, and write the package booking back mid-conversation. The enquiry moves. The booking does not.
Why this matters for booking enquiries
A support conversation and a private-hire enquiry look similar and behave nothing alike. A support conversation is resolved by a reply. A hire enquiry is only resolved when the area is held, the deposit is taken, and the package is confirmed in the booking system. That difference is the whole problem.
Intercom can write a polished reply. It cannot hold the room or take the deposit. The transaction, the part that actually earns the revenue, still lands on your events team, one enquiry at a time. This is why most competitive-socialising and late-night operators that run a messaging tool for support still run their booking enquiries through a shared Gmail or Outlook inbox. The messaging 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 inbox and the booking system are the same surface, so the enquiry is answered and the hire is progressed in one place. This is what RevVue does, and it is easier to show than to describe.
Every enquiry is tagged to the right venue automatically, so a private-hire request for one site is never answered with another site's spaces or packages. The team works from one queue, by location, instead of a folder maze.
Every enquiry lands in one place, tagged to the venue it is for, instead of scattered across conversations and tabs.
The AI reads each enquiry and drafts the reply in that venue's own tone, grounded in its spaces, packages, and policies. The events coordinator reviews and sends with one click rather than retyping from scratch.
The AI drafts the reply in the venue's voice and waits for one-click approval, so the team reviews instead of re-keying.
Because it connects to the booking system, the AI does the step Intercom cannot: it checks availability and prepares or creates the booking inside the same thread. Routine enquiries are handled on arrival, and the high-value ones, the private hires and large parties, are acknowledged instantly and held in a prioritised queue for a person to nurture, so the £40,000 enquiry is never the one that sits unseen.
High-value bookings the AI has acknowledged and prepared, waiting in a queue the team actually works rather than buried in an inbox.
And because every enquiry is tracked by location, the black box becomes a dashboard: response rates, volumes, and conversion by site, the numbers the tabs-and-conversations workflow could never produce.
Response rate, volume, and conversion by location, so the inbox stops being a black box and starts being something you can manage.
An honest note on where RevVue is today
RevVue's Collins integration is on the roadmap, and the group runs an email-only pilot now. That is the honest status. The pilot already delivers the inbox value shown above: location-aware routing, instant acknowledgement around the clock, AI-drafted replies in each venue's voice, high-value hires surfaced, and reporting by location. The UK AI is in pilot. The booking-system connection deepens that later, it does not gate the value today.
This is the move the Brasilia Group made, off a horizontal tool 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 messaging-first tools, the fuller picture is in the Intercom alternative for restaurant groups and RevVue vs Intercom, and the category overview is in shared inbox software for restaurants. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes or email karan@revvue.ai.
Frequently asked questions
Does Intercom integrate with Collins?
No. Intercom has no native integration with Collins, the DesignMyNight venue-management system. A custom build on Intercom's API and the Collins API can sync some data, but it cannot check availability, hold an area, take a deposit, or create a package booking inside a conversation. That work still has to be done by hand in Collins.
Can Intercom's Fin AI take a private-hire booking?
No. Fin is a strong conversational agent that resolves questions from conversation history and support content, but it has no connection to a venue-management system, so it cannot check the diary, hold an area, or take a deposit. It can hold the conversation up to the point a hire needs confirming, then a person has to build it in Collins.
Is Intercom a good fit for large-party and events enquiries?
It is a strong fit for a software company's support and engagement, less so for venue hires. It is web-chat-first while hire enquiries are mostly email, it has no connection to Collins, and its single-product model makes per-venue tone and packages hard for a multi-site operator. The reply is good, but holding the area and taking the deposit still falls to the events team.
What do late-night and competitive-socialising venues use instead?
A purpose-built option is RevVue, which is email-first, location-aware, and gives each venue its own tone and knowledge, with an AI that checks availability and progresses the booking in the conversation. Its Collins integration is on the roadmap, with an email-only pilot available now that delivers value on the inbox first.
