Wednesday, December 3, 2008

Finger Lickin' Good Stories

I'm not sure what the training program is for Kentucky Fried Chicken employees but they surely have room for improvement because their service here in NW Washington just plain sucks.

Or maybe they just don't like my family.

KFC Story #1:
My first indication of the problems at KFC came from my first visit to one of their restaurants here in Mt. Vernon. It was obviously an old building, in the traditional KFC style... it was dirty and gross. I'm pretty sure chickens wouldn't even eat there - that's how bad it was.

Luckilly, they demolished that building and built a new one down the street. Now KFC shares a restaurant with A&W (also owned by Yum! Brands).

We went back.
I spent some time browsing the KFC / A&W menu for something appetizing. Interesting... their 'combo meals' are assigned a code consisting of a letter and a number. Such as A1, A2, K1, K2... you get the point.
Hmmmmm... what to order.... hmmm... Oh, hey, that combo meal looks appetizing.

Employee: "Hi. Welcome to KFCAandW. CanItakeyourorderplease?"
Me: "Hi. Yes, I'll have the... uh (looks up at menu board to locate meal code)... oh, I'll have the K9 meal."
Me: (to myself, silently) Really... K9? Surely it doesn't mean anything. They couldn't at least skip K9 and go with K10? This may be a bad idea.

Anyway, the service continues to suck. Not just suck, but sucks bad. Really bad. Continuously. Consistently. On the bright side, it's not quite as bad as the Taco Bell/Pizza Hut combo down the street which never actually has any pizza for sale. Coincidently, those brands are also owned by Yum! Brands. Do you see the trend here?

So, back on topic here:
KFC Story #2
This past Saturday we traveled down to Grandpa Dave & Margie's house, which is quite a long drive. We decided to stop for lunch along the way. We stopped at, you guessed it, a KFC restaurant.

Like the old KFC in Mt. Vernon, this one is in another of those 'original' buildings and it shows its age. I'm going to pretend it passes the health code inspections because it's still open.

Today, we were Customer Number 1. The first in the door for the day. Hmmm... Red Flag.
The cashier was pleasant and took our order.
Our food came. It was close to being correct.
We ended up with five or six cups. There are only four of us.
Mikayla's mashed potatoes without gravy came with gravy.
Being Customer #1 apparantly has no relationship to being "The customer is #1" or even being "the #1 Customer".

We sat and ate.

After a while, one of the kids makes an interesting observation.
"Hey! We're the only one's here!".

Well, of course. We're Customer #1.

A moment later we realize that she is saying that the workers aren't even here. It's unusually quiet for a restaurant. Weird... but not weird for KFC, in my opinion.

Whatever.

A few minutes later a female employee comes out from the kitchen and starts cleaning the wall with some heavilly scented industrial cleaner. The scent (or fumes is more like it) drifts over to us and all three start complaining. Time to pack up and go.

We load up into the car and Tanya notices a Geo Metro parked behind the restaurant with the driver's window part way down.

Tanya: "Hey, I found all the rest of the workers!"
Eric: "Where are they?"
Tanya points in the direction of the Geo where all the workers are stuffed inside the vehicle.
Smoking.

It may not sound funny, but it was.

I guess you had to be there.

Of course, after the discovery I had to roll down the window to get a blog photo, just to share with everyone. Unfortunately you can't really see the people in there.


KFC Story #3
This isn't really about KFC or their service, but I just need to remind everyone that one day Tanya mistakenly thought the drive through exit was the main road, drove down it the wrong direction and then had to exit the whole thing in reverse. It's true... and we like to talk about it often.

I don't have any pictures of that event, but I'm sure that one day it will surface on youtube.com or some 'craziest driver video' show on TLC after the survelliance videos are released.

~E

No comments:

Post a Comment