Tagged with customer service

Another Communications Example Northwestel Could Learn From

Last week the blog platform I use, WordPress.com (the one you’re currently reading these words on), suffered some downtime.

The people who manage this platform went beyond just fixing the problem.

They told us what happened, what they did to fix it, how long it took, and what they’re doing to try and prevent another similar occurrence in the future. You can read their blog post here: Downtime.

That’s great customer service. And it’s for a service that’s totally free.

Now compare that to how Northwestel handles its outages. They provide almost no information, avoid even acknowledging that anything happened (it’s that maybe nobody noticed mentality), rarely explain what happened, don’t offer information about how they recovered from the outage, and provide no assurance that they’re working to avoid similar outages in the future.

That’s awful customer service. And it’s for a service I pay $90 a month for.

It would be both refreshing and encouraging if Northwestel made an effort to communicate these matters to its customers. It would provide an assurance to us that we can depend on the company to work in our interests and in the interest of providing quality services.

Instead, when the company hides behind a wall or buries its head in the sand over these issues, one begins to lose trust, faith, and wonder what the company is hiding.

Tagged , , ,

Communication Breakdown Within Northwestel Itself

Never mind apparently failing to share information with its parent company Bell, Northwestel seems to have a pretty deficient internal communications system, too.

Whoever’s managing the company’s Twitter feed posted that a cable cut disrupted service yesterday. Unfortunately, that person seems to have chosen not to share this information with other people in the company.

Since service levels do not seem to have recovered since that event (it’s taking upwards of 30 seconds to load web pages today), I called Northwestel’s customer service line to ask for more information.

The customer service rep I talked to was caught flat-footed. He didn’t even know that a cable had been cut or that service had been disrupted. When I mentioned the tweet he went silent.

I felt sorry for the guy. I’d inadvertently blindsided him with information that his managers should have prepared him to respond to. But instead he was completely off guard and unable to provide me with any information at all.

Smooth, Northwestel. Real smooth. You’re a tele-what company?

Tagged , ,

Bell-Northwestel Communication Breakdown?

Twice in the last 2 weeks, there’s been a significant, long-term Bell Mobility mobile network outage in at least Whitehorse. It’s coincided both times with reports on Twitter from Northwestel of internet disruptions due to to cut cables (here and here; the latter appears to apply only to Ross River).

In both cases you could “feel” a significant drop in internet quality by the virtue of a reduction in web page responsiveness and an almost total disability to stream media like video from YouTube or download files from iTunes. Late last night especially, it was painful to be online (like 20+ seconds to download basic web pages over my $90/month internet connection; ouch).

And almost exactly corresponding with the duration of that reduction in connectivity quality, the local mobile network was completely down (at least, the 3G one was; I can’t speak for the old CDMA one).

The first mobile-phone outage and internet service disruption, on the 13th, lasted about 10 hours. The second was last night and lasted for some people from about 10:30pm last night to 6:30am this morning.

The problem is, when you call Bell to ask about these significant outages, they don’t even know they occurred. Bell Mobility is completely unaware that their mobile networks are going down for significant periods of time in Whitehorse.

It could be that Bell is just not paying attention. Maybe their system isn’t as cutting edge as they make it out to be and they’re simply unable to monitor network stability and availability. One technical support rep (Glen) explained they aren’t aware of outages until a critical mass of customers call to complain; I find that very hard to believe.

And it’s suspect that these network outages coincide with internet access disruptions in Whitehorse. Could it be that Northwestel is somehow responsible for Bell’s mobile network in Whitehorse and, when they experience outages, they’re not reporting them to Bell for some reason?

Does anyone know anything about the internet or mobile network outages? Has anyone managed to extract an explanation for them from either Bell or Northwestel?

To be honest, I don’t even care about the circumstances. I just need an explanation, and I feel one is owed to me since I’m giving both of these companies a significant amount of money every month. And it irritates me that no explanation is forthcoming.

When information about service disruptions are difficult to attain from providers, however, one tends to become suspect about the circumstances and begin to think the providers are hiding something. Otherwise, why obfuscate?

