Set Responsible Betting Limits
Design account controls that let an adult set spending and time limits, review activity, and activate a protected break from betting.
The brief
Understand the problem
Background
Regulated betting services need controls that help customers understand spending and step away. These controls lose value when they are hidden, easy to reverse, or surrounded by promotional pressure.
User context
Jon is an adult customer who has spent more than intended during recent sports seasons. He wants a weekly deposit cap and a three-month break that cannot be casually undone.
Product problem
Limit settings involve money, identity checks, time delays, and emotionally charged decisions. The product must support informed action without using streaks, urgency, or rewards to encourage more betting.
Objective
Create the responsible-play area for reviewing activity, setting limits, and starting a self-exclusion period.
What to design
Define the experience
Required experience
- Plain-language activity and net spending summary
- Deposit, loss, and session limit controls
- Cooling-off and self-exclusion confirmation
- Protected status with support resources
Screens and states
- Activity overview
- Limit settings
- Exclusion review
- Protected account state
- Limit change notice
Core user flow
Follow the critical path
- 01
Jon reviews deposits, withdrawals, and net spending over time
- 02
He sets a weekly deposit limit
- 03
He selects a three-month self-exclusion period
- 04
He reviews the consequences and confirms after identity verification
- 05
The account enters a protected state with support and withdrawal access
Product rules
Requirements and constraints
Requirements
- Use neutral language and avoid promotional content throughout the flow
- Show net position rather than only wins or account balance
- Explain when a stricter or looser limit takes effect
- Make self-exclusion duration and consequences explicit
- Allow access to withdrawals and required account records during exclusion
- Provide region-appropriate independent support resources
Constraints
- Local regulation determines available limits and exclusion periods
- Increasing a limit may require a mandatory delay
- The user may hold linked accounts across related brands
- Identity verification can fail or require manual review
Reality check
States worth considering
Finish line
What to deliver
- Design five screens focused on activity clarity, limit setting, exclusion confirmation, and the protected account state.
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Yeseva One & Merriweather
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Yeseva One & Merriweather
Clear interface writing gives people the confidence to understand what changed and decide what to do next.