Billing complaints rose in two cities, and the share closed on the first contact fell from seven in ten to a third
Billing contacts in Los Angeles and Philadelphia reached per thousand subscribers today. The share closed on the first contact fell to across the same five days, while every other category closed at . Agents could find the charge the subscriber was ringing about in only of those contacts. Billing contacts still open after seven days reached , and the repeat rate held on its own level in every other category. Los Angeles rose to its own level and Philadelphia to , against Chicago at .
So what? Volume and resolution have different owners, and only one of them is billing. A contact that cannot be closed comes back, so handling cost climbs faster than the complaint count and the subscriber calls twice to hear the same non-answer.
34 vs 71%
the reading that decides the cost
2.06 vs 1.27 per thousand
up three fifths in five days
27.0 vs 12.9%
each contact comes back twice over
67 vs 92%
the agent cannot see what is being queried
81 vs 80%
so it is not staffing
1.06 vs 1.00× its own level
two cities, not the country
Billing resolution against every other category, day by day
The band is the range billing resolution holds on an ordinary day.
Billing closed of its contacts on the first one today, falling in each of the five days from the level it held before them. Every other category closed at across the same days. A billing defect on its own would lift the volume and leave resolution where it was. The two moving apart is the finding, rather than either one alone.
Complaint Rate · the change in each category and city, against its own level
One category, two cities. The network rise in New York is a different problem.
| Billing | Network | Device | Plan change | |
|---|---|---|---|---|
| Los Angeles | +68% | +4% | 0% | +2% |
| Philadelphia | +56% | +3% | −1% | 0% |
| Chicago | +6% | +2% | 0% | +1% |
| New York | +4% | +28% | 0% | 0% |
Billing in Los Angeles reached its own level and Philadelphia , against Chicago at . The network category moved only in New York, which is a different problem with a different owner. Every cell is read against its own level, so one national complaint total would have shown a flat line.
Each step against the number that normally reaches it.
The line on each bar is that row’s own expected level. The scale runs from 0 to 4200.
Agents found the charge being queried in of billing contacts and closed of them. It is a roaming charge that posts inside a total with no line of its own. There is nothing on the account to point at, and so nothing to explain. The contacts that did not close came back: the repeat rate reached while it held on its own level in every other category.
27.0 vs 12.9%
every one handled twice
34 vs 71%
and still falling today
2.06 vs 1.27 per thousand
on a base of two million
Resolution is the finding, not volume
Billing closed of its contacts first time while every other category closed at .
Why it matters: Volume sends this to billing. Resolution sends it to care operations, and that second fix is the one that stops the contacts coming back.
The agent cannot see the charge being queried
Agents found the charge in of billing contacts, and the ones that did not close came back at .
Why it matters: An agent cannot explain a line that is not there. That is a published answer rather than a headcount or a training course.
Two cities, read against themselves
Billing reached its own level in Los Angeles and in Philadelphia, against in Chicago.
Why it matters: A rise confined to two cities on one charge type is a specific thing to go and look at rather than a national care trend.
Which charge type are the billing contacts about?
Joins the complaint category to the billing lines on the same accounts.
How many of the open contacts have called more than twice?
Sizes what the missing answer costs in contacts handled.
Which plan family carries that charge?
Turns two cities into the population that will call next.
Is resolution falling on the same charge in any other city yet?
Uses the resolution reading as the early warning rather than the volume.
What did resolution do the last time a charge type was introduced?
Says whether this is the charge or the way changes are published.