Search DC to White Light

Showing posts with label phone. Show all posts
Showing posts with label phone. Show all posts

Wednesday, July 11, 2012

CEO's: Have you been duped?

An open letter to CEO’s, COO’s and CMO’s:

Let’s see.  How do I say this?  How ‘bout this…is your customer service department/division/person really giving any service?

Now, let me back up.  Somewhere along the line, a really bright person stood in front of you with a Powerpoint® presentation and showed how automated customer service would save you money while at the same time keeping customers happy by providing faster service.

Well, friends, hate to tell you, but you got sold a bill of goods.  Want proof?  Think of a problem that you might have with one of your products or services.  Call your own customer service line.  WARNING:  this is not for the faint-of-heart!  If you are taking prescription drugs or have a history of health problems, I suggest you have someone else make that call while you monitor on a speakerphone.

You’ll find out quickly just how bad things are.  Actually, it may not be so quickly.  You could be pressing 1 the 2 then 5 then 1 then 4 then…and then you may arrive at a person to whom you’ve given NO authority except to say, “Sorry, it’s company policy,” and when you want to discuss it with an actual decision maker, you’re told that they can only return calls and then, only in the morning.  At this point, you’ll realize that you’ve invested anywhere at least ten and maybe twenty or more minutes to get nowhere.  Well, actually, at least you’ve probably made a great voice recording (for training purposes only, of course)*.

Think you’ll get a call back from that decision maker?  Don’ take it to Vegas.

Now, about that phone tree and saving time.  Well, it saves time for your company, I guess, but it wastes a great deal of your customers’ time.  As you use automation to sort and categorize, you waste hours and hours of time on your customers’ behalf.  And they’re getting tired of it.  Tired of pressing numbers, tired of punching in a phone number or credit card or account number only to hear from the live person you finally get to say “May I have your (phone, credit card, account) number please?“  Why did you have them enter it in the first place?  Ah yes.  The prescreener.  But that person with the Powerpoint didn’t tell you about the costs to port that information to the servicer’s computer screen, did they?

The fix:
  • One (o-n-e) automated encounter before connecting the caller to a live person
  • Empowered people who actually know the product
  • Ability to escalate a problem or issue immediately
But that’ll cost me money.  Deal with it.  Look upon it as priming the pump – the one that pumps out happier consumers.  

Go ahead.  Make the call.  But on your cell, dial 911 so that all you have to do is hit “Send” when you start feeling ill.

*NB: A lot of call center recorders continue even when you’re on hold.  That can be fun.

Monday, August 1, 2011

Gone in Sixty Seconds

The star of this one isn’t Nicolas Cage and the title really isn’t as above but rather, Obsolete in 18 Months.

Technology keeps marching, for sure but now it’s double time or better. Maybe it’s the technology or maybe it’s just churning the masses and generating new purchases.

Hey, I can understand true advances but the one I’m writing about is not. It’s an “upgrade” by what you want to think is one of the good guys. Google.

Google and T-Mobile launched the MyTouch and Android pairing. Pretty good competition for iPhone. Worked great. I bought one. The Android platform is open source and thousands of folks are developing apps. I’m amidst one right now.

Well I was – until awhile ago. The phone slowed to a crawl. Sometimes locked up, even rebooted on its own. But the biggest annoyance is that the touch screen runs slowly, often responding to a touch long after a finger has left it. And with that, slow screen changes including over a minute for the screen to rewrite itself after dialing a phone call or reading an email.

Calls to T-Mobile were a laugh with the first one beginning with, “Have you turned your phone on and off?” Well actually, it didn’t begin there. It began with them asking if I was aware of a certain promotion…I had to remind them that they shouldn’t be pushing anything on me while my phone was misbehaving.

At first, the person denied that it was a common issue – until I pointed to pages on T-Mobile’s own forums and all of the problems and complaints posted. Then she admitted that, well, there have been some other calls. Well, if the calls were like the posts, people aren’t happy. In fact, they’re angry at both T-Mobile and Google

