..:: Comcast Can Kiss My Ass Final Round ::..

Comcast made good, and sent a tech and a senior tech on out to the homestead.  Before they arrived, I tested out the phone again with local and long distance calls… in an odd twist, I could make local calls and not long distance suddenly.  The whole thing flip-flopped on me prior to their arrival.

Well, the techs were there when promised.  They tried out the phone and found what I discovered to be true.  They made a bunch of calls to the call center, tried out a bunch of things.  In the end, you know what they found?  Something that was brought up in passing by the tech that was at the house on Saturday… there was something wrong with the phone… the number 9 was wonky.

Now, before I have the interwebs jump on me and say “you ass clown… why didn’t you check to see if you were dialing all the numbers?”  Well, you know the pharmacy, the pizza place, the quasipalindromic voicemail box in Seattle… not a 9 in the bunch.  So, what the fuck?  I don’t know, and neither entirely did the techs.  It’s a factor, definitely, but not the entire issue.

But they were cool, I’ll give them that.  They suggested a swap out on the handset, and even cleaned up a rats nest of wires in the kitchen wall for me.

So, in the end, it’s over.  A wonky number 9 doesn’t explain Comcast’s inability to communicate from call center to the field, from one division of customer service to another, from dispatch to the tech in the field, and for the tech in the field to replace a battery when one is known to be dead.  The troubleshooting flow chart Comcast follows should not resemble a Choose Your Own Adventure book where different phone reps arrive at different definitive solutions ranging from a bad modem, to a bad battery, to a fault with a switch to black magic or voodoo.

There you have it Comcast.  Learn from this experience.  And comp me a couple years of voice and data for the valuable training tool and lesson I have provided.