No. Zendesk has no native, purpose-built integration with Design My Night, and any bridge you build still cannot check availability or take a booking inside the conversation. Zendesk is a customer-service helpdesk. Design My Night is a consumer discovery, bookings and enquiry platform for bars, pubs, late-night and experiential venues. They were built for different jobs, and the gap between them is exactly where an experiential group's event enquiries stall, and where the biggest ones quietly go cold.
The short answer
Zendesk can receive a Design My Night enquiry as a ticket. It cannot do anything with it in Design My Night. Checking the venue's availability, taking the booking, logging the deposit terms, moving a party from Friday to Saturday: all of that still happens by hand, by a person, in the booking system.
Zendesk + Design My Night | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Zendesk's API and the Design My Night API |
What the workaround still can't do | Check availability, take or amend a booking, read the guest's booking and enquiry history |
What actually happens to a booking enquiry
Event enquiries are where this hurts most, because they are the ones worth the most. Here is the real journey of a single enquiry when Zendesk and Design My Night do not talk to each other.
A guest fills in a Design My Night enquiry form asking to hire a floor of your bar for a 30th birthday, 25 people, drinks package, next month. The message becomes a Zendesk ticket.
An agent opens the ticket and reads it.
The agent opens Design My Night in another tab, because Zendesk cannot see availability.
They check the venue, date, and space for that party size, by hand.
They type the enquiry into Design My Night, re-keying the guest's name, date, party size, package interest, and the note about a vegan in the group.
They switch back to Zendesk and write the reply with package options.
They mark the ticket solved.
The guest replies: "Can we do the Saturday instead, and it's now 30 people." The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person copying the same fields from one screen to another. For an operator running late-night and experiential sites, where each enquiry can carry a drinks package and a deposit, that double-handling is not admin, it is lost margin. 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. An event enquiry is only worth anything if you answer it before the group books another venue, and the double-handling above takes time you rarely have when enquiries land in the evening. 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 booking 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 restaurant and venue booking 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 Design My Night.
Because Design My Night connects out to POS, CRM 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 Design My Night 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 see live availability or take a booking back in Design My Night. 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 the booking system and cannot take a single action inside it. 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 booking enquiry is only resolved when the venue is held in the booking system. That difference is the whole problem.
The helpdesk can write a polished reply. It cannot book the space. The transaction, the part that actually earns the event, still lands on your team, one enquiry at a time. This is why most bar and experiential groups 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 floor-hire request for one bar is never answered with another site's 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, policies, and FAQs. The agent reviews and sends with one click rather than retyping package 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 floor 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 Design My Night integration is in active development. That is the honest status. Where the direct booking-system link is not yet live for a group, they 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 booking-system connection deepens that, it does not gate it. 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 Design My Night?
No. Zendesk has no native integration with Design My Night. You could commission a custom build on Zendesk's API and the Design My Night API to copy an enquiry into a ticket, but it cannot check availability, take a booking, or amend one in Design My Night. That work still has to be done by hand.
Is there a Design My Night connector for Zendesk?
No. Design My Night connects to POS, CRM 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 perform a live availability check or take a real booking inside the conversation.
Why doesn't Zendesk work with restaurant and venue booking systems?
Because Zendesk was built for customer-service tickets, not reservations. Its market is software, retail, and financial services, so its integrations are CRMs and e-commerce tools, not Design My Night or Collins. Handling a booking enquiry needs the tool to read and write to the booking system, which a support helpdesk is not designed to do.
What do bar and experiential groups 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 Design My Night integration is in active development, with an email-only pilot available now.
