Keeping Fios while porting out a landline phone number can be tricky

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.

Advertisements

2016 in review: a year of travel

This has been a trash bag of a year in so many ways, but on a personal level it could have been worse. As in, for a few weeks in the late winter I thought the overwhelming source of my income would vanish along with most of the Yahoo Tech operation.

Instead, Yahoo Finance picked me up before I’d gotten too far in exploring other possibilities. But the publicity over Yahoo’s content cutbacks wound up helping an overdue diversification of my income anyway–an editor at Consumer Reports e-mailed to ask if the news meant I’d be interested in writing for them. That led to a good series of stories, one not yet published.

2016-calendarI got another lucky break when a press-room meeting at the cable industry’s sparsely-attended INTX show yielded a string of assignments for the FierceTelecom group of sites.

These and other new clients still leave most of my income coming from a single company, but the totals aren’t as skewed as they were last year.

2016 did, however, see me do much better at finagling opportunities to speak on panels that got my travel expenses covered in the bargain. My mileage totals kept climbing as conferences and other tech events took me to places I’d hadn’t seen in 18 years (Hong Kong), 25 years (Paris), 43 years (Lisbon), or ever before (Israel), as well as my now-regular trips to Barcelona for Mobile World Congress and Berlin for IFA.

Domestically, New York was once again my most frequent travel destination, followed by Boston (now that both my brother and my mom live around there, I’m kind of obliged to find interesting tech events around the Hub). I also made my way to Austin, Denver, Las Vegas, New Orleans, and the Bay Area. Having SFO appear as a work destination only once seems like a grave dereliction of duty; I’ll try to do better.

(Read on after the jump to see all of my air travel plotted on a map of the world.)

My single favorite trip of the year: Viva Technology Paris, which brought me back to France for a second time this summer and showed that I could moderate four panels in a day. The trip also allowed enough downtime for me to take a train to the suburb of Louveciennes, knock on the door of the house my family rented a quarter-century ago, and discover that the family we’d rented the place from still lived there and was happy to let me look around.

The most challenging trip of 2016 would have to be Web Summit. Doing three panels on four hours of nightmare-level sleep is not an experience I need to repeat.

On that note, I can only hope that 2017 will bring less bad news than 2016. But I don’t know how it will turn out, only that I have work to do and good fortune to repay somehow.

Continue reading

Verizon’s online tech support needs some serious work

Yesterday I logged into my Verizon account for the first time in months and got an unpleasant and embarrassing surprise: a $2.80 “router maintenance” fee for having an old router. It was unpleasant as all junk fees are, embarrassing because I’d covered this exact problem in my USA Today column.

And Verizon had even warned me about the charge. Once. A July 19 e-mail advised me to upgrade my router to avoid the fee but offered no instructions on returning the router I hadn’t used since 2012–since we don’t get Fios TV, I’ve always been able to plug in the router of my choice.

verizon-chat-safari-incompatibilityI saw on Verizon’s support site that I could have them call me back, so I plugged in my number. After a day of nobody calling, I tweeted to the @VerizonSupport account that this support option wasn’t too supportive. In a direct-message reply, a rep told me to try Verizon’s chat instead.

I hadn’t seen that as a choice on the support site earlier, and clicking that link yielded a 1990s-esque error page with the useless message “We are sorry, but a problem with your request has occurred.” Somehow, this chat doesn’t work in Safari. Memo to Verizon: Running the default Mac browser is not an edge case.

I asked why we couldn’t deal with my problem in our direct-message chat. My interlocutor’s reply: “We have to secure your account and the chat is the secure location for that.”

verizon-tech-support-chatFine. The chat link did work in Chrome, and then I was treated to thanks-for-your-patience automated messages every 30 seconds, each heralded by an annoying chime. The chimes stopped at some point, but a rep never showed up until I closed the chat window by mistake.

I tried again, and a human entered the chat right away. The rep asked for my name, phone number, address and account number–an understandable request, since I wasn’t logged into my Verizon account in Chrome, but also information that I could have given just as easily in a Twitter DM chat.

Which would have been more secure too: Chrome reports that Verizon’s chat site employs the obsolete and insecure SHA-1 algorithm.

After some back and forth to establish that I haven’t powered on this old, Verizon-issued router in years, the rep said Verizon would send a return mailer kit for the thing and, after I asked a second time, said they would also refund the two months of router-maintenance charges.

Total time to get $5.60 returned to me: about two hours. I need to rethink this particular business model.

 

Year-end cash considerations

Yesterday, I forgot to invoice Yahoo for the last month’s worth of stories, and my stupid oversight may save me a little money next year.

That’s because the odds of payment for November’s work at Yahoo Finance arriving by Dec. 31 just got two days’ worse. And if I don’t get paid by then, I don’t owe taxes on the money until 2017.

2016-in-changeThe downside of this scenario is that my 2016 income, already assured to fall below 2015’s because I wrote less than usual in early summer, will drop even more. That potential embarrassment bugs me, but apparently not enough that I remembered to get the payment machinery in gear by Friday.

Deferring income isn’t exactly an advanced financial hack, but it is something I couldn’t do when I worked on a salary.

Tax calculations should also drive me to go on a moderate hardware-spending binge this month. My laptop and my desktop are both ancient, and replacing either now would put a nice big expense on my Schedule C.

Alas, Apple seems uninterested in shipping a new laptop in my price range, or a new desktop at any price. The Windows universe offers a few enticing options, but on closer inspection I realize that the laptops I like all omit at least one feature I’d appreciate.

More important, CES is now only a month away. And I can’t possibly make any big electronics purchases before using that event to see what the gadget industry has in store for this year–its no accident that electronics rarely land on my Christmas list.

That leaves me another way to lower my tax burden: a late-December spree of charitable donations. You may have read a lot on Twitter about #GivingTuesday this week, but for me that day comes on the last Tuesday of this month–when I know the donation will count for my 2016 taxes but won’t come due on on my credit-card bill until sometime in February. Please do the same if you’re financially able.