It would be ideal if both service providers maintained some sort of status page that was maintained with up-to-date information about disruptions, upgrades, and anything else pertinent to the quality of service being provided. Web app developer 37 Signals, for example, provides just such a report, and it goes a long way to alleviating user anxiety. And I wouldn’t have to keep phoning them and hassling them, which would save them and me tons of time and money.

Instead, Bell and Northwestel, either intentionally or by accident, choose to withhold this information or make it very difficult to attain. Which leads to a lot of confused and pissed off customers, like me and several others I’m aware of.

Why hide your mistakes when it’s so much easier to admit them, learn from them, and move on?

I don’t even know why I ask really, about the philosophical aspects of admitting mistakes, or about Bell’s and Northwestel’s flubs. I should know by now that these are two companies that rejoice in stonewalling their customers, and that’s never going to change.

Tagged , , , ,

Hello, Solo Mobile? Is Anybody There? (UPDATE)

Sometimes I experience such a resoundingly bad customer experience I can’t help but relate it to the world at large.

I called up Solo Mobile this afternoon to ask about their rates and plans. I used the number on their web site, 1-877-999-7656.

It seems this is their customer service number, as I was asked for my Solo Mobile number. When I didn’t enter one, the system told me to hit the # key if I wanted to ask about becoming a new customer. So I did this.

Then I received a message that their call centre was closed. The system informed me that they are open from 8:30am to 9:00pm Monday to Friday. Odd. I was calling at 3:00pm on a Wednesday.

The system told me I could hit 1 to leave a voicemail message, which I did. Then the system told me that the voice mailbox belonging to Solo Mobile was full. That sort of made me chuckle. I hung up.

I went back to their web site, as I’d noticed a callback button. Here’s what I got when I clicked that:

Unfortunately, our callback system is temporarily unavailable. Please try again later. For Service during our regular business hours, please call 1-877-999-7656.

Been there, done that. Something is clearly wrong here.

There’s enough information on their web site, so I thought I may be able to complete the transaction myself. So I clicked on the phone I liked, but quickly discovered that their shopping cart system is broken. Despite having added a phone to it, the amount I was going to pay was a mere $0.

I followed the purchase process through anyway (more to see how bad it could get than anything) and ended up with this message:

Internal Error

An Error has Occured

Please return to home page.

Okay. Last ditch effort. Email.

I clicked on the “Send Us an Email” link on their Contact Us page, filled out the form there, and submitted it.

Moments later, I received this email message from Solo Mobile in response:

Good day, We regret to inform you that due to technical difficulties with our systems, all the information contained in your message was lost. We sincerely regret the inconvenience this situation may cause.

That’s about when I decided to write this blog post. Does anybody even work at Solo Mobile? Aren’t they aware that their entire system is FUBAR?

Oh, wait. They’re a subsidiary of Bell. Well. That explains everything, then.

The Next Day…

I received this message from a Solo Mobile representative today:

Good day Mr. Robulack,

Thank you for using Solo Mobile’s Internet Customer Care. My name is Darine. I have read your message and I am pleased to assist you.

However, I wish to clarify that your question refers to products and services provided by Bell Mobility, which has its own client care service. We suggest that you submit your question at the following URL address:

http://www.bell.ca/contactus

Thank you for using Solo Mobile’s Web site. Don’t hesitate to e-mail us again at:

http://www.solomobile.ca/Default.aspx#/Contact-Us/Contact-Us.aspx

Have a really nice day

Darine (6026572)
Solo Mobile Internet Client Care

Well, at least she was polite, even if she didn’t quite comprehend the gist of this blog post. Whatever.

My experience makes me wonder if we won’t be seeing this sort of memorial service soon:

Solo Mobile Memorial Service

Solo Mobile Memorial Service

Too bad the company’s customer intake service doesn’t match the quality of their advertising because the Solo Mobile commercial I pulled this image from is actually very funny. Check it out:

Tagged , , ,

Customer Service, Good and Bad

I’ve recently had two notable customer service experiences. One was awesome, the other was autrocious. Both are worth sharing as a lesson for businesses that engage in customer service.

The amazing customer service experience I recently had was delivered by Apple’s MobileMe.

