Skip to main content

Know Thy Customer

We all get telemarketer calls, even if you think you've signed up for the National Do Not Call Registry. It's just a fact of life these days. Thus, you can approach them a number of different ways:

1) Simply hang up
2) Demand to be removed from the list then hang up
3) Make them hang up

I prefer #3, but that's not what this post is about. (ask me about my SkyMiles call, which is my personal favorite)

I got a call from a certain hotel chain today that I stayed at from time to time. The call started something like this: "Mr. Spendoli (telltale sign of a telemarketer when the last "ni" is left off). We're calling our preferred customers to let them in on a great deal we're having at our properties in Las Vegas and Orlando."

Before I go on, I need to note that this same hotel chain scuttled my rewards point account a couple months back because I did not stay there over the past 12 months or so. All of my accrued points went with it. No grace period, no offer to extend. Just plain old gone.

"Well," I replied, "do you completely delete the rewards accounts of all of your preferred members?" was my reply.

"Oh, I'm sorry to hear that happened. Let me ask you a question about your income: Do you make less than $50,000, between $50,000 and $75,000, etc." replied the agent.

I then took the next few minutes trying to explain to her that I was really not up for spending money with their company in light of how I was treated. She persisted, upping the ante to include New York and Hawaii. I held my ground and eventually got dumped off to a manager who did little more than give me their toll free number and offer his apologies. At least he stopped trying to sell me stuff.

Now, I don't really care about this incident or my rewards points, and the call gave me something to do while having lunch, but my point here is that companies should at least make a college try to weed out potentially unhappy people before calling them and trying to sell them more stuff. A simple query of their systems could have shown that I was a somewhat erratic customer over the past 10 years who simply had just let his account slip into the void. This could have been parlayed into an opportunity of sorts - perhaps an offer to reinstate my account and its previous balance for at least listening to their pitch or agreeing to one of their offers. The call would have gone in the entirely opposite direction.

After all, they were calling me on their terms; they could have at least chose the correct terms!

Comments

Unknown said…
Sure you know already Mogens Nørgaard as Oracle smart guy, but have a look to this page:

http://www.wedonotuse.com/

Genius!! ;-)

p.s.: I can assure that in danish is even more funny!
Scott said…
Yes, I have seen that before, and love it!

One of my other all-time favorite calls is when IBM called me at my desk at Oracle and tried to sell me database software.

I told them that we have some older IBM software that we used to run our robots, but things were not good, as one of the robots mauled "Earl", who ran the assembly line. She actually wanted to speak to "Earl", as he was the end-user, despite my pleas that he was in the hospital trying to recover form the robot attack.

Priceless!

- Scott -

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p