For years, my secret shame has been that we still have a landline phone at home. Why? The number dates to 1997, so all my relatives know it and some of them still call it. Besides, I find the robocalls it attracts in campaign seasons weirdly fascinating.
Those things, however, weren’t worth the $15 Verizon charged us for the most minimal level of phone service. The obvious fix, one I endorsed in a 2015 USA Today column, was to port our number to an Internet-calling service. But months after third-party reviews and some testing of my own led me to pick Ooma‘s free service as that VoIP alternative, we were still wasting $15 a month–because I am sometimes slow and always easily distracted.
Finally, a Costco sale on a bundle of Ooma’s Telo VoIP adapter, a WiFi/Bluetooth module for it, and Ooma’s cordless handset got me to get moving on this transition.
After I put in the order on March 18 to port out our number (for which Ooma charges $40), it was active in Ooma’s system on the 22nd, allowing us to place and receive calls through the Telo. The next day I logged into our Verizon account to confirm the transfer.
That’s where things got interesting, as that site said our account had been disconnected.
Prior reports from Ooma users in various forums as well as Verizon PR’s own statements had led me to expect an industry-standard porting experience: You start the port with the new service, and there’s no need to talk to the old one until your number’s out of their grasp.
Perhaps I was wrong? I called Verizon to find out. That March 23 call was a model of how phone customer-support should work–I only had to provide my account number once, I wasn’t left on hold, and the rep said my Internet service should be fine.
Alas, other parts of Verizon had other ideas. A day later, a recorded message advised us to contact Verizon by April 14 to discuss new service options or risk disconnection a second robocall a week later cited the same April 14 deadline.
On April 4, our Internet went out.
The error page that interrupted my Web browsing told me to set up automatic payments to reactivate my service, but each attempt (using the same credit card as before) yielded a generic error message. It was time to call Verizon again.
Thirty-one minutes later, another pleasant rep was as confused as me, saying she couldn’t get the auto-pay setup to go through either. She said she’d get a specialist to work on my case and would call back with an update.
In the meantime, I enjoyed the unfair advantage of having two LTE hotspots in the house–required research to update a Wirecutter guide–that I could lean on for free in place of our inert Internet connection.
By the next evening, our Fios connection was back online, in keeping with the second rep’s “you should be all set” voicemail that afternoon. But Verizon’s site still listed our account as disconnected.
A third call Friday deepened the mystery. This rep said she saw two account numbers–and the one she could access listed our service as pending disconnection. Then I took another look at the e-mail Verizon sent after the second phone rep had pushed through my auto-pay enrollment: It cited an account number ending with seven digits that did not match my old one.
My best guess here, based only on my dealing with Verizon since it was Bell Atlantic, is that Verizon’s system has created a new account for me because the old one was somehow too intertwined with the phone number to keep around.
If so, I should be getting a letter with the new account number in the next day or so, after which I may or may not need to set up a new account online. Sound right? Or am I in for another long phone call?
Either way, I suspect I have not written my last post here on this subject.