Sunday, April 13, 2008

Why I've Been Absent, Part Two

As I said at the end of "Why I've Been Absent, Part One" on February 9 of this year my life took an abrupt turn. My health began to fail me. It started with a cough. And went downhill from there...

I was down with the flu for ten days. Then I worked for a couple of days, and went down with a really bad cold. Which apparently turned into "walking pneumonia." The cherry on this little cake? I went functionally deaf for about two weeks. More time in bed. Working fewer hours when I did take a cab out. Ignoring the signs of impending disaster...

Because I don't have health insurance (a stupid situation, because I could have afforded it, as it would have cost less than my smoking habit, which by the way ended on February 9), I kept putting off seeing a doctor until March 13. At that time I was treated for the pneumonia. And told I had very high blood pressure. So high that I should have been immediately referred to an Emergency Room. But all the doctor said was, "You might want to have that looked at." No urgency was attached to the situation. I figured I'd save up some money and come back when I could afford to. Later on, a friend of mine told me I couldn't afford to wait, I needed to get treatment immediately, that the doctor should have insisted I go to an ER immediately.

But I waited. Five days later, suffering from extreme "blahs" and continual mild to moderate headaches, I finally decided to go to the local Emergency Room. Even at this point I dragged my feet. I worked most of a shift, dropped my cab off, got in my car, and went to Del Taco for dinner. Well, why not? It was "Taco Tuesday", three for a dollar. I ate half-a-dozen, and washed them down with a large Mountain Dew.

After dinner, my plan was to go home, and put together a few things I would want in case I was admitted. You know, things like books, toiletries, a few pairs of underwear and socks, pajamas, and my cellphone charger. Another plan thwarted
by the vagaries of life. Given the route I take home, my apartment is only about a quarter of a mile past the hospital. I never made it.

On the way home, I developed a very bad headache, shortness of breath, nausea and blurry vision. I decided to skip home, and go right to the ER. I guess I didn't say the right things to the receptionist, because I had to wait about forty-five minutes to see the triage nurse. I guess collapsing to my knees in front of her didn't convey any urgency. To be fair, since I couldn't hear what she was saying over the noise in the lobby (still functionally deaf at this point), I took the contact form from her to fill it out. She may have thought I went to my knees to be level with her desk, making it easier for me to fill out the form.

My friend Dean said that rather than standing up and going to a chair to wait, I should have just clutched my chest and laid down on the floor. He says this puts you to the head of the line every time. That's good to know, just for future reference. But I didn't think of doing something like that. So I took as seat, alternately crying, moaning and holding my head, praying I would hear my name called over the bedlam in the waiting room.

I found out later that a forty-five minute wait was relatively short. When I was called back by the nurse, the first thing she did was take my blood pressure. Which was so high that she went into overdrive. Within minutes I had an IV line in place, and serious blood pressure meds were being pumped into me.

Was I scared? Sure for about two minutes, which was how long it took for the nurse to get a syringe of morphine from the drug locker, hook it up to the IV, and squirt it into me. And about four seconds more for the morphine to take effect.

Once in my brain, the morphine instantly erased the pain, and filled me with an incredible sense of euphoria, well-being, and a complete disregard for the seriousness of my situation. I reverted to form and started telling taxi jokes, which were well received. Then I told a couple of morphine jokes which really cracked the nurses up. Actually, they're funny riddles. Here they are:

Question: What's the dumbest a nurse can ask? Answer: Would you like some morphine for the pain?

Question: What's the second dumbest question a nurse can ask? Answer: Would you like some more morphine?

This was my answer to the first question: "Sure would."

This was my answer to the second question: "Why wouldn't I?"

When asked the second question a second time, this is what I said: "You know, a good bartender doesn't ask questions. She just keeps the drinks coming."

Actually, I didn't say that out loud. But I was thinking it. She must have been a mind reader, 'cause she poured me another, and just kept them coming.

So, I was in the ER for a few hours while a bunch of tests were done. After a while a doctor came over to talk to me. "Cab Guy," he says, "In addition to severe hypertension, you are suffering from acute kidney failure. You're down to about 15% of normal renal function."

Which is devastating news. Or would have been if I wasn't juiced up on morphine. This is the beauty of morphine: when administered as a clinical dose calculated to ease pain, it leaves me lucid and completely aware of my situation. But calm. Very calm. It should have pained me to hear his words. But pain is pain, even if it's emotional. And morphine eases pain...

Looking him straight in the eye, I said, "Hmm... well I'm not surprised!" I could tell that this response was unexpected and shocking to him. The conversation continued:

"Doesn't this bother you?"

"I'm sure it will later, Doctor, after I sober up!"

"But you haven't been drinking!"

"And that's the beauty of morphine, Sir! After it wears off I'll worry about my condition. Right now I trust you'll fix me up."

Or words to that effect.

