A service window is the on-screen menu built into a physical slot machine. It is how a player loads money, checks a balance, or reaches support, without leaving the machine they are sitting at.
Casinos traditionally ran on cash: players left the machine to visit an ATM that charged five to thirty dollars a transaction. The fix had to live on a small, fixed, regulated screen bolted to hardware I could not redesign — and that constraint shaped nearly every decision that follows.
In short — I owned research, UX, and interaction design for this redesign end to end — and lifted cashless usage 20% on hardware I couldn't touch.
The challenge was not building a payment button. It was redefining how money moves through a regulated, security-critical ecosystem, on hardware most digital designers never touch. Every decision below — the research, the testing, the interface itself — was shaped by the limits laid out here.
I led UX research, strategy, and design for the cashless funding flow on the service window — the primary player-facing screen covered in this case study. That work sat inside a larger cashless initiative at IGT, which also included a casino operations platform for floor staff and an internal support platform for technical teams; I contributed to both, and mention them briefly below for context, but the flows, testing, and outcomes described here are about the player-facing service window.
I worked alongside a junior UX designer and a development team of eight, across product, engineering, compliance, marketing research, casino partners, and internal support teams, to align UX decisions with business and technical constraints.
Players funded gameplay through on-property ATMs charging five to thirty dollars a transaction. That friction cost casinos revenue and cost players their sessions — and the fix had to fit inside the constraint above, not around it.
How the shift from cash friction to a cashless ecosystem actually unfolded, start to finish.
ATM fees and long lines delayed or discouraged funding. Many players left to find a cheaper machine, or ended sessions early — shorter play, less engagement.
Long ATM queues, floor congestion, and no visibility into player funding behavior translated directly into lost revenue and reduced retention.
Removing that friction reliably increased player spend. The opportunity was real — but only if the experience felt secure, intuitive, and trusted.
Because the hardware was fixed and every change went through a regulatory review cycle, there was little room to learn by iterating on-device. I partnered with IGT's marketing research team to analyze over a year of qualitative and quantitative data, synthesized into core player personas grounded in real behavior, not assumptions — the research had to do the work the constraint wouldn't let screens do.
One of the core player personas built from this research — internal shorthand name, kept here as evidence of the process rather than a polished deliverable.
The original focus group readout — the source data behind the stats above.
Using real player flows and direct quotes, I mapped the end-to-end journey across every system a single funding action touches: player experience, casino floor operations, technical support, and compliance reporting.
On hardware I couldn't patch overnight, a broken flow on the casino floor was a real cost to real players and real revenue — not a bug ticket. That raised the stakes of testing itself. I partnered with live casino properties to test cashless prototypes with real paying customers on the floor — account creation, machine pairing, wallet funding, cash-in and cash-out, error handling, and support flows. These early findings are what shaped the redesign priorities below.
Key insight: inconsistent casino connectivity affected transaction speed and pairing reliability — leading to parallel infrastructure work with casino IT teams, alongside the interface changes below. In parallel, I ran remote usability testing with internal support teams, redesigning workflows to reduce tool fragmentation and speed up incident resolution.
The original usability testing readout — the source data behind the stats above.
With no room to add screen real estate and no fast iteration cycle, every simplification had to earn its place. Based on research, journey mapping, and live testing, I focused on reducing cognitive load and building trust into the highest-risk transactional moments on the service window — within the same fixed screen the whole project was constrained to.
More iterations followed these; I no longer have access to those later files.
Casino players skew older and more varied in dexterity than a typical mobile app audience, and the service window is fixed at one height and angle on the machine, glanced at mid-game rather than studied. Both changed what "accessible" meant here.
Instant funding had to coexist with regulatory compliance. I prioritized clarity, confirmation, and trust over raw speed — financial safety without breaking a player's immersion in the game.
Funding directly from the machine — balance on card, credits to machine, confirm, play. No ATM, no card, no wait.
Cashless balance and account status stay visible without pulling the player out of the game.
Two of the biggest concerns from early research (account security, and not wanting another app) fed directly into these decisions:
The same cashless initiative also touched a casino-operations platform for floor staff and an internal support platform for technical teams — both out of scope for this case study, briefly: simplified compliance monitoring on the floor side, and a shared cross-system record that cut resolution time on the support side.
Simplifying the highest-risk transactional flow — and building trust into every step — turned a feature players were reluctant to try into IGT's most successful on-demand product for this hardware category.
Measured by comparing service window drop-off and cashless usage rates from 2019–2020 against usage in late 2021, after the redesign had been live across casino properties.
“A recurring principle from this project was giving the interface room to breathe — cutting complexity and click counts until the player's next action was obvious. On hardware with no room for a wasted tap, that restraint mattered more than any single feature.”