Booking inside your own website
Visitors book on your page, in your colours, and are never sent to a ticketing site.
Two lines of code on any page of your site. The booking flow sizes itself to fit and takes your brand colours.
Roadmap
TicketHero is new, and we build it alongside a small number of venues. This is the whole picture, with every item marked as live, in build, planned or under consideration.
Everything here runs in the product now. You can book through it in the live demo and see the staff side in a private preview.
TicketHero is new and runs on demonstration data. Payments in the demo are simulated: no card is taken and no money moves.
Visitors book on your page, in your colours, and are never sent to a ticketing site.
Two lines of code on any page of your site. The booking flow sizes itself to fit and takes your brand colours.
People see which days are free, and the price for each day, before they choose tickets.
Start times show as free or full and update the moment one is taken. We show availability, never a count of the places left.
A place is held while someone pays, so the same start time is never sold twice.
If they leave without paying, the place goes back on sale by itself after ten minutes.
Every ticket carries a code. Scan it with a phone or type the reference to check the party in.
Staff see who is arriving, what they bought and each child's details before the family reaches the front of the queue.
Open up more places on a busy date in seconds. Your booking page updates as you save.
One grid shows every date and start time, with confirmed bookings against the places released for sale.
The booking fee is in the total from the start, in line with UK pricing rules.
Prices can differ by date, so a peak Saturday and a quiet weekday are priced separately and shown on the calendar.
Families add each child's name, age and interests afterwards, from a private link they can return to.
Nothing extra stands between the visitor and the booking. Staff can see which families have still to fill theirs in.
Read your experiences, availability and bookings from your own systems.
You create and revoke the keys yourself in the admin, as read only or read and write. Each key reaches one venue's data.
Create, change, cancel and refund bookings, and set capacity, from your own systems.
A booking made through the API takes a place exactly as a website booking does. Refunds are recorded for now; when card payments arrive they will return the money as well.
A name and an email address are all it takes. Nobody has to create an account.
Marketing consent is asked for separately and is never ticked in advance.
Offer add-ons with the ticket, chosen by quantity or added once for the whole party.
Each extra takes one tap, joins the running total straight away and shows for staff at the gate.
Set the largest party, require a child ticket on a family experience and cap one experience within a shared start time.
The same rules run in the booking flow and in the database, so the price a visitor sees is the price they are charged.
The campaign, the referring site and the landing page are saved on the booking itself.
Because the booking happens on your own site, nothing is lost in a hand-off to another domain. Staff see the source beside every booking.
Bookings and sales so far, who is arriving today and how many have checked in.
It also shows the places being paid for right now and the families who have still to send their children's details.
Search by reference, name, email address or date.
Each row shows the experience, the visit, the party, where the booking came from and the total paid.
Your systems are told the moment a booking is confirmed, changed, cancelled, refunded or checked in.
Every message is signed so you can prove it came from us. Each one is sent once today; automatic retries are planned.
Nothing in this part of the venue at this stage.
The pieces we are working on at the moment. They are what turns the demo into a system a venue can take real bookings on.
Paid straight to your own Stripe account, so the money and the customer stay yours.
You are the merchant and we never hold card details. Until this is switched on, the demo uses a stand-in payment and takes no card.
Each booking is confirmed by email, with the ticket and the link for adding details.
Today the ticket appears on screen at the end of the booking and stays on its own private page.
Pitches booked by the night, in the same system as your tickets.
A start time and a pitch night are the same thing underneath: a space with a capacity in a time window. One admin covers both.
Nothing in this part of the venue at this stage.
Planned and understood, and not started yet. The order is agreed with the venues we work with, so it can change.
Customers move their own date or ask for a refund from their booking link, within rules you set.
Fewer emails to your team, and the freed place goes straight back on sale.
People leave an email address for a full start time and hear if a place opens.
It also tells you which dates are in demand before you decide where to release more places.
Everyone signs in as themselves, in place of the single shared staff password used today.
It lets you see who checked a party in or changed a date, and remove access when someone leaves.
Codes for offers, partners and campaigns, with the limits you choose.
Limit a code by date, by experience or by the number of times it can be used.
Sales by date, by experience and by campaign in one place, without a spreadsheet.
The source is already saved on every booking. This turns it into a view you can act on.
If your system is briefly unavailable, the message is sent again rather than lost.
Messages are sent once today, with the result of the latest one shown in the admin.
Nothing in this part of the venue at this stage.
Things a venue group like yours has asked about or is likely to need. We have not committed to any of them. Tell us which would matter to you.
Enquiries, viewings and quotes tracked beside your ticket sales, in the same system.
For venues that sell tickets and host weddings or private hire, and want one place to see both.
One booking for a large party, with final numbers confirmed nearer the day.
For schools, clubs and coach parties that do not fit a family-sized booking.
Vouchers sold on your website and redeemed in the same booking flow.
Bought as a gift, then spent against any date and experience you allow.
Regular visitors book their place with a pass and no payment step.
For sites that people return to through the year, such as a country park or a campsite.
Sell at the gate from the same availability as your website, so the two never clash.
A place sold in person would come out of the same start time as a place sold online.
Sales and fees in a format your accounts package can import.
Split by experience and by date of visit, so income lands in the right period.
With the venues we work with, in the order that suits their season. Large platforms decide once for thousands of venues. We decide with a handful.
We work with a small number of venues, so this list is set by what they need to run their days. You talk to the person who builds the product, and what you ask for is weighed against a short list, not a long queue.
A campsite needs its bookings ready before the summer. A Christmas event needs everything settled before tickets go on sale. We agree the order with you and work back from the days that matter most.
Nothing moves to working today until it runs in the product and you can try it. Where something is a stand-in, such as payment in the demo, we say so on this page.
You will not find dates on this page. Timings are agreed venue by venue, and anything further out can change as we learn what you need.
Tell us how you sell today and what gets in your way. If it is missing from this page, that is the conversation we want to have.
We reply by email, usually within one working day.