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 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


  • Fixing discussion lists to work with new Yahoo policy

    Al has some really good advice on how to fix discussion lists to work with the new Yahoo policy. One thing I would add is the suggestion to actually check dmarc records before assuming policy. This will not only mean you're not having to rewrite things that don't need to be rewritten, but it will also mean you won't be caught flat footed if (when?) other free mail providers start publishing p=reject.No Comments


  • Sendgrid's open letter to Gmail

    Paul Kincaid-Smith wrote an open letter to Gmail about their experiences with the Gmail FBL and how the data from Gmail helped Sendgrid find problem customers. I know a lot of folks are frustrated with Gmail not returning more than statistics, but there is a place for this type of feedback within a comprehensive compliance desk.No Comments


Archives