Your Cart ()

Subtotal £
Checkout
Back to Latest

If your ticketing doesn’t fit, build the journey around the visitor

an illustration of someone riding a ticket

Most ticketing systems are designed around a sensible assumption. Most events work in broadly the same way. You choose a performance, pick your tickets and pay. For plenty of venues, the standard process does exactly what it should. It’s when somebody needs to make a choice the booking journey hasn’t accounted for that things get interesting.

Where Spektrix booking problems show up

Say a visitor has picked a Saturday and found four seats together. They want to add a workshop, but the only way to see if the times work is to go back and start again. Everything might be working as configured. It just isn’t helping the visitor make the decision they came to make.

Other problems are more literal. A performance is on sale at the box office but doesn’t show online, a ticket type goes missing, or the basket is empty at checkout. Spektrix’s troubleshooting guide covers these symptoms. An empty basket can point to the booking subdomain. If sign-in is the sticking point and you’re using the older checkout, Express Checkout lets new customers book without setting a password. Neither is a reason on its own to rebuild the whole journey.

It’s worth looking at what people can find out before they book, too. Can somebody tell which performances are captioned, or how to book a wheelchair space and a companion seat? In Indigo’s Access Culture 2025 research, 17% of disabled respondents found booking cultural events online fairly or very difficult, compared with 2% of non-disabled respondents. That’s a finding about cultural booking generally, not Spektrix specifically.

When customers start asking for your website

Say a visitor has picked a Saturday and found four seats together. They want to add a workshop, but the only way to see if the times work is to go back and start again. Everything might be working as configured. It just isn’t helping the visitor make the decision they came to make.

Other problems are more literal. A performance is on sale at the box office but doesn’t show online, a ticket type goes missing, or the basket is empty at checkout. Spektrix’s troubleshooting guide covers these symptoms. An empty basket can point to the booking subdomain. If sign-in is the sticking point and you’re using the older checkout, Express Checkout lets new customers book without setting a password. Neither is a reason on its own to rebuild the whole journey.

It’s worth looking at what people can find out before they book, too. Can somebody tell which performances are captioned, or how to book a wheelchair space and a companion seat? In Indigo’s Access Culture 2025 research, 17% of disabled respondents found booking cultural events online fairly or very difficult, compared with 2% of non-disabled respondents. That’s a finding about cultural booking generally, not Spektrix specifically.

digital mockup featuring 878 AD branding
a homepage render on a laptop of the historic winchester website

The event that didn’t fit

We worked on a Christmas event with two ticket options. You could book the experience on its own or book it with a visit to Santa’s grotto. On paper, that sounds simple. In practice, there were two related booking journeys, and we wanted visitors who’d chosen the experience on its own to see the grotto option while they were still planning their visit. When you’re selling a Christmas experience, booking is the first part of it. The standard Spektrix setup wasn’t a good fit for how the two options needed to work together. Rather than bend the event to fit the system, we built the booking journey around the event.

It’s tempting to start with what the platform can do. We find it more useful to start with what the visitor needs to do. Before we designed or built anything, we mapped both ticket journeys and worked through them with the client. Agreeing where people should make each choice gave us something concrete to design, review and refine together.

A christmassy mock up with a phone a website booking journey
A red background a digital booking journey featuring a calendar and time selection
a christmas themed laptop mock up featuring the Christmas at milestones website

Building right up to checkout

With the flow agreed, we used the Spektrix API to build the steps leading up to checkout. We designed how visitors chose a date and time, selected tickets and reviewed their basket. That gave us control over what each step asked of the visitor and how it led to the next. Spektrix still handled the underlying ticketing, and payment stayed with the Spektrix checkout. If Spektrix works well for your box office, you can improve what visitors see without asking the team to change systems.

Visitors choosing the experience on its own were offered the chance to add Santa’s grotto before they continued. They could consider it while they were deciding what to book, rather than finding it as an afterthought at the end. Done badly, upselling feels pushy. Done well, it’s closer to somebody at the box office asking whether you’d like to see Santa while you’re there. It’s a useful question at the point you’re planning the visit. It’s less useful once you’ve got your card out.

We also approached the site knowing that not everyone arrives ready to browse. Some people already know what they want and just need the shortest route to booking. We added a booking widget to key pages for those visitors, so they didn’t have to work through the event information to find their way in. Combined with a site of its own to let us build the content, design and booking journey around one event. For another event, the same changes could sit within an existing venue website.

When bespoke is the right answer

If the standard process does the job, use it. If you’re not sure where the problem is, start with the questions your box office keeps answering. Try one of those bookings on a phone. If you’re having to go backwards or piece together information across several pages, look at the order you’re asking people to make decisions in. If your event doesn’t quite fit your ticketing system, tell us where visitors are getting stuck. We can help you work out what’s worth changing, from a fix to your existing set-up to a bespoke Spektrix website integration.

Got an event that doesn’t fit the standard?

Tell us what you’re offering and how you’d like people to book it. We’ll help you build a journey that guides them from first click to checkout.