A carrier billing and service dispute, documented rather than argued. Complaints filed with the FCC and the BBB, a settlement reached on a recorded line, and every measurement kept — including one that cannot yet be attributed. This is a working public record, including unresolved items.
This did not start in August. It started last month, with the service disconnected after the bill had already been paid.
That was the first time I measured it rather than described it. I ran a speed test during that outage and kept the result. Its exact date and test ID are not verified in this record, so no figures from it appear on this page — it belongs in the chronology as the point where documentation started, and nothing more is claimed for it than that.
Underneath the billing problem sat the one that actually cost me work. The connection had degraded to the point of being unusable — video wouldn't upload, transfers failed, and the hotspot add-on I pay for worked intermittently or not at all.
Service went down again despite a settled account showing a zero balance, and the promised technician callback never came.
The support chat that day produced commitments. Those commitments were not applied. The specifics are not reproduced here because the chat record has not yet been placed into this file, and nothing goes on this page from memory — but the outcome is documented and simple: what was agreed in that channel did not happen, which is why the dispute continued.
Financial compensation and technical resolution are separate outcomes. Accepting a credit does not establish that the underlying service failure has been repaired.
Formal complaints went to the FCC and the Better Business Bureau. Both were submitted and both returned confirmations.
The complaints were submitted after the August 5 support channel failed and before the August 6 retention settlement. Filed and confirmed, on the record, while the dispute was still open.
Forty-five minutes with a retention representative, on a recorded line.
The counter I put was straightforward and true: a competitor was offering device payoff and new equipment and I was prepared to take it — but I would rather stay if the fault got fixed. That's leverage without threat. It isn't a bluff if you'd actually do it, and stating a real alternative calmly gives the person on the other end something to work with internally.
What the call produced, as confirmed:
Worth recording honestly, because it cuts against how these stories usually get told: the representative was the reason I stayed. Not the credits. She engaged with the actual problem instead of processing me. The company's policy was the constraint. She worked inside it in good faith, and I said so on the call.
An August 7 test recorded 1.95 Mbps, but the result identifies the connection as Optimum over Wi-Fi. It therefore cannot currently be attributed to Verizon cellular service.
The result screen records the connection as Optimum over Wi-Fi, with the test server listed as Optimum Online, Tyler, TX. The device was an iPad Pro 11-inch (M5). Those figures document poor loaded performance on whatever connection was actually being measured — they do not isolate a cause, and they do not establish carrier cellular throughput. This result stays on the page because removing inconvenient evidence is its own kind of dishonesty, but it carries no weight in the dispute until the attribution question is settled.
A controlled comparison is being collected: the same carrier tablet, Wi-Fi explicitly disabled, tested at two locations. That removes the ambiguity this result has, and it is the evidence the technical side of this dispute will actually rest on.
Both columns are the deliverable. A case study that publishes only the wins is advertising.
A financial settlement was confirmed. Some relief consists of scheduled future credits, and the technical problem remains unresolved. Complaints are filed and confirmed with both regulators, the agreement from the recorded call is on record, and controlled testing is being collected to settle the technical question properly. Follow-up correspondence drafted since then is tracked separately from the filed complaints. Whatever happens next gets documented here the same way this did.
Nothing here is specific to a phone company. The same six steps run on a garden, a training module, or a client brief — the subject changes and the process doesn't.
The most-quoted number in this file is the one that carries the least weight, because the result screen names a connection that can't be tied to the carrier. It stays on the page, quarantined, rather than quietly deleted. Documentation that hides its own gaps isn't documentation.
An ambiguous measurement is worth almost nothing in a dispute. Same device, Wi-Fi off, two locations, controlled conditions — that's the difference between a number and evidence, and it costs nothing extra except deciding it in advance.
Financial compensation and technical resolution are separate outcomes. Accepting a credit does not establish that the underlying service failure has been repaired, and a settlement that pays out over 34 months isn't money recovered — it's money promised.
The regulator complaints went in after the support channel failed and before the retention settlement. Filed and confirmed beats held in reserve, because a complaint you're saving to deploy is a bluff and a complaint already on record is a fact.
A competitor's actual offer, stated calmly, is information. A threat you wouldn't act on is noise, and experienced representatives can tell the difference instantly.
The individual on the phone was constrained by policy she didn't write, and she still worked the problem honestly. Documentation that flattens that into "I beat the phone company" is less accurate and less useful.