File a complaint about unlocking phone and customer/technical service

DrJRH
Newbie

We have been Verizon customers for that past 10 years or so. Their recent change in plan format, poor customer service, and better coverage from other carriers prompted us to switch carriers. We got the new service set up, my wife's phone and phone number transferred easily. The issue came with my phone. Verizon's phone locking policy says that phones will be unlocked after 60 days of service and there are nearly no reasons for a phone to be locked after that. I had my Samsung Galaxy S22 Ultra for 18 months so I was surprised when I went to move my phone, that it was locked. I contacted Verizon and was passed on at least 5 times during the call but nobody could help me except to say that if I paid off the balance, it would be unlocked. Reluctantly, I paid it off (I was going to have to anyway), then I was supposed to wait 24 hours, and check it. Still not unlocked. I called back and again was transferred several times and it was decided that they needed to fill out a form that would ask for a technical review and it should take about 24-48 hours. I was also to receive a text or email about the result. About 4 days later, no word so I called back, transferred several times again, until someone said they found the problem. The unlock date was for the year 20220 instead of 2022. I asked if they could change it but they said they could not. They submitted another request to fix it. This time I waited another 3 or 4 days and was told all was fixed; however, the phone still would not work and was still locked. I called again and they said everything was right on their end that it must be something with the phone. I finally just traded it in for another phone which activated immediately. Everyone I talked to outside of Verizon said that this should have been an easy problem to fix but I never felt Verizon wanted to fix it. In addition, several of the people tried to get me to stay with different offers instead of fixing my phone.

0 Likes
0 Replies