Thinking through the customer contact process

Without going into all of the particulars, or naming names, I’ve been having a minor back-and-forth and with my health insurance provider.

Now, I first have to say that, overall, the service from this insurance provider has been excellent. They pay our doctors’ and hospital bills promptly, don’t seem to reject things willy-nilly, provide very clear information (for the most part), and employ customer service reps who are pleasant, knowledgeable, helpful, and courteous.

Which is what I would expect, given that my husband and I pay about $14K worth of premiums each year.

And it’s not as if we’re making over claims on our service, either.

With the exception of last year, when my husband had surgery for prostate cancer, and this year,with my broken arm and prolonged physical therapy saga, we don’t tend to put in a lot of health insurance claims. (Knock on wood.) We pretty much have our regular physicals, whatever tests they entail (which at our ages means an occasional colonoscopy, I’m afraid), flu shot, and a stray visit or two to the hospital walk in clinic. (A few weekends ago, I diagnosed myself with strep throat and wasn’t willing to wait an extra day to see my regular doctor.)

But, as I’ve mentioned, I’m now in a bit of a call and response regarding an issue around my broken arm.

Here’s the shape it’s taken:

As I’ve mentioned, everyone I’ve dealt with has been perfectly nice - or at least imperfectly nice, but this inquiring mind wants to know why:

This is, of course, a trivial matter (at least I think and hope it is), but it’s exemplary of a clumsy customer contact process that isn’t very well thought through. The inclusion of one simple sentence on the letter would have cleared things up completely, and saved me the trouble of a phone call. Not to mention having to address an envelope, given that I’d already recycled the envelope they sent along with their letter (since I had no clue what I was supposed to do with it).

Please, customer contact folks, walk and think through your processes. There may be some stray odd-ball glitches that could be easily remedied.

Grrrrrrrrr.


Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader. If you don't have a feed reader, you can always have these articles delivered to your email inbox every day. Click here to sign up.

Trackbacks & Pingbacks

No trackbacks/pingbacks yet.

Comments

I’m going through this with Comcast. I am having a technical non-critical glitch with my phone service (one feature not working correctly).

Here’s the funny thing: on their web site they gives a choice of phone, live chat, and email. After two tries with live chat, neither of which fixed the issue, i decided to send an email explaining everything in detail, so that they could research it and figure it out.

Here’s what I’ve found any time I’ve used their email contact option: it generates an email telling you to use the phone or live chat.

Why is it there? If for whatever reason, you don’t want to use email support, why put it there? It seems like no one has gone through the simple process of thinking “How will a customer want to contact us? How are we prepared to respond?”

It’s pretty poor not to be able to take support incidents by email - but it’s even worse to pretend you do and then close them by telling people to try again with another method. (I’m sure my email resulted in a case that’s marked ‘resolved’ in some database now.)

Sigh. Customer contact prevention.

Leave a comment

Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

(required)

(required)