A day in the life of our ticket system administrator

The ticket system administrator’s day begins with an inbox, not a stage. Overnight sales reports arrive beside requests from box-office staff, teachers at ATEB and artists changing arrival times. The administrator turns that stream into a short list: what needs attention before doors open, what can wait, and what requires a conversation with the venue team.

Figueres a Escena’s programme crosses theatre, music, dance, cinema, opera, circus and family events, so no two evenings look alike on the system. A concert at Teatre El Jardí may need different ticket types from a school workshop at Sala La Cate, while an ATEB course can create sales and attendance records across an entirely different calendar.

Much of the work is invisible to audiences but visible in their experience. Prices must be right, seats must be protected, access arrangements need to reach the right staff, and a changed performance time should not trigger a queue at the door. The administrator connects those tasks to people rather than treating technology as a separate concern.

For an Australian audience, that reliability is familiar from busy cultural precincts in Sydney, Melbourne and Brisbane, where audiences often move between work, school runs and public transport while choosing how to spend an evening. Our administrator’s role is to make the digital process feel ordinary: a clear event, a secure booking, a useful confirmation and a smooth arrival.

The morning inbox

The morning inbox is sorted by audience impact. A broken checkout link or incorrect seat map comes first; a request for a receipt can wait; a question about a rehearsal-room booking may need routing to a programmer rather than technical support. The administrator checks messages in several languages because Figueres welcomes international visitors and touring teams, while keeping internal notes concise enough for busy venue staff.

Next comes the shape of the day. The calendar shows sales deadlines, delivery of promotional ticket allocations, accessibility bookings and production meetings. It also includes less visible deadlines, such as when temporary holds expire or when a workshop reaches its attendance limit. Each entry is checked against the correct venue, with one shared system covering performances, classes and community activity.

A healthy system starts early

The morning’s technical check includes a close look at the Volvox STNK configuration for each event. The administrator confirms that ticket categories, taxes, availability windows and access links are behaving as expected. An event may look correct on the public page while a special price, member allocation or booking fee remains wrong behind the scenes.

Payments, confirmations and scanner data are tested before the first ticket is sold through the day. The administrator also checks that staff accounts have the permissions they need without exposing sensitive information to the whole team. This routine is quick when everything is in order, but it prevents small inconsistencies from becoming long queues later.

Designing for real audiences

From an Australian perspective, booking habits are increasingly mobile and linked to public transport. A visitor in Sydney may tap an Opal card while travelling to a performance, a Melbourne theatre-goer may rely on trams and Myki, and a Brisbane family may plan around a Go Card and school pickup. Digital wallets, QR confirmations and quick decisions on a phone are normal expectations, so event information must load clearly on a small screen.

The wider Australian market also shapes how tickets are presented. Independent theatres, festivals and community companies compete with major platforms, while memberships, concession rules and transparent booking fees influence trust. Our administrator checks that each price, age category and fee matches what was published, and that families or groups can understand the options before paying.

The box office before doors

By late morning, the first real test arrives with ticket buyers. Some customers want the best available seats for a family, while others have a single concession ticket or a booking that needs transferring between names. The administrator works with venue colleagues to place holds correctly, release blocked inventory and make sure printed and digital tickets contain matching information.

When something goes wrong, calm communication matters. A duplicate purchase, expired confirmation or incorrect performance date is resolved through the same channel that sold the ticket, rather than sending the customer to another department. Clear instructions also help box-office staff explain the solution without making the visitor feel responsible for the system’s failure.

Midday checks and useful numbers

Reports turn the morning’s activity into useful information. The administrator compares ticket sales against capacity, tracks which sessions are filling and checks whether online sales align with payments received at the box office. This can reveal a weak checkout device, misleading event information or an allocation that needs adjustment before too many customers encounter it.

Data access is handled just as carefully. When information relates to people in Australia, the administrator checks whether the Australian Privacy Act 1988 and its privacy principles apply to that activity, while retaining the GDPR duties that govern our operations in Spain. Access to customer records is limited, and account details needed for a sale are not retained simply because they might be useful later.

Before campaigns go out, consent and customer communication receive another review. Communications aimed at Australian visitors are checked against the Spam Act 2003, including sender identification and a working unsubscribe route. Published ticket conditions also support obligations under the Australian Consumer Law by making fees, refund terms and restrictions easy to understand before purchase.

Preparing for tonight’s stage

Mid-afternoon, each event has a different profile. A theatre performance needs scanners tested, seat maps verified and box-office stock organised for collection. A cinema session depends on timed admission, while a workshop may require a register, age bands and space for children. Talks, rehearsals and community activities bring their own access details and arrival arrangements.

Schools, visiting artists and community organisers can send practical requests through the contact the venue page, and the administrator helps route each request to the appropriate team. Once the doors approach, attention shifts from configuration to coordination: staff know which doors to open, which tickets require special handling and where an audience member should be directed if the usual plan changes.

Closing the loop

After the audience leaves, sales, payments, refunds and scanned entries are reconciled. A missing scan may indicate a technical fault rather than an absent guest, while an unusual refund pattern can expose a confusing condition in the booking flow. The administrator records what happened so the same question does not have to be investigated from scratch the following morning.

The final task is preparation. Notes go into the shared system, access credentials are checked and any configuration change is backed up before it becomes permanent. The next morning may bring a new production, another busy class at ATEB or an entirely different kind of event, but the aim remains the same: accurate information, responsive colleagues and a ticket journey that stays out of the audience’s way.


Figueres a Escena’s programme brings international touring work, local performers, cinema, music and family events into two welcoming rooms, with ATEB workshops adding another way to take part. The next evening begins on the event listings page, where you can compare dates, sessions and ticket options before choosing what suits your group.

Book with confidence, arrive a little early and leave the ticketing details to the team. A good performance should begin before the curtain, with every seat, booking and arrival working quietly in the background.