GSA Results

What GSA did for the bays it looks after

Every 10 days we add up the last 30 days across every bay running GSA: the sessions it opened, the resets it ran between players and the problems it fixed before anyone had to step in. Figures are rounded and pooled across venues, so no venue or bay can be picked out.

Every day

Bays opened and run, every single day

Each bar is one day across every bay GSA looks after. Before each session the system starts the stack in the right order, checks the launch monitor is reading, and only then opens the bay to the player.

Bar height shows how busy each day was compared with the busiest day. No counts are shown.

Fixed on its own

Most problems were sorted before anyone was called

GSA watches the game, the launch monitor and the screens for the whole session. When something stops, it repairs it on the spot and checks the repair worked.

Sorted with no one touching the bay

Out of every genuine problem, including the ones that did need a person, were fixed by the system alone.

What it fixed most often

Bar length compares each kind of problem with the most common one.

    How fast

    of automatic repairs were done inside five minutes

    The typical repair took a moment, measured from the moment GSA noticed the problem to the moment the bay was confirmed working again.

      Share of automatic repairs by how long they took, from first noticed to confirmed working.

      How it works

      A player says the ball is not reading. This is what happens next.

      GSA tries the gentlest fix first, checks the ball after each attempt, and stops the moment it reads again. The player stays on the mat.

      1. Spots the problem

        From the player’s report or the bay’s own health checks, often before anyone says a word.

      2. Works out the cause

        Reads what the bay is reporting to pick the right fix, not just the biggest one.

      3. Fixes it

        Starts with the lightest fix that could work, so the round can carry on.

      4. Checks it worked

        Confirms the ball is reading again. If it is not, it moves on to a stronger fix.

      5. Calls a person

        Only if the bay still is not right. Staff get the full history of what was already tried.

      of “ball not reading” reports in the last 30 days were sorted this way, without staff.

      Every booking

      The same routine, booking after booking

      Between one player and the next, GSA resets the bay so the next group walks in to a clean, working screen. Nobody has to go round the bays checking them.

      When a person is needed

      Some things need a person. GSA gets them there faster.

      Outages spotted and reported

      Power cuts, dropped networks and bays switched off, flagged straight away instead of discovered by the next player.

      Remote sessions

      Times a bay was checked or fixed from somewhere else, by venue staff or our team, without anyone driving in.

      Help requests triaged by AI first

      GSA Guardian Assist reads every request for help, checks the bay and suggests the next step before a person picks it up.

      Want these results in your bays?

      See GSA running on a live bay, and we will walk you through what it would do in yours.