Bookings.
Tickets.
Sorted.

Booking and event ticketing systems for Cornwall businesses.

From choosing a session to finding a ticket at the gate, every step matters. I connect websites, booking tools and ticketing so customers can complete the purchase and your team can manage what happens next.

[ 01 / IS THIS FOR YOU? ]

Less chasing. A clearer way to book.

  • Customers have to message you to check availability or reserve a place.
  • Ticket sales, confirmation emails and check-in create separate admin jobs.
  • You are launching an event or activity and need the buying journey ready.

[ 02 / THE WORK ]

What is involved.

01

Map the customer journey.

We work through ticket types or session choices, capacity, the information customers need and how they pay. A clear mobile journey matters as much as the booking tool behind it.

02

Choose and connect the tools.

The scope may include booking software, payments, confirmations and digital tickets. We check platform fees, payment-provider charges and any limitations before choosing a setup.

03

Think beyond the checkout.

We agree how your team will view bookings, manage changes and run check-in where needed. Test bookings and key customer emails help us check the flow before launch.

[ 03 / SELECTED WORK ]

See it in practice.

WAX Events website project

WAX Events

From announcement to ticket to check-in.

Reusable event pages, ticket sales, customer emails and check-in were brought together in one WordPress setup.

Read the WAX Events case study
WAX Burner OCR mobile website screenshotWAX Burner OCR mobile website screenshotWAX Burner OCR mobile website screenshot

WAX Burner OCR

Help people choose the right entry.

Race information and ticket choices were organised into a clear journey, connecting entry buttons to ticketing and campaign tools.

Read the WAX Burner OCR case study

For activity bookings, see how locations, session choices and the route to booking were brought together for Crazy Football Golf. Explore the case study.

[ 04 / WORKING TOGETHER ]

One person.
A clear plan.

You work directly with me, from the first conversation through to the work itself.

  1. Start with the rough version.

    Tell me what you need, what is getting in the way and any deadline or budget you have in mind.

  2. Agree the scope.

    We work through the requirements, responsibilities and costs. You can see what is included before deciding to go ahead.

  3. Build, review and hand over.

    We agree review points and check the important journeys. Handover and any ongoing support form part of the plan.

[ 05 / BEFORE YOU ENQUIRE ]

The practical
questions.

Do you build a new booking system every time?

No. An established platform may already do the job well. We start with what your business needs, then decide whether to integrate an existing tool, configure WordPress or scope something more tailored.

What are the ongoing fees?

These depend on the chosen platform and payment provider. Hosting, software licences, transaction fees and support are separate considerations. We identify them during scoping so you can compare the total running cost.

Can it handle refunds, cancellations and capacity?

Those requirements need to be agreed before choosing the tools. Tell me your rules for availability, refunds, transfers and cancellations; we will check what the proposed platform supports and what needs extra work.

Can I keep my current ticketing provider?

Potentially. Send the provider name and the parts of the journey you want to improve. We will check its available integrations and whether it can support the experience you need.

What do you need to quote?

A description of the event or activity, ticket or session types, expected volumes, current tools and the launch date. If some of that is undecided, we can work through it together.

[ LET’S TALK ]

Discuss my booking setup.

Tell me what people will book, how you manage it today and when it needs to launch. I will work through the customer journey and tool options with you before we agree the build.

Just exploring? That is a useful place to start, too.

Prefer email? projects@jordanhammond.co.uk

Your details are used to respond to your enquiry. Privacy notice.