SIM and account login
OTP, password, and biometric entry, including the cases that die when the SMS is slow. We check whether a failed OTP is counted separately from a killed session.
Audit scope
The audit scope is the journeys a Malaysian subscriber already uses: login, reload, bills, roaming, notices, language, and help — and the events attached to each.
OTP, password, and biometric entry, including the cases that die when the SMS is slow. We check whether a failed OTP is counted separately from a killed session.
Amount pick, payment method, confirmation, and the moment the balance actually moves. Duplicate taps on Friday evenings are in scope.
Cycle summary, itemised view if it exists, payment, and receipt. We compare the event with the SMS billing already sends.
Catalogue, purchase, and activation, with extra attention when the user is a Johor commuter on a clock.
Bahasa Malaysia, English, and Chinese paths for the same journey. Names must match or we will not compare them.
Outage banners, maintenance screens, chat or ticket entry. We note whether those taps are counted at all.
This page is the menu we use when scoping a customer-app measurement review. You may strike journeys that do not exist in your build. You may not add radio-network or core-billing audits without a separate brief.
Default walkthrough set: two Android models still common in Malaysian prepaid channels, and one iOS version that still accounts for a meaningful share of postpaid self-care. Flagship-only testing is a constraint we will write down, not a standard we will hide.
Fibre TV companions, dealer web portals, USSD, and in-store tablet apps. A second operator brand. Mystery shopping of dealers. Legal review of MCMC consumer notices.
Print it or send it with your contact note. Circle the journeys that generated tickets this quarter. If you want a sitting first, book a working session and bring the event catalogue to the table.