Shortly thereafter that I had my own private room. In the Intensive Care Unit. Where I laid flat on my back for the next five days. Mostly deaf. Hooked up to an IV tower with a continual infusion of blood pressure and kidney medications. And morphine, at least for the first day or two. But I didn't care, because I had constant care from a whole series of nurses. Who were all very friendly, competent and compassionate.

Who ran the gamut from very attractive to smokin' hot. Except for Steve, who I'm sure most women would have found to be attractive, but didn't do a thing for me. But he was a friendly guy who laughed at my jokes, so he was okay in my book.

Pretty nurses, a comfortable bed, and morphine. What more could a Cab Guy want?

To be continued...


I hope to see you out there on the road.

Sincerely,

The Cab Guy

Read More...

Saturday, April 12, 2008

Why I've Been Absent, Part One

Thank you to all my loyal reader and new visitors for your patience with my progress here at RRTT. Allow me to explain why I haven't been too active lately.

When I first started this blog, it was my goal to post a new entry at least three or four times a week, to give people a taste of what the cab business is like from my point of view. However, I generally had something to say almost every day, and had a lot of fun saying it. Having been in the business for almost ten years, I had a tremendous store of stories and anecdotes, and of course gained new stories all the time.

I don't know about you, but my experience has shown that no matter what my plans are, my life doesn't always follow my plan. Which is okay, because I've learned to enjoy the surprise twist and turns of the human experience. Around about the first of December, 2007 I have run into a whole series of twists and turns. Unfortunately most of them were of the negative variety. Which doesn't worry me, because I love a challenge.

The first challenge was financial, which in some of my earlier posts I discussed how things in the industry were affecting my bottom line, and therefore my wallet. The impact of this challenge on RRTT was I couldn't afford my Internet connection. I attempted to overcome this but writing some articles, copying them to a CD-ROM, and going to Kinko's/Fed-Ex, and renting a computer to upload the articles. This worked for a little while.

And then my computer decided to have a stoke, which I haven't been able to have repaired yet. It should be a simple fix, but alas, it is not. What happened is that there is a small battery in the computer, which powers the real time clock, and apparently the On/Off circuitry. Even when the computer, which is a notebook, has a full battery, or is plugged into AC, it won't start. It's a really good computer, which I got from Fry's Electronics, a reputable company. I've had it for several years, so the warranty has expired, which is unfortunate, because the whole battery issue is the result of what I think is a curious design flaw.

If you're thinking, "Hey Cab Guy, why don't you just replace the damn battery and be done with it, and start posting more stories?" I completely understand. I mean, it's a watch battery costing no more that $10.00 (American). It shouldn't be a problem. And it shouldn't be. But there's that curious design flaw...

You see the battery is easily accessed by lifting the keyboard up. However, rather than being connected to the computer through a socket, it is inside a shrink-wrapped envelope, with power leads that are then plugged into the motherboard. I actually like this design, for two reasons. First, were the battery to leak or corrode, the plastic envelope would protect the computer from damage. Second, because there is no socket, any battery of the proper voltage that would fit inside the computer could be utilized, making replacement fairly simple, even if a battery of the original size couldn't be found.

But here's the rub: the power leads plug into the motherboard deeper inside the chassis, and I haven't been able to figure out how to disassemble it to access the plug-in. I am hesitant to just cut the battery off the leads and splice a new one on, and I can afford to have a techie geek fix the problem.

So I haven't been able to do much writing, either for RRTT or www.DiscoBisquit.blogspot.com, which is very frustrating to me. I have things to say, and I want to say them, just for the satisfaction of knowing that some people want to hear me ramble.

So... just about the time that me finances started to improve, life to an abrupt turn...

To be continued...

I hope to see you out there on the road.

Sincerely,

The Cab Guy

Read More...

Saturday, December 8, 2007

Cab Cheats Part Two - Feeding

Supposedly, all cab drivers within a particular company are supposed to be working on an even playing field, with all having equal access to calls for service offered by the company. However, in some cases, in some companies, some drivers have a higher earning potential because of a scam known as "feeding."

Feeding is generally defined as a driver being given a call by a dispatcher (or other cab company employee) in a manner other than receiving it through normal methods. It may or not be the result of collusion between the driver and dispatcher, and may or may not result in the dispatcher being "paid off" by the benefiting driver. To understand how the feeding process works, it helps to understand how the "standard" dispatching system works.

At my old cab company, XYZ, and my new cab company, ABC, calls for service are dispatched by a computerized call-to-cab matching system. Each cab has a computer terminal in it, connected to the company's host computer through a radio-modem system. The cab terminal has a GPS antenna, to provide a real time position report to the host computer of where each cab is located. This information is used to determine which cab gets which of the calls that may be available.

Although XZY and ABC use the same basic equipment and software, there are some differences. XYZ uses GPS-based matching, where a call is matched to the closest cab; ABC uses Zone-based matching, where a call is matched to the first cab "up" in the zone the call originates in. Both systems have their advantages and disadvantages. I've worked under both systems, and don't really have a preference of one over the other.

