Normal Comcast Mess without resolution in reasonable amount of time
I opened a ticket 3 days ago for a 'bring my own domain' request that has been 'stuck' with a processing status for nearly two weeks.
Of course I got the normal it will be up to 48 hours until someone from Tier 2 will get back to you.
Finally a Tier 2 rep got back to me day before yesterday... He knew absolutely NOTHING! In fact he even asked for my portal username and password so he could log in and 'click along with me' to see what was happening.
After explaining exactly what had been done, transfer request, creation of cname on existing server, etc he gave the normal answer of "I can't do anything about that" I will send an email to another group to attempt to resolve it and get back to you tomorrow!
So yesterday morning comes along. he calls back and tells me that "All is good!" We have resolved your issue!" I told him I had a busy day on the road. Thank you and I'll go in and check when I get in.
Of course late last night when I logged in to the portal my status was still "processing" He did absolutely nothing! Other than close my ticket of course.
I call in immediately to support. As usual get a very nice young lady who agrees that this should not have been handled this way. She understands completely. If should could she would go in and fix it immediately but of course cannot but gives me a number of someone and hosting who can fix it.
I tried to call that number but the wait exceeded my need for sleep. At about 10 this morning I called back in to the number she gave me. Was promptly told they cannot help me you need to talk to CS. Told me they would transfer and prompty hung up.
I then called CS.. Asked to speak to a Tech manager. After about 10 minutes I got a "John" on the phone that claimed he was a supervisor. Was was quick to continually apologize. Told me he had to open another ticket but would escalate and keep track of this call personally and back to me by phone very soon.
Imagine this. 6+ hours later I still haven't heard anything and of course the problem is not resolved!