Unbelievable!! Port issue

[ntrimm]

So, our business account had two lines that were waiting on the T-bolt to port from Sprint. So the Tbolt came out on the 17th but the two users on the Sprint lines were out of town. So, with concerns about inventory with Tbolt we started 2 temp lines with Tbolt. Monday the 21st, we ported the Sprint numbers to Verizon to replace the temp numbers on the T-bolt. BIG PROBLEM. Its been 30 hours now and one line went through successfully (with the change of a new 4G sim and 2 hours on the phone with support) The other is lost in transition from Sprint to Verizon. It wont even show up in Verizons system in order for them to manually push it to our business account. The problem is the Sprint phone is turned off now and we can undo the port nor can he use his old phone. So he is stuck with no phone (business phone). 6 hours on the phone with Verizon today for them to only tell me they have escalated the problem up the I.T chain as far as they can go and it could be 72 hours before a fix, if a fix at all. Anyone else have this issue and does anyone have any suggestions for me?

 

[jfoofoo#AC]

nope and this doesn't sound like a tbolt issue.. rather than phone company customer service/IT issue.

 

[Benjaminarroyo]

Trying to switch from sprint to Verizon and having same issues

I ordered my new thunderbolt last Thursday and as of today, 1 day short of a week the IT ticket has been working in my issue since last Friday. Not to mention that I'm a business owner and causing me to loose business because customers cannot call me. I'm stuck and Verizon supervisors, 8 now to be exact say they are going to call me back with the status and not 1 Verizon representative has called back with a resolution. I totally understand computer issues, but I don't understand the awful follow through Verizon has...Verizon, you might have the best network but you've lost a new customer already! The issue is that the port transaction or my line is caught up in a "hot line" status and no one seems to know how to resolve this.

 

[KSmithInNY]

Moved to Carrier specific thread rather than phone specific thread. Same issue would have occured despite the device.