No. Gorgias has no native, purpose-built integration with DesignMyNight, and DesignMyNight is not on Zapier either, so there is no low-code bridge to reach for. Gorgias is a helpdesk built for e-commerce, wired deeply into Shopify. DesignMyNight is the UK discovery, booking and enquiry platform used by bars, pubs, late-night and experiential venues, with Collins as its venue-side software. Gorgias can complete a commercial transaction inside a conversation. It cannot hold you an area on a Saturday.
The short answer
Gorgias can receive a DesignMyNight enquiry as a ticket. It cannot do anything with it in DesignMyNight or Collins. Checking capacity, holding an area, quoting a drinks package, taking a deposit: all of that still happens by hand, by a person.
Gorgias + DesignMyNight | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Gorgias's API and the DesignMyNight API |
What the workaround still can't do | Check availability, hold an area, quote or attach a package, take a deposit |
That middle row is thinner than it is for most booking systems, and the reason sits on the DesignMyNight side. Gorgias is well served on Zapier and publishes a developer API. DesignMyNight is not on Zapier at all, so the usual no-code shortcut does not exist.
What actually happens to a booking enquiry
Late-night and experiential venues get party enquiries as open questions about packages, not requests for a table at a time. Once you also sell anything online, a single thread starts doing two jobs.
Someone emails about a 21st birthday for 15 on a Saturday, asking what drinks packages you offer, whether a booth or area can be reserved, and whether they can bring a cake. They mention in passing that they bought two tickets to your Halloween event online last year and never used them. The message becomes a Gorgias ticket.
The ticket half about the old event tickets is easy. Gorgias shows that order alongside the message, because it lives in Shopify, and AI Agent can look it up and answer on refund eligibility without a human.
The party half waits for a person. An agent opens Collins in another tab, because Gorgias cannot see capacity or the area plan.
They check that Saturday for 15, see which booth or area is uncommitted at that time, look up current package prices and any minimum spend, and check the cake policy.
They pencil the area in, re-keying the date, numbers, package and the cake note from the enquiry.
They switch back to Gorgias and write the reply, with packages and the minimum spend.
They set the ticket pending, because a 21st is booked by committee.
Six days later: "It is 22 now and we want the upstairs area." Twenty-two changes the area, the minimum spend and the package maths. The agent repeats steps 3 to 7.
Every enquiry is handled twice, in two systems, by a person copying the same fields between screens. Steps two and three are the ones to read together, because the same tool resolved a paid-order question by itself and then could not tell anyone whether a booth was free. One operations director described the inbox behind this workflow as "a black hole, no KPIs, no response rate, nothing," because the booking work happened in tabs and tickets that no report could see.
The sharper cost is the enquiry you never hear about again. Someone organising a 21st sends the same message to five venues on a Tuesday night, and the first one back with a package and a price usually takes the deposit. 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." Gorgias did not cause those losses. Routing bookings through a system that cannot book anything is what makes the delay inevitable.
What Gorgias actually connects to
Gorgias is the counter-example that proves the rule, so it deserves a fair and precise description.
Most helpdesks in this comparison cannot take real actions on anything. Gorgias can. Its App Store is organised around e-commerce, shipping, marketing, loyalty, analytics and support channels, with Shopify at the centre and apps like Magento, NetSuite, Klaviyo, Recharge and Tapcart alongside. Its AI Agent, the Automate product, is an autonomous support and sales agent for e-commerce brands: it answers order questions, recommends products, and performs genuine transactions such as looking up an order, cancelling one, editing a delivery address or changing a subscription. That is a helpdesk completing work inside the conversation, which is rare and real.
So the argument here is not that a helpdesk cannot act. It is that Gorgias can act because it was purpose-built around one system of record, and that system of record is Shopify. A venue booking system is a different system of record, and Gorgias has no line into one. Search the Gorgias App Store for DesignMyNight and you will find nothing.
The workaround is unusually thin in this pairing. Gorgias is on Zapier and publishes a developer API, but DesignMyNight is not on Zapier, so there is no zap to assemble. DesignMyNight and Collins connect outward through their own APIs to point-of-sale, payment and marketing systems rather than exposing a general automation connector. That leaves a custom development project against Gorgias's API and the DesignMyNight API, which is a hard budget line for a bar or late-night group and delivers modestly: enquiry text copied into a ticket, one direction, treated as a support case. AI Agent will not fill the gap either, because its action library is built from your connected e-commerce systems. It can answer on last year's Halloween tickets and cannot reserve the upstairs area.
One honest credit worth giving. If your group sells event tickets, gift cards or merchandise online, Gorgias is genuinely good at that side and the AI Agent will resolve much of it without a human. The gap is bookings, not the whole tool.
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, or in Gorgias's case sometimes by an autonomous action. A party enquiry is only resolved when the space is held and the deposit is taken. That difference is the whole problem.
Gorgias proves the point rather than escaping it. It shows what a helpdesk looks like when someone builds it around the transaction an industry runs on. Nobody has done that for venue bookings inside Gorgias, so the transaction that earns the revenue still lands on your team, one enquiry at a time.
What it looks like when the tool is built for booking enquiries
The gap closes when the enquiry and the booking sit in one place, so a package question can be answered and held in the same reply. This is what RevVue does, and it is easier to show than to describe.
Enquiries are routed to the right bar or venue automatically, which matters when a group runs several late-night sites with different licences, layouts and last entry times. Nobody quotes the wrong venue's closing time, because the team works from one queue, by location, rather than a helpdesk organised around a shop instead of a diary.
Each site gets its own queue, so the answer always matches the venue that was asked about.
The AI drafts the reply in that venue's voice, grounded in its packages, its minimum spends and what the space can actually hold. Package enquiries are long and repetitive, and the draft arrives with those details already in it.
The package answer drafted in the venue's voice, waiting for one-click approval.
Because it connects to the booking system, the AI does the step Gorgias cannot: it checks what is free and prepares the booking inside the conversation. Straightforward requests are handled as they arrive, and the ones carrying a deposit or a whole-space hire are acknowledged instantly and held for a person to work properly.
Deposit-carrying and large-party enquiries, acknowledged and prepared for someone to finish.
And because everything is tracked per site, you get the numbers a booking widget never produced: how fast each venue replies, how many enquiries convert, and which site is quietly losing its Friday nights. Gorgias reports on tickets and the revenue its agents influence, which is a different question from how many Saturday bookings you won.
Response rate, volume and conversion per site, including the enquiries that never converted.
An honest note on where RevVue is today
RevVue's DesignMyNight integration is in active development. That is the honest status. For now, venues 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."
The wider category view is in shared inbox software for restaurants. Because party and private-hire enquiries are where the money is for a late-night venue, how to triage high-value group bookings is the most useful read next. To see what the AI would have said to a real enquiry your team received last week, book 20 minutes.
Frequently asked questions
Does Gorgias integrate with DesignMyNight?
No. Gorgias has no native integration with DesignMyNight, and no venue booking system appears in the Gorgias App Store. DesignMyNight is not on Zapier either, so there is no low-code bridge. Connecting them means a custom development project against Gorgias's API and the DesignMyNight API, and even then it only copies enquiry text into a ticket. It cannot check availability, hold an area, or take a deposit.
Can I connect Gorgias and DesignMyNight with Zapier?
No. Gorgias is on Zapier and publishes a developer API, but DesignMyNight is not on Zapier, so there is no zap to build. DesignMyNight and Collins connect outward through their own APIs to point-of-sale, payment and marketing systems rather than exposing a general automation connector, which leaves custom development as the only route.
Gorgias AI Agent can cancel an order, so why can't it hold an area?
Because its actions come from the systems Gorgias was built around. AI Agent performs real transactions such as order lookups, cancellations, address edits and subscription changes, because Gorgias is wired into Shopify and the e-commerce stack. A venue booking system is a different system of record, and Gorgias has no connection to one. The capability is real, the scope is e-commerce.
What do bars and late-night venues use instead for party enquiries?
Most run enquiries through a shared inbox even when a helpdesk covers customer service and the online shop, 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, with high-value party enquiries surfaced for a person to nurture. Its DesignMyNight integration is in active development, with an email-only pilot available now.
