Onboarding
Make sure new players can actually get in.
Registration is the first thing every player does, and the first place many of them leave. We walk through your sign-up and sign-in the way a local player does, on their phone and network, and record exactly where it stops.
What we check
- Entry points and registration fields
- Verification requests such as SMS or email codes
- Sign-in and sign-out
- Error and recovery messages
- What happens on retry after a failed step
What you receive
- Account preconditions for each case
- A step-by-step recording
- The messages the player saw
- Outcome of each attempt and the point of failure
- A likely cause and suggested fixes from engineers experienced in iGaming
What it looks like
Every finding comes with the evidence behind it.
This is the shape of a single record in your report.
Examples of what this can surface
- A verification code arrives late, or not at all, on a local carrier
- A required field fails with no message telling the player what to fix
- Sign-in succeeds but returns the player to a blank page
- Retrying after a failed step restarts the whole form
VN-REG-01P2
Verification code arrives after it expires
- Case
- Register with a new mobile number
- Expected
- Code arrives and can be used within its validity
- Observed
- Code arrived after it had expired; resend showed the same message
- Environment
- Ho Chi Minh City · OPPO Reno11 · Viettel 4G
- Evidence
- Recording, 2 screenshots
- Likely cause
- Code delivery runs over a carrier route that is slow in this market, and the code validity is short.
- Suggested fix
- Add a second delivery route, lengthen the validity and show a clear resend countdown.
Before we start
We agree the details before any test runs.
What we need from you
- A test build or staging address
- Test accounts, or permission to register new ones, and how test phone numbers receive codes
- The sign-up rules (age gate, bonus opt-in, referral fields and so on)
What we agree up front
- Target market and test location
- The build, accounts and access we will use
- Devices and networks
- Steps and expected results
- Number of attempts, delivery timing and retests
Functional QA does not constitute security testing, game-math validation or certification. Additional work is scoped separately. Likely causes and fixes are our engineers' assessment from observation and experience. Please confirm them against your own logs and code.
Want this tested in your markets?
Tell us the product, the markets and the journeys that matter. We will come back with a scope and a plan.