Client notes

What teams said after the readout

Notes from product, channel, and prepaid owners who sat a review or a funnel reading. They mention screens, devices, and the awkward bits, not a score.

Farah Idris

Farah Idris · Prepaid self-care product

Customer-app measurement review

They made us complete a RM 10 reload on the same Android model we still give out in Johor stores. The success event fired on the spinner, not on the balance change. We had been arguing with commercial for months using two different counts. The written map was blunt, which we needed. I still wish they had been allowed into the vendor’s backlog meeting; that part stayed with us.

Daniel Koh

Daniel Koh · Digital channel

Recharge and bill-pay funnel review

Bill pay after payday was the brief. They showed the English receipt event and the Bahasa path that only sent a generic payment flag. Finance had been told Chinese users paid less. They were not. The names were different. Short document, one painful table.

Meera S.

Meera S. · Store listing owner

Store listing and first-week reading

The Play Store screenshots still showed a roaming pack we had retired. Priya lined that up with first-week sessions that died on the language picker. We changed the shots the same week. The first-run OTP note was fair and slightly irritating, because we already knew and had not scheduled it.

Hafiz Rahman

Hafiz Rahman · App engineering counterpart

Working session, Johor Bahru

Half day, projector, one mid-ranger. Wei Jie would not let us mark reload_success until the test SIM showed credit. We left with a marked catalogue and two items for the next sprint. No slide theatre.

A longer note: roaming packs before the checkpoint

A southern operator asked us to sit with the roaming purchase used by people who cross to Singapore in the morning. The brief sounded narrow. The event fired on the first tap of “Buy.” Activation in billing lagged long enough that a person could enter the checkpoint with a thank-you screen and no pack.

We walked the journey on a store-typical Android in the office, then again with the radio deliberately poor. The retry created a second purchase event without a pack type. Commercial thought they had sold two packs. They had sold none yet.

The review named the success definition, the missing pack type, and the Bahasa confirmation that still used an older string. Product took the definition. The vendor took the pack type. We were not in the vendor meeting; Farah’s reservation above is the same pattern. The operator sent a short follow-up two sprints later: the thank-you screen now waited on activation, and the causeway tickets about “paid but not roaming” dropped in the weeks they could compare.

We do not treat that drop as a trophy percentage. We treat it as evidence that the screen and the billing record were finally the same object.