No. Gorgias has no native, purpose-built integration with Collins, and Collins is not on Zapier, so there is no low-code bridge to attempt. Gorgias is a helpdesk built for e-commerce, wired deeply into Shopify. Collins is the venue-management and booking software behind DesignMyNight, used by bars, late-night venues, competitive-socialising sites and events-led operators to run large-party enquiries, deposits, pre-orders and area bookings. Those are the highest-value enquiries a venue gets, and Gorgias cannot touch one of them.
The short answer
Gorgias can receive a Collins enquiry as a ticket. It cannot do anything with it in Collins. Holding an area, building a package, taking a deposit, attaching a pre-order: all of that still happens by hand, in Collins, by a person.
Gorgias + Collins | |
|---|---|
Native integration | None |
Best available workaround | A custom build on Gorgias's API and the Collins API |
What the workaround still can't do | Check space availability, hold an area, build or quote a package, take a deposit, attach a pre-order |
The asymmetry in this pairing is stark. Gorgias can take a payment-related action on a Shopify order without a human touching it. It cannot tell you whether a room is free on a Thursday in December.
What actually happens to a booking enquiry
Events teams feel this most, because a private-hire thread runs for weeks and often arrives tangled up with something you sold online.
A company emails in November. They bought 20 gift cards from your online shop last week as staff prizes, one has not arrived, and while they are writing they ask about hiring the mezzanine for a party of 40 in January, with a drinks package and payment by invoice. The message becomes a Gorgias ticket.
Gorgias handles the gift-card half well. The order sits alongside the message because it lives in Shopify, and AI Agent can look it up, see which card failed to deliver and reissue or refund it without a human.
The private-hire half waits for a person. An agent opens Collins in another tab, because Gorgias cannot see the space diary.
They check which January Thursdays still have the mezzanine, what minimum spend applies, which packages work for 40, what deposit is required and when the pre-order deadline falls.
They pencil a provisional hold into Collins, re-keying the date, headcount, space, package and the invoicing requirement from the email.
They switch back to Gorgias and write the reply covering both halves.
They set the ticket pending, because corporate bookings need sign-off.
Two weeks later: "Approved, but it is 55 now and the date has moved a week." The mezzanine may not take 55, the minimum spend changes, and the hold has probably lapsed. 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 sit side by side in the same ticket, and the contrast is the point: Gorgias resolved a real commercial problem autonomously and then had nothing to offer on the booking worth several thousand pounds. 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. A company party is worth thousands, the organiser has emailed four venues, and December and January enquiries arrive in a flood. 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 Collins and you will find nothing.
The workaround is thin. Gorgias is on Zapier and publishes a developer API, but Collins is not on Zapier, so there is no zap to build. Collins connects outward through its own API 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 Collins API. It is a real engineering budget for a venue group, and what it buys is a pipe that copies enquiry text into a ticket, one direction, treating a private-hire negotiation as a support case. AI Agent will not fill the gap, because its action library comes from your connected e-commerce systems. It can reissue the missing gift card and cannot hold the mezzanine.
One honest credit worth giving. If your group sells gift cards, vouchers or merchandise online, and events-led venues usually do, 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 private-hire enquiry is only resolved when the space is held, the package is agreed and the deposit has landed. That difference is the whole problem.
Gorgias proves the point rather than escaping it. It shows exactly 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 function diary are the same surface, so a private-hire question does not become a week of forwarded email. 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 whose sites each hold several private rooms. The team stops opening messages just to work out which building is being asked about, and works from one queue, by location, rather than a helpdesk organised around a shop instead of a diary.
One queue per venue, so an enquiry about a private room reaches the people who run it.
The AI drafts the reply in the venue's voice, using its own capacities, its minimum spends and what each room can seat. Event enquiries are the longest threads a venue handles, and starting from a drafted answer removes most of the typing.
A drafted reply carrying the venue's own capacities and terms, ready to approve.
Because it connects to the booking system, the AI takes the step Gorgias cannot: it checks the space against the date and prepares the booking in the thread. Simple date questions are answered on arrival, and the enquiries worth thousands are acknowledged within moments and held in a queue a person works through.
The large-event enquiries held, prepared and visible, instead of buried in a shared inbox.
And because every enquiry belongs to a venue, private hire finally has a funnel. Enquiry volume, reply speed and conversion by site: the reporting a function diary cannot produce, because it only ever sees the events that were confirmed. Gorgias reports on tickets and the revenue its agents influence, none of which tells you how much function revenue the inbox lost.
Enquiries, response times and conversion by location, including the ones that never got booked.
An honest note on where RevVue is today
RevVue's Collins integration is on the roadmap, and the honest position today is an email-only pilot. That pilot 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 private-hire and large-party enquiries are the highest-value threads a venue handles, 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 Collins?
No. Gorgias has no native integration with Collins, and no venue booking system appears in the Gorgias App Store. Collins 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 Collins API, and even then it only copies enquiry text into a ticket. It cannot hold a space, build a package, or take a deposit in Collins.
Can I connect Gorgias and Collins with Zapier?
No. Gorgias is on Zapier and publishes a developer API, but Collins is not on Zapier, so there is no zap to build. Collins connects outward through its own API 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 process an order, so why can't it hold a space?
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 events and private-hire venues use instead?
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 private-hire enquiries surfaced for a person to nurture. Its Collins integration is on the roadmap, with an email-only pilot available now.