For some time I had been experiencing a problem with syncing failures between my desktop iCal calendar and the calendars on the MobileMe web site and my iPhone. I had spent a considerable amount of time self-troubleshooting the problem using Apple’s online support documentation, and I had failed to resolve it. By the time I chose to engage with the chat-based support of MobileMe, I was borderline irate. In fact, I was actively researching alternatives to MobileMe.

It didn’t take the MobileMe support technician, Nicholas C, long to cool me down, however. After he read my brieft rant about all the time I’d spent on the matter already, he replied: “I really appreciate the insight to the issue and im sure we can get this up and running as it should.” As simple a reply as it was, I found it reassuring. He didn’t dismiss my efforts, was able to see past my somewhat rude mannerisms, and he approached the problem with positivity.

Throughout our hour-long session, in fact, Nicholas punctuated our chat with statements like, “Awesome, you’re doing great Andrew,” and, “you did great.” I consider myself an advanced Mac user, and many of the troubleshooting tasks he had me perform were mundane. However, the simple fact that Nicholas was recognizing the time and effort I was investing into the process was satisfying.

Nicholas worked with me through Apple’s online documentation twice, but he was not able to resolve my issue this way either. At this point, I asked him: “should I just cry now? ;-) ” He replied: “please no tears, i dont want to give up. This is pretty different though… lease give me a moment to research this for us… I want to see what im missing or waht else can be done”

I like how he recognized that the situation was now unusual, and also that he referred to “us,” recognizing the fact that we were working together on the matter. I’ve never experienced that before during a tech support session. Typically a support technician has difficulty disassociating him or herself from the role as a representative of their employer.  This can lead to adversarial discussions when the technician becomes defensive of the company’s product or service. Instead, Nicholas adopted a tone of advocacy, and that had a tremendous reassuring effect on me.

In fact, despite the fact that this technical problem with MobileMe was consuming a tremendous amount of my time, Nicholas’ ability to openly recognize my interests and communicate a commitment to collaboratively resolving my problems overcame my anger at the technical failure of the MobileMe service itself. And by creatively problem-solving with me, effectively reaching a resolution, my chagrin was turned to gratitude and I left our session with a renewed faith in the MobileMe service.

Nicholas closed our chat session by saying, “i really appreciate your patience working with me,” and I believe he honestly meant it.

Now compare that to an abysmal customer service experience I recently received from the web business services company, Business Catalyst (aka Good Barry).

In a nutshell, a variety of company representatives including several members of the executive team, stonewalled my efforts at communication for over 7 weeks. I won’t go into great detail on this matter, but suffice to say that I was attempting to rectify a minor billing matter with the account of a not-for-profit client. For some reason, however, the accounts team, the sales team, and the executive team opted to completely ignore my repeated email and Twitter requests for assistance.

When I finally announced my client’s departure from the Good Barry hosting environment as a result of the poor customer service I’d received, one of their team invited me to email him regarding the issue. I did. Not surprisingly, he failed to respond.

I finally received an email with a resolution to my problem the other day — a full two months after I’d first made a request regarding it. There was no apology for the delay, no recognition of the tremendous amount of time that I’d invested in seeking to have a simple matter dealt with; just a simple email with an explanation of the action that had been taken.

Ironically, Business Catalyst provides a suite of web-based tools that promise to enhance customer service for online businesses. My experience suggests that more than software is required for a positive outcome to a customer’s concerns. More valuable are people within an organization who take a genuine interest in them.

With MobileMe, I started my customer service experience ready to move on. Thanks to Nicholas, my commitment to MobileMe is instead renewed (as will be my account later this year).

Back in January when I began my efforts to resolve my issue with Business Catalyst, I had lined up several clients to subscribe to their service and was on the verge of investing in the company as a resale partner. I’ve since placed those clients elsewhere and am now sworn off dealing with this company in any manner at all.

When I deal with clients, I act transparently and place their interests ahead of my own in the relationship. Clients and customers are the reason for any business’ existence, and it’s absolutely important that they remain satisfied with the business’ service, feel recognized, respected, and compelled to maintain the relationship.

