Sprint is utterly adorable. So far there have been two notable problems we’ve had, the first was trying to get a new line established for a new staff member in the office. They gave us a number with the exchange 363, which fails local dialing because the other POTS companies don’t understand that 363 is in the 269 area code. Sprint’s solution wasn’t “We’ll fix it” but “You should call the other POTS companies and request it be fixed.” Oh, really now? The second problem we had been crappy service in Kalamazoo Township. Instead of owning the problem, they simply just gave me the 1-800 number to essentially DIY. If I had 3 lines and ran a dumpy mom-n-pop shop out of Climax Michigan I’d be fine with it, but I’ve got damn near 25 lines and I spend two grand a month – I would appreciate some TLC god damn it. So here is an email I wrote to Sprint…

Thanks for the information.

This is the second time that Sprint has kicked the can as it were, the first time was Sprint’s determination that their customers were the proper party to resolve local carrier exchange switching errors and now with poor signal quality, as well. On some level I could be upset that Sprint has refused to take ownership of problems related to their network and problems brought to them by their customers but I am really not that invested in haranguing either of you about this. The first time is a mistake, the second time is by design. I have made a personal resolution to reduce the amount of stress and trim my rage for my own personal health and wellbeing. We are learning quickly that Sprint isn’t really invested in the whole ‘taking ownership of problems’ practice and because of these failures we are awaiting the announcement of an Apple iPhone 4-CDMA class device to be brought to Verizon and when that device is announced and manufactured I am going to recommend that we take our business to Verizon.  I don’t expect any better customer support from Verizon, but at least I won’t be filled with fantasies of skeet-shooting my mobile device any longer and feeling little blossoms of cluster headaches whenever I reset my device and get mocked by “SprintSpeed”.

As for the twin problems, the first one being the 363 local exchange switching error, we’ve avoided that by swapping numbers with a line number we already had possession of in the 599 exchange, solving that problem by sheer abandonment. As for the second problem, conditions may have improved for my user who was having problems, and if they come up again I will not bother either of you but take the issue to BWTS directly.

Thanks

So all we have to do now is wait. Wait for Verizon and Apple to ink those contracts, make sure Qualcomm has enough Viagra to go the distance, and hope that Foxconn doesn’t endure anymore “It’s Raining Men (and Women)” 🙂