In theory, after calls are entered into the computer system by customer service representatives, the host computer handles the actual dispatching of the calls. However, there is a human operator to oversee the system, and to communicate with the drivers regarding the status of the system.

For example, a call may come up in a zone that does not have any cabs in it, or in any adjacent zones. If the dispatcher left the system to it's own devices, the call might never get covered, because a cab might never match to it, or bid on it. At this point the dispatcher might "advertise" the call, to induce a cabbie to cover it.

For example, the dispatcher might send a fleet-wide message saying something like, "The call in zone 233 has wings!" meaning the party wants to go to the airport. This message should generate interest among the drivers, leading one or more of them to bid on the call, thereby maintaining an adequate level of customer service.

However, rather than sending a fleet-wide message, the dispatcher might send the same message to a select driver, allowing only that driver to have the extra information about the call. Moving one step further along, the dispatcher might just override the matching system, and send the call directly to a particular cab. This is the genesis of "feeding."

Even at this stage, the feeding might be relatively benign. The dispatcher may just be sending the message or call to the closest cab, not a co-conspirator; in a future similar circumstance, another cab may be closer, and it's driver will be favored. The motivation of the dispatcher in this type of case is not to favor a particular driver, or group of drivers, but to favor the customer, and get the call covered. Or, maybe, just get the call covered so he can go smoke a cigarette.

Even though a particular driver isn't being favored, this activity is usually frowned on by everyone involved, simply because it looks subversive. It's generally best to advertise calls, and let the cabbies, through the bidding process, cover the calls based on their own decisions.

The type of feeding that I described above was going on at XYZ company. I know it was happening, because over the period of time that I was there, I was sent calls directly from the dispatcher. I could tell this, because calls dispatched in this fashion were labeled as "Personal" on my cab terminal. The odd thing is, in many of these cases, I would have matched to the calls, if the dispatcher had allowed the computer to do it's job. And here's what confused me the most: while some of the calls were bigger than average, I was never approached by a dispatcher to pay a "commission" for the benefit of being sent the calls. What was the motivation here? I'll never know.

As far as I know, this type of feeding is not allowed at ABC company. Apparently, management thinks it best to avoid the appearance of evil, and just let the matching system do the job. If particular calls aren't getting covered, the dispatchers advertise them, and allow the drivers to decide if they want to go after any particular call. This may tend to degrade customer service in some outlying geographic areas, but does maintain the integrity of the entire system.

Meanwhile, back at XYZ, the feeding continues. Certain dispatchers have made it know that they can be "bought." I never had a dispatcher approach me to pay him a "commission" to get better calls, but I know it goes on. The driver manager himself confirmed this to me. He told me that the "fee" varied from dispatcher to dispatcher involved, from a few dollars a week, to a fixed percentage, like 10% of the value of all "fed" calls. According to this manager, whenever he caught a driver or dispatcher involved in feeding, he would fire them. It seems to me he couldn't fire them quick enough, because the feeding never stopped.

And it isn't just dispatchers who can feed calls. Customer service representatives who actually talk to the customers, and enter call data into the system, can also get into the act. One way a CSR can do this is to take the order from the customer, and appear to enter into the system. However, rather than submitting the data to the system, the CSR can send a cellular text message to a particular cabbie, detailing the call, and then delete the call from the system.

As a matter of fact, in this circumstance, the favored cabbie doesn't even have to work for XYZ. Because XYZ has so many "brands," most customers wouldn't even think to question the name on the side of the cab. They're just satisfied to get their cab. The company might never notice what's going on, because as long as the "call" is covered, the customer is never going to complain about what happened.

But, every once in a while, something does go wrong, and the customer calls back to ask, "Where's my cab?" But in these circumstances, it's just assumed that there was a "glitch" in the system. The customer is then told that no record of their call can be found, but that a cab would be sent to them as quickly as possible.

I know that this type of feeding was going on, because a former employee of the XYZ company, who was a CSR, saw it happen, and gave the details to another cabbie friend of mine. This person told my friend that she could not believe the number of times people would call for a cab to take them to Tucson, Las Vegas, or Los Angeles. Calls like this could be worth literally hundreds of dollars to the driver. She said that in almost all the of the cases that she witnessed, the call never got into the computer system. Someone, somewhere in the company, would "hijack" the calls, and send them to their favorite cabbies.

Not really fair is it? All drivers paying the same amount for the use of a cab, but some drivers, being singled out to get better calls, and make more money with less effort.

Well, I never thought that life was fair. Until I found out about the feeding, i just never realized how unfair it could be in the cab world. Guess that makes me kind of a naive sonuvabitch.

But an honest sonuvabitch.

The next installment of "Cab Cheats" will detail how "Ghosting" works.

I hope to see you out there on the road.

Sincerely,

The Cab Guy

Read More...