Apple recently made me feel valuable and wanted while Business Catalyst silently expressed a preference to have me go away. I hope that me own efforts in customer service fall on the former end of that effect spectrum and never the latter.

Tagged , , , ,

quick lesson from bell mobility: establish and deliver consistent messaging

 

BellAs I fell asleep last night, I realized the one thing that most irritated me about my recent experience with Bell Mobility: a complete lack of consistency in communication. Over the course of a day, several of Bell Mobility’s staff delivered a wide variety of conflicting information on a single subject: how long it takes to provision a phone.

When I initially called to provision the pre-paid service on my phone, I spoke with Lucy. She was prompt and courteous, and informed me that my phone would be activated within 24 hours, but that I first had to call 1-888-542-3784 to get my phone programmed.

I dutifully called that number, but there was no answer. I called several times over several hours, but never was the phone picked up.

So I called back to Bell’s customer service. I spoke to a man this time, whose name I didn’t write down. He complained that my phone wasn’t activated, and he also complained that Lucy hadn’t programmed my phone while she had me on the line. “She should have programmed it,” he said. “Those CSRs are so lazy.” He helped me program my phone during that call (it took about 10 seconds). He also said I shouldn’t have to wait more than a couple of hours to have my phone activated.

The next morning – 24 hours after I’d initially spoken to Lucy – my phone still wasn’t activated, so I called Bell. Continue reading

Tagged , , ,

bell canada: a lesson in abysmal customer service

bell_pantone301_smMy monthly bill with Bell Canada is almost $200. That’s a serious amount of scratch for a cell phone.

Recently when I spoke with one of their customer service representatives, he referred to me as a “preferred” customer because of my high bill. That’s nice, but it doesn’t seem to be buying me any cred with the company.

I’ve fallen behind on my bill a bit lately (working for peanuts at a day care centre tends to constrain one’s revenue stream), but I’ve been negotiating the situation with Bell and making regular payments. Heck, I forked over $400 to them the day before Christmas. So I was astonished that at midnight Sunday they shut down my account without warning.

Any call I make just results in a busy tone, and apparently any inbound calls are ringing busy too. Sheesh, at least they could have let the calls ring through to voicemail. Are they adding insult to injury through public embarrassment?

I’ve even tried to call their billing department to make a payment, but those ring busy, too, despite an email message from “Carl” at their customer service department that states: “I wish to clarify that even if you have a lock on your phone you can call our Client Care Accounts Receivable department from your mobile phone.” Whatever, dude.

Speaking of email, that’s the form of correspondence I’ve been using with Bell. Unfortunately, the turnaround time on responses from them is over 24 hours. 24 hours! I thought this was a telecommunications company. I get faster responses via email from the Body Shop.

What’s worse, I’ve been trying to use their web site to make a payment, but each time I attempt to enter their bill payment service, I get a blank web page that simply reads, “Unexpected error.” Nice. So 1993.

It’s been almost four days now without mobile service for me, and I have yet to even reach a point of being able to communicate meaningfully with Bell beyond their pre-fab customer service emails, which have just been a complete waste of time. I get the sense they could care less.

Besides a quick vent, I suppose what I’m hoping to accomplish with this post is to share an abysmally bad customer service experience. If I’m a “preferred” customer, then I’d hate to think how Bell treats their, um, “unpreferred” customers. Because I’m feeling insulted and unwanted. Bell’s the underdog of Canadian mobile telecommunications providers. Rather than pissing off and driving away the customers they’ve got, you’d think they’d work extra hard at retaining us.

Tagged , , ,

starbucks’ moral message

Recently, I complained to Starbucks head office. The brewhouse was constantly fucking up my regular drink order. (Not too mention I often found myself waiting more than 10 minutes to get the wrong drink.)

My preferred Starbucks drink order? A quad-grande, half-full Americano.

The problem was, the baristas would tend to fill my cup to the brim, which produced a vile, watery beverage that too closely resembled Nabob.

So it was fitting that, in coupon form, this response arrived from Starbucks today:

half full americano coupon

Apparently it should never be half full either.

Tagged , , , ,
Follow

Get every new post delivered to your Inbox.

Join 297 other followers