Reading store reviews after a billing cycle

Public store reviews are a poor average and a useful queue. After a postpaid cycle date, the one-star notes that mention “bill,” “deduct,” or “double” often describe the same three screens: bill summary, itemised view, and pay. If measurement does not cover those screens, the tickets and the store page will tell the story first.

What we extract

We do not average stars. We tag a month of reviews for reload, roaming, login, crash, and billing. Billing tags get a second pass: is the person angry that the amount is wrong, or that the app would not show the amount at all? The second case is an app measurement and navigation problem. The first case may be a core billing dispute that the app can only display.

Timing against the cycle

If your billing dates are clustered, plot review volume in the three days after those dates. A spike that mentions “cannot open bill” belongs next to the event that should fire when the bill PDF or HTML view loads. If that event is missing, you are flying on call-centre volume alone.

Tone

A store page is not a courtroom. People write in anger and in mixed languages. The job is to find repeated screen failures, then confirm them on test accounts. We quote phrases in the review document only when they point to a named screen. We do not use store ratings as a substitute for a walkthrough.