No. Zendesk has no native, purpose-built integration with Collins by DesignMyNight, and any bridge you build still cannot check space, take a deposit, or confirm a booking inside the conversation. Zendesk is a customer-service helpdesk. Collins is the venue-side management software late-night, competitive-socialising and events venues use to run 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 big private-hire enquiry loses momentum, and where the deposit never gets taken.
The short answer
Zendesk can receive a Collins enquiry as a ticket. It cannot do anything with it in Collins. Checking area availability, building the package, taking the deposit, logging the pre-order, moving a private hire from one room to another: all of that still happens by hand, in Collins, by a person.
Zendesk + Collins | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Zendesk's API and the Collins API |
What the workaround still can't do | Check area availability, take a deposit, build or amend a package booking, read the enquiry's history in Collins |
What actually happens to a booking enquiry
Large-party and private-hire enquiries are where this hurts most, because they carry deposits, pre-orders and package spend that a single missed reply throws away. Here is the real journey of one enquiry when Zendesk and Collins do not talk to each other.
A guest emails to book a private-hire area at your competitive-socialising venue for a work party, 24 people, two hours of gameplay, a drinks package and a food pre-order, in three weeks. The message becomes a Zendesk ticket.
An agent opens the ticket and reads it.
The agent opens Collins in another tab, because Zendesk cannot see the venue's areas or availability.
They check the area, date, and slot for that party size, by hand.
They build the enquiry in Collins, re-keying the guest's name, date, party size, the package, the pre-order, and the note about two guests who do not drink.
They switch back to Zendesk and write the reply with the deposit terms.
They mark the ticket solved.
The guest replies: "Can we add six people and swap to the later slot." The agent repeats steps 3 to 7, and re-checks whether the deposit figure still holds.
Every enquiry is handled twice, in two systems, by a person copying package details, deposit terms and pre-orders from one screen to another. For a venue where a single private hire can be worth a full evening's revenue, that double-handling is not admin, it is the deal slowing down at the exact moment it should be closing. One operations director we spoke to described the inbox behind this as "a black hole, no KPIs, no response rate, nothing," because the work all happened in tabs and tickets 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 and hold it before the group books a competitor, and the double-handling above takes time you rarely have when enquiries arrive late at night. 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." Zendesk did not cause those losses. But routing enquiries through a system that cannot take a deposit is what makes the delay inevitable.
What Zendesk actually connects to
Zendesk has a large marketplace of integrations: CRMs, e-commerce platforms, telephony, analytics. What it does not have is a connection to venue-management systems, because those are not tools its core market (software, retail, financial services) uses. Search the Zendesk Marketplace and you will find Salesforce and Shopify, not Collins.
Because Collins connects out to POS, payment and property systems through its own API rather than exposing a general automation connector, teams who want it to talk to Zendesk cannot wire it up with an off-the-shelf tool. The realistic route is a custom build against Zendesk's API and the Collins API. That is an engineering project, and even when it is finished it moves information in one direction and treats each enquiry as a support ticket. It does not let an agent check area availability, build a package, or take a deposit back in Collins. Zendesk AI, the platform's answer bot and agent copilot, can suggest a reply from your knowledge base and past tickets, but it has no line into Collins and cannot take a single action inside it, deposit included. So the "integration" is really a copy of the enquiry sitting in a second system, and the actual booking work, steps 3 to 7 above, is unchanged.
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. A private-hire enquiry is only resolved when the area is held, the package is built, and the deposit is taken in the booking system. That difference is the whole problem.
The helpdesk can write a polished reply. It cannot hold the room or take the deposit. The transaction, the part that actually earns the party, still lands on your team, one enquiry at a time. This is why most late-night and competitive-socialising operators that run Zendesk for customer service (vouchers, refunds, complaints that need finance) still run their booking enquiries through a shared Gmail or Outlook inbox. The helpdesk 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 booked 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 venue's areas or availability. 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 tickets and tabs.
The AI reads each enquiry and drafts the reply in that venue's own tone, grounded in its packages, deposit terms, and FAQs. The agent reviews and sends with one click rather than retyping package and deposit details 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 Zendesk 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 ticket-and-tabs 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. 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 enquiries 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 Zendesk, and whether the helpdesk fits a multi-site operator at all is covered in is Zendesk right for restaurant groups. 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 Zendesk integrate with Collins?
No. Zendesk has no native integration with Collins by DesignMyNight. You could commission a custom build on Zendesk's API and the Collins API to copy an enquiry into a ticket, but it cannot check area availability, take a deposit, or build a package booking in Collins. That work still has to be done by hand.
Is there a Collins connector for Zendesk?
No. Collins connects to POS, payment and property systems through its own API, not through a general automation tool that would raise a Zendesk ticket. Bridging the two means a custom development project, and even then it only moves enquiry data one way as a support ticket. It cannot check space, take a deposit, or confirm a package booking inside the conversation.
Why doesn't Zendesk work with venue-management systems?
Because Zendesk was built for customer-service tickets, not reservations and events. Its market is software, retail, and financial services, so its integrations are CRMs and e-commerce tools, not Collins or Design My Night. Handling a private-hire enquiry needs the tool to read availability and write bookings, deposits and packages, which a support helpdesk is not designed to do.
What do late-night and competitive-socialising venues use instead for booking enquiries?
Most run booking enquiries through a shared Gmail or Outlook inbox even when they use Zendesk for customer service, 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 Collins integration is on the roadmap, with an email-only pilot available now.
