→ Back

Cerberus: Black Rush

Entain — Dec 2025 to Apr 2026

Cerberus home screen with links to each brand

My role

UX Designer

Client

Entain

Timeline

Dec 2025 – Apr 2026

Platform

Internal web admin

Tools

Figma, React

Overview

A new screen in Entain's internal admin tool that shows support agents what happened in a customer's casino session.

The problem. Agents could see a customer's sports bets and payments, but not what they did on Black Rush, Entain's online casino.

What I did. As the only designer, I designed the Game Activity screen and six supporting screens in about four weeks, reusing existing patterns.

The outcome. One screen shows play grouped into sessions, each payout split by type of money, and filters for casino, poker and bingo. Agents no longer need developers to look things up.

01

Problem & goal

Agents couldn't see casino activity.

A blind spot for support teams

Cerberus is the internal tool Entain's support, trading and risk teams use to manage customers across Ladbrokes, Neds, TAB NZ and Betcha. When Black Rush, Entain's online casino and bingo product, joined, agents couldn't see what customers did while playing.

Problem 01

Activity wasn't grouped

Every spin and hand appeared in one long list, with no link to a game or session.

Problem 02

Payouts didn't show their source

A payout can mix cash, bonus cash and free spins. Only the total was shown, so agents had to ask developers.

Problem 03

Casino, poker and bingo looked the same

Everything was labelled "Casino", so agents had to read game names to tell them apart.

Goal: one place for agents to see what happened in a casino session, organised, easy to filter, and showing each type of money used.

This was part of a larger rollout that also included VIP settings and casino risk review (see Other designs below). This case study focuses on Game Activity, the most complex screen.

02

The challenge

Why it wasn't a simple copy of existing screens.

Three problems to solve

Reusing the existing layout saved time, but three design problems still needed solving.

Challenge 01

What counts as a "session"?

Slots are played spin by spin. Blackjack can last hours at one table. We had to define a session before grouping anything.

Challenge 02

Where should casino activity go?

Deposits and withdrawals work differently from casino play and have different data, so casino got its own section.

Challenge 03

Keep agents fast

Agents work quickly using keyboard shortcuts. Spacious layouts would have slowed them down, so the screen stays compact.

03

Role & team

Only designer, many stakeholders.

Keeping everyone aligned

I was the only product designer on the project, planned for three to four weeks.

  • Open questions were tracked on a shared board, not in private messages
  • Before the program lead's two-week leave, I ran a review with the product manager and technical expert to keep key work moving
SM
Shakeel MastersProduct design (solo)
A
AdamProduct manager
TL
Thomas LillEngineering / technical expert
A
ArthurCasino product stakeholder
NC
Nathan ChowDelivery / program lead
S
ShuhanDesign system expert
04

Game Activity

Game Activity: the main screen.

Shaped by feedback

This screen had the most feedback rounds, with the product manager, the technical expert and a casino stakeholder. Three decisions shaped it.

Decision 01

Getting the columns right

The first version showed date, game, amount bet and amount won. Feedback added total stake, total win, multiplier and game provider, plus a Game Class field to filter casino, poker and bingo.

Game Activity table with the final columnsClick to enlarge
Decision 02

Defining a "session"

A session is one game played continuously until the customer takes a break. The same rule works for a three-hour blackjack session and a five-minute slots session.

Game Activity with a session expandedClick to enlarge
Decision 03

A dedicated section, with clear payouts

Casino activity has its own section instead of sharing the transactions list. A detail panel splits each payout into cash, bonus cash and free spins.

Game Activity with the transaction detail panel showing fund breakdownClick to enlarge
05

Other designs

Other screens I designed.

Six supporting screens

Six more screens, each solving a day-to-day or regulatory problem found during research.

VIP and loyalty configuration
VIP & loyalty Ranks, rewards and multipliers, editable without asking a developer
Confirm before saving dialog
Confirm before saving Manual loyalty changes need a reason and a plain-English check
Casino risk queue
Casino risk queue Flagged transactions with a New → In progress → Escalated flow
Customer dashboard
Customer dashboard Loyalty status, account manager and audit trail
Cerberus home
Cerberus home The shared entry point across every Entain brand
Edit rank configuration
Edit rank Adjusting one VIP tier's points and reward value
06

Outcome

The outcome.

Time spent on what was new

Existing layouts, tables and pop-ups were reused, so design time went into what was new: sessions, payout breakdowns and casino filters.

1screen for session activity and fund breakdown, grouped by game
0guessing: a Game Class field filters casino, poker and bingo
3fund types (cash, bonus cash, free spins) in one payout view

Agents can now open one screen and see what a customer staked, what they won, and where the money came from.

07

Reflections

What I learned.

Plan for unusual cases early

The blackjack question came up after the first designs. Next time I'll involve the risk and trading teams before sketching.

Design for reuse

Keeping the VIP screens free of brand names cost little and means other products can reuse them.

Clear scope makes speed possible

Four weeks worked because we were strict about what was new, and focused design time there.