Big data? What about the small stuff?
In preparing for an upcoming business trip, I decided to rent a car on Enterprise.com. I could have sworn that I had registered on the site at some point, but I couldn't find my user name and password. Call it a senior moment.
I can't imagine that this is an uncommon occurrence on most popular e-commerce sites. I don't have a photographic memory, so I filled out the password reset form. What followed, however, was nothing less than shocking, at least to me:
I couldn't believe my eyes:
If you entered a valid email address?
How do you not know this?
I have a really simple question for Enterprise's CXOs: How does your company not know whether I entered an email address that exists in its CRM system? I don't know which application you use, but it's logical to surmise that email address is a required field – or at least it should be. It is 2014, after all, right?
I no longer code very much, but I'm pretty sure that building in logic here can't be terribly difficult. I would suspect that the business rule/code would look something like this:
If [ENTRY] IS IN CUSTOMER.EMAIL_ADRESS THEN "YES" ELSE "We're sorry. We cannot find this email address in our system. Would you like to try another or register here <insert link>?"
Yet, Enterprise gave me a conditional statement on a data element as basic as my email address.
It never ceases to amaze me. Big data is here. There's no doubt about that. Still, there are plenty of large and ostensibly successful organizations that don't manage their small data terribly well.
Messages like this may very well not resonate with the vast majority of the public. After all, most consumers don't think about things like master data management and referential integrity. To those in the know, though, this is a clear signal that the company can use its data to provide for a better customer experience.
What say you?
While it's definitely possible their coding/data searching is not up to snuff (who hasn't had a problem with a rent-a-car agency at some point or another?), this could also be a purposeful implementation to ensure that anyone who is just phishing, doesn't get confirmation on whether an e-mail address does in fact have an account.
Perhaps they're trying to cover their bases, in case the email address is in their system, that that email address is no longer valid these days - in that case, the mail can't successfully be sent to that address(?)
Or, perhaps this is a way they prevent hackers from trying to "guess" which email addresses are in the system, by not giving them an easy way to verify whether it's in the system or not(?)
These are all possibilities. I just wonder why simple contact forms include authentication and captcha. Those seem like effective ways to combat phishing and spam.
Pingback: Phil Simon: 3 Things that Marketers Can Learn from Message Not Received