Kmart pharmacy customer (dis)service

-
First off, let me qualify this post by saying I am a former employee of Sears Holdings Corporation which is the parent company for Kmart. As such, I happen to still use their insurance through COBRA and because of the plan offered, my insurance only allows me to use Kmart (and VERY few other) pharmacies.

Last night I was supposed to go to Kmart and refill a prescription for my son. As circumstances would have it, I forgot so ultimately, I probably contributed to the stress levels associated with this situation. We happened to have one dose left of his medication so we assumed it wouldn't be a big deal to pick it up in the morning. My wife thought she could just run to the pharmacy this morning and get a refill.

This morning, I happened to be attending a software development conference in Chicago (coincidentally with at least one, if not more than one SHC associate) and started receiving frantic calls from my wife. She went to TWO different Kmart pharmacies (10 miles apart) and they didn't have the prescription. She was assured, however, she could drive just another 5 miles away and get it filled.

Because she had other things she had to get done, she went to another pharmacy right next door (Walgreens ) and was going to pay a LOT of money ($150) to get the scrip filled. After the third call, I told her to simply lay down the cash and we'll worry about the cost later, after all, our time and our son's health was too valuable to be driving all over Northwest Illinois hoping that someone had what we were looking for. It turns out, she got the idea to call our pediatrician and they happened to have had a some samples that they gave us until Kmart would be able to fill the prescription, but this brings me to my point:

Kmart pharmacy, you get a big fat "F" in customer service. Honestly, I really like the people working there as individuals, they're really friendly and seem to be nice people

BUT...

I happen to know that the store in Rockford is affiliated with mygopher.com. This should have been a home-run make my wife happy win-win-win situation for all involved. If the store in Rockford had proposed that my wife pay an extra $10 to have the prescription delivered to our doorstep she would have been jumping up and down in happiness. Instead she was frustrated, mad, and disgusted with the entire situation.

Some alternative scenarios proposed:

#2 Go get the scrip from Walgreens, then figure out how to get reimbursed...
#3 Anything else? Really, do you need US to come up with better solutions? I'm the customer here, I'm looking for solutions, NOT excuses...

Comments

Post a Comment

Popular posts from this blog

Please use ANSI-92 SQL Join Syntax

-
Image
Way back in 1992, a standard was published for SQL. In it, the syntax for specifying joins in SQL Database was finally standardized. This was a good thing because (for folks who've been doing this a while), trying to decode the vagaries of how various Databases handled outer joins could drive you bonkers yielding different results depending on the parse order of things in the from and where clauses. Unfortunately, some DBMS vendors took a while to adopt this standard (Oracle didn't support it until 2001), but at this point if you're using a major RDBMS and NOT using it, you're probably mired in a tradition or habit that bears changing. As an example of what I'm describing, here are some examples of what I mean. Old School (no standard syntax + implementation and evaluation of predicates varied by vendor [and query]): select * from customer, order where customer.customer = order.customerid ANSI way (agreed to standard, predicate evaluation has some rules
Read more

the myth of asynchronous JDBC

-
Image
I keep seeing people (especially in the scala/typesafe world) posting about async jdbc libraries. STOP IT! Under the current APIs, async JDBC belongs in a realm with Unicorns, Tiger Squirrels, and 8' spiders. While you might be able to move the blocking operations and queue requests and keep your "main" worker threads from blocking, jdbc is synchronous. At some point, somewhere, there's going to be a thread blocking waiting for a response. It's frustrating to see so many folks hyping this and muddying the waters. Unless you write your own client for a dbms and have a dbms that can multiplex calls over a single connection (or using some other strategy to enable this capability) db access is going to block. It's not impossible to make the calls completely async, but nobody's built it yet. Yes, I know ajdbc is taking a stab at this capability, but even IT uses a thread pool for the blocking calls (be default). Someday we'll have async databa
Read more

The difference between Scalability, Performance, Efficiency, and Concurrency explained

-
I thought I'd give some explanation of the difference between scalability, performance, Efficiency, and concurrency. To make things more accessible (and because I'm watching a cooking show on TV) I'm going to use a baking metaphor to help explain the differences. In our case, the system in question is baking cookies for consumers. Scalability, is how well something responds to adding more resources. If we can double our capacity by doubling the number of resources, we've got linear scalability. In our baking example, if we add more ingredients, we can scale to a larger number of cookies. To contrast with our other metrics, this doesn't actually increase the performance of creating a single cookie (they still take 10 minutes to bake), and the efficiency is the same (we just have more capacity). We also cannot bake more cookies in a fixed time period, but over a larger time period we can produce more cookies. Performance is how fast something can get done, u
Read more