BLOG

Verifying addresses after POS collection

Collecting email addresses at point of sale is a challenge. Some stores collect the addresses electronically, where the clerk or the customer types addresses directly into the register. Smaller stores, however, typically collect addresses on a sheet of paper at the cash register. Eventually someone takes the list and types it into whatever contact management system the store maintains.

There are all sorts of errors that can happen when someone types in an address, but those errors are only compounded when the addresses are written on a sheet of paper for later transcription. Not all of us have perfect, copperplate handwriting and many of us have barely legible scribbles. In one case I had a sender read the tag in my email address wrong causing all their mail to me to bounce.

One person found an interesting solution to the problem of illegible addresses: using Facebook’s lookup to clarify illegible addresses.

To figure out what the addresses should have read, we turned to Facebook which allows you to search for anybody by the email address(es) they have registered (unless they have tweaked some privacy settings). We just kept trying to enter each address we weren’t sure about, permuting a few of the difficult to read letters each time, until Facebook returned a match.aprèsSci

Standard caveats about how the addresses verified as valid addresses may not be the addresses belonging to the store customers, but it is an interesting way to resolve the problem.

3 comments

  1. Chris T. says

    That’s a great idea, just as long as the sender is an honest Joe and is not tempted to scrape addresses from FB. We deal with a number of small businesses that get heaps of bounces due to illegible handwriting. Good article, thanks.

  2. Neal says

    Integrating a email validation API like on from StrikeIron at the point of capture (POS in this case) improves data quality and email verification.

  3. Catherine Jefferson says

    I’ve heard some complaints about Strikeiron marketing to businesses that ran into trouble with Spamhaus, so I’d be cautious where they are concerned. However, the concept of email verification itself is I think a good one. With all the problems caused by typos at points-of-sale and in web forms, I can’t see any objections whatsoever to software that spots likely typos and prompts the user for corrections. Ditto software that spots likely accumulated typos on lists and puts them on a list for a COI loop before continuing to email them.

Comment:

Your email address will not be published. Required fields are marked *

  • AOL compromise

    Lots of reports today of a security problem at AOL where accounts are sending spam, or are being spoofed in spam runs or something. Details are hazy, but there seems to be quite a bit of noise surrounding this incident. AOL hasn't provided any information as of yet as to what is going on.4 Comments


  • ReturnPath on DMARC+Yahoo

    Over at ReturnPath Christine has an excellent non-technical summary of the DMARC+Yahoo situation, along with some solid recommendations for what actions you might take to avoid the operational problems it can cause.No Comments


  • AOL problems

    Lots of people are reporting ongoing (RTR:GE) messages from AOL today.  This indicates the AOL mail servers are having problems and can't accept mail. This has nothing to do with spam, filtering or malicious email. This is simply their servers aren't functioning as well as they should be and so AOL can't accept all the mail thrown at them. These types of blocks resolve themselves. 1 Comment


Archives