Case study · Booking & operational software

Bedazzle Box Office

A bespoke event system that connects the public booking journey with the practical work behind it: event publishing, bookings, payments, ticket delivery, administration and mobile check-in.

Bedazzle Arts Bespoke operational system Booking & payments Mobile check-in
Bedazzle Box Office public events page showing an upcoming event and booking information
The public Box Office brings event information, ticket availability and the booking journey into one clear place.
The problem

One event journey instead of several disconnected tools

Bedazzle needed more than a page with a payment button. Events have to be published, customers need clear booking information, bookings need to be recorded correctly and staff need practical information before and during the performance.

Atinamos built the Box Office around that complete workflow so the public website, booking records, payment state, ticketing and venue entry all belong to the same system.

What was built

A connected system from event publishing to entry

Public events & bookings

Event listings, individual event information, ticket availability and a booking journey designed around the information customers actually need.

Payments & confirmation

Paid bookings can use hosted SumUp checkout while free or complimentary bookings follow the appropriate no-payment route. Payment and booking states remain separate but connected.

Event administration

Staff can create and update events, manage booking status, review operational information and keep the public event record aligned with what is actually happening.

Tickets & venue entry

Confirmed bookings can issue individual ticket information for use at the venue, with mobile tools for attendee lookup and QR-based check-in.

Operational use

From the office to the venue door

The operational dashboard gives staff a clear view of event and booking activity, while the check-in interface is deliberately designed for a phone so it can be used where the work actually happens.

State design

Built around real operational states

The important work is not the appearance of a booking form. It is making sure the system knows the difference between an event that is coming soon, on sale or closed; a booking that is paid, complimentary or cancelled; and a ticket that is valid, already used or belongs to a different event.

Those states give staff something dependable to work with and allow the customer-facing side of the Box Office to stay in step with the operational reality behind it.

What it demonstrates

Public experience and operational software in one project

Workflow design

Turning an event journey into one connected process rather than stitching together unrelated tools.

Payment integration

Using an established hosted payment provider while keeping booking logic and confirmation inside the operational system.

Admin software

Building practical interfaces for event management, booking oversight and operational status rather than only the public website.

Mobile operational tools

Designing the check-in workflow around staff using a phone at the venue, not around a desktop admin screen.

The result

A box office that follows the event all the way through

The result is a system that can support the journey from publishing an event to managing bookings and admitting attendees. Because it is built around Bedazzle's own workflow, it can continue to evolve as the organisation's event requirements change.

Need bookings, payments and admin to work together?

Tell us what customers need to do and what your team has to manage afterwards. We can look at the whole journey rather than treating each screen as a separate problem.

Discuss the workflow