stories filed under: "installation"
by Mike Masnick
Wed, Nov 7th 2007 11:54pm
We've had a few stories now about Verizon FiOS (its fiber optic broadband offering) installs that resulted in fires and damaged properties. While Verizon's PR folks have focused an awful lot of effort on convincing reporters that where there's smoke there isn't necessarily fire, perhaps the company should put a few more resources towards both preventing fires and fixing things up for those whose property was destroyed by install-related fires. Broadband Reports points us to yet another FiOS-related fire (which the reporter at Network World is now calling FiOS: Fire is Our Speciality), where Verizon promised to help the family impacted by paying for their living expenses and reimbursing them for destroyed property. The only problem? That bill came to $58,000, and Verizon only wants to pay $1,800 of it. The family has now decided to take the matter to court. You would think, given the negative publicity over the previous fires, that Verizon would know to pay up and apologize, rather than try to stiff the folks whose house they set on fire.
Fri, Sep 7th 2007 4:27am
from the yes,-again dept
Last month, Verizon's PR folks went back and forth with a writer over whether or not one of their technicians actually started a fire at a customer's house when installing its FiOS service. The fire department says there was a fire, but Verizon denies that. In any case, the damage the installation caused was certainly significant, even if Verizon so generously paid for repairs. A month later, and look what's happened (again): a Verizon FiOS installer once again clipped an electrical wire, resulting in $2,650 worth of damage and a smoking house. Verizon's PR people are more than welcome to (again) argue about whether or not the smoke means there was fire, but regardless of their definition, these sorts of stories continue to pile up.