
Santilotto is a terminal-based lottery platform built for agent-led betting operations. The system was designed to work in real-world environments where speed, clarity, and trust are non-negotiable β from busy POS counters to back-office operations managing money, people, and devices.
The product consists of two tightly connected experiences:
Agent POS App: used by agents at the point of sale to take bets, check results, and pay out winnings
Agent Admin App: used by operators to manage agents, terminals, funds, and system-wide financial activity
This case study documents how both sides were designed as one system, not two separate products, each optimised for the realities, constraints, and decision-making patterns of its users.
Visual and Product Designer
2025

Terminal Application
|
Product Design
|
Interaction Design
Before touching UI, I broke the platform into two mental models:
Execution β what agents need to do, quickly and repeatedly
Oversight β what admins need to monitor, control, and resolve
This separation shaped everything that followed.
Agents need confidence and speed.
Admins need clarity and accountability.
Both experiences had to feel intentional, not bloated.
Understanding the Agentβs Reality
Agents donβt βexploreβ apps β they execute tasks. Most interactions happen while:
Talking to players
Handling cash
Watching draw closing times
So the POS experience was designed to answer one question clearly on every screen:
βWhat do I need to do right now?β
Navigation Built Around Core Actions
The POS app was deliberately constrained to five nav items:
Home β wallet balance, top-up, recent activity
Bets β play games and view betting history
Results β draw outcomes and winning numbers
Payout β winning tickets and payout requests
Account β profile and system actions
Anything that didnβt directly support betting or payouts was removed or pushed deeper.
The Betting Flow
The betting experience was designed backwards from the bet slip β the most important artifact in the system.
Flow:
Select game (with closing & draw times visible early)
Select bet type
Pick numbers (1β90)
Input stake per line
Auto-calculate total stake
Confirm and generate bet slip (print or SMS)
Key decisions:
All calculations are system-driven to reduce human error
Timing is surfaced early to prevent late entries
Confirmation screens are short to avoid queue buildup
Results & Payouts β Clear Separation of States
Results and payouts were intentionally split:
Results focuses on transparency (what won, what didnβt)
Payout focuses on action (who gets paid, how, and when)
This separation prevents disputes and reduces cognitive load for agents handling winnings in front of players.
Admin Mental Model
Admin responsibilities naturally clustered into five areas:
Monitoring performance
Managing agents
Managing terminals
Tracking money
Securing the system
This directly informed the navigation and information hierarchy.
Dashboard as an Operations Overview
The dashboard isnβt just analytics β itβs an operational snapshot.
Key decisions:
Wallet balance appears before analytics, not after
Sales, commission, and payouts are always visible at a glance
Trends support decisions, not vanity metrics
Admins should immediately know:
βIs the system healthy right now?ββ¨β¨
Managing Agents & Terminals
Agents and terminals are treated as separate but connected entities.
Agents can be activated or deactivated independently
Terminals can be funded, disabled, or reviewed individually
Each terminal drills down into: Bets, Wins, Payouts
This structure allows admins to isolate issues without shutting down operations entirely.
Financial Transparency by Design
Money movement is where trust is won or lost.
To reduce ambiguity:
Transactions always show status, reference, and context
Payouts are clearly separated from general transactions
Filters are date-first, because most disputes are time-based
The goal was to ensure admins can always answer:
βWhere did this money come from, and where did it go?β
Empty States as Onboarding
Both apps include deliberate empty states β not as dead ends, but as guidance.
Examples:
No games available
No bets yet
No payouts processed
No agents or terminals added
Each empty state explains why itβs empty and what action unlocks progress, reducing the need for training or documentation.
Santilotto was designed as a single operational system with two perspectives:
Agents get speed, clarity, and confidence at the counter
Admins get visibility, control, and financial accountability
Every decision prioritised real-world use over abstraction β ensuring the platform feels dependable, not complicated.
The screens that follow walk through the final designs, showing how these principles translate into the actual interface across both apps.


The Home page serves as the operational overview. It surfaces the wallet balance upfront, followed by key actions such as wallet top-up and transaction history, alongside an activity summary that gives agents a quick sense of performance at a glance.



The Bets page is where active and past bets are managed. It allows agents to view all bets in one place, filter by date or ticket ID, and drill into individual bet details to review selections, stake, and status, or perform actions like printing or sending the bet slip.


The Results page provides a clear view of completed draws. Agents can see game outcomes at a glance, verify winning numbers, and reference draw times, helping them quickly confirm results and respond to customer queries with confidence.


The Admin Home gives admins a clear starting point for the day. By combining financial summaries with high-level activity signals, it allows them to stay in control of agents, terminals, and money flow at a glance.


The Agents page centralizes all agent activity and profiles. Admins can view, activate, or deactivate agents, monitor their performance, and quickly access financial or operational details tied to each agent.

The Agents page centralizes all agent activity and profiles. Admins can view, activate, or deactivate agents, monitor their performance, and quickly access financial or operational details tied to each agent.