There were no improvements after the first call. Reset a lot of things, turned off one app that had decided to run all the time, but no improvements.

I made a trip to the T-Mobile store. “You’re not alone,” the kind guy behind the counter said. “I probably had five or six others just today.”

“So what is it?” I hoped for an instant fix.

“Google.” Well, Android 2.2, to be specific,” he smiled.

I wasn’t smiling as he continued, “1.6 was fine but when they went to 2.2, the MyTouch 3G saw all sorts of problems. Looks like your phone has most of them.”

“How do I fix it?”

“Go back to 1.6,” he said. But you don’t have long on your contract…stick it out and get a different phone.”

That wasn’t the right answer. Especially when he said the alternative was to go back to 1.6 which meant wiping everything on the phone, reverting to the old version of Android and reloading it all. I asked if there was a patch coming for 2.2 which would fix the problems and he said it wasn’t likely.

OK, off to the web. The guy was right. Lots of folks getting burned by a non-caring Google. At least that’s how it seemed. Apparently, I was lucky. At least my alarm still worked and I could get text messages. But as I read the complaints and checked them out, I found I had even more issues. Battery life, for sure and keyboard freezes. Now I get the battery life issue – a newer OS may be running more items in the background and it’s all those cycles in CMOS that suck current – but keyboard freezes? C’mon, Google. A $600 stock price doesn’t give you the right to ignore your customers…unless your goal is a $300 stock price!

Next came another call to T-Mobile. “May I have your phone number?” he asked.

“You mean the one the automated system already had me type in?”

“Yes.”

“XXX XXX XXXX.”

“And the last four of your social…”

“And you mean the ones the automated system already me type in?”

“I’m sorry. That information doesn’t come over to us.”

“Why?”

“Uh…”

“Never mind. I know it’s not you. Let’s hope someone actually listens to the recording you’re making for ‘training’ purposes. Where do we start?”

“First, let’s turn your phone off and back on.”

I resisted the urge to stick my hand through the phone. “OK, but if you have any of my account history in front of you, you know this is going to take some time.

“That’s OK.”

So we waited…and waited. Did get to talk about weather.

“OK. We’re back up. I counted almost four minutes. How about you?”

“I’m sorry sir. How is it working? Can you open an app?”

The first one opened perfectly, as fast as I touched it. But when I closed it out and opened another, it slowed to its usual crawl. After some investigation, he was hard-pressed to believe that no one had told me that 2.2 allowed me do move apps from the phone to the SD card and that that should clear everything up.

The migration started…and stopped. “These apps have the “Move to SD Card” option greyed out,” I told him.

“Yeah. Some don’t work except on the phone.”

One after another gave me no option but to leave the app on the phone. But convinced that moving the apps would free up needed phone memory, I made a mistake. I told him that I could do these changes without holding him up and I’d call back if there were further problems. He thanked me, promised he had noted everything in my account history and hung up.

I moved another eight or 10 applications to the SD card then restarted the phone. The house of hope fell in on reboot. No better. I mean no better.

Another browse session just showed more disappointed users. I called T-Mobile customer care again and, as you would expect, went through the same restating of my information as before. I got to an unsympathetic lady who
• Read my account history
• Confirmed that a lot of people were having the problem
• Asked if I had turned the phone off and back on
• Disagreed when I asked her if she thought that Google and T-Mobile have rendered my phone obsolete (“…after all, you can revert to Android 1.6 and your phone will work…” she said.) – as if somehow asking me to spend hours fixing a problem brought about by an “upgrade” was fine with her
• Told me she didn’t know how to get my message (that Google and T-Mobile have to provide support for their products or say goodbye to consumers) to her supervisor or others in “management”

So, with an 18 month old phone, I’m on the make again. This time, though, it’s for a new service provider as well as new phone. I’d say, “Farewell, Android, [Aquarius] and we thank you,” but the astronauts on Apollo 13 were saved and Aquarius helped. Android burned up on reentry.