A pretty indepth Tech/Account Question.
I ported over two customers earlier this month from At&t to Verizon. We had a small snag in the port process but were able to get it fixed. Ever since, the customer has been getting spotty coverage. The customers two phones will not recieve phone calls half the time and text messages get delivered several hours later, even from one phone on the account to the other. The phones in question are the LG Cosmos, phones that i personally haven't had any problems with. I have already replaced both devices.
The area in question is completely covered by Verizon. There are no known dead zones and i have been able to duplicate the problem with the custom...
(continues)
I often feel like as soon as i mutter the phrase "i'm an indirect store manager" the person on the other end of the phone automatically goes into "ok this guy is a f*cking idiot" mode.
Whenever you have a mobile number, there's a "phone number" and a "network access" number. For native Verizon numbers, that is often the same. For ported numbers, that is never the same.
Think of your cell phone number like a mask. Your true identity to disguised beneath it. If your cell number is 123-4567, your network access number may be 345-2049.
My wife's mobile number is entirely different from her network number, because her number was originally a T-Mobile number. My mobile number, on the other hand, was originally assigned to Verizon and the number had never been used as someone else's network number (which happens), so my mobile and my network numbers are ident...
(continues)
You might want to also check with LNP Tier 2 to make sure that the port was completed with no glitches.
Is the MDN that you ported over a 'local' area code? Is the home SID the same as the serving SID? Do you happen to know if they are running off a Lucent or Autoplex-1000 switch?