Forum Moderators: phranque

Message Too Old, No Replies

Best practices for registration messages?

         

blang

6:25 pm on Feb 19, 2010 (gmt 0)

10+ Year Member



I haven't really thought about this much before, but I have a specific application I'm building where I want to provide the customer with a brief note (that they can agree to), with the standard boilerplate, e.g. "we are collecting your information for internal use, we will not sell it to spammers", etc.

I should mention, we basically want to pull in the customer's email, name, phone (optional), zip and field for internal marketing purposes. No truly personal information will be collected. Technically the email is all we really need but we want to get an idea of the our customer demographics and send emails to specific targeted markets.

Is there a standard out there I can go by? Do most other sites just make it up as they go? I've clicked "I agree" on countless forum entry pages with only a glance at what it said, and most of them seem to be copied-and-pasted or rehashed from other forums or other websites.

A related question: by saying "I agree", what sort of legally binding agreement have you and your customer made at that point? Just your word?

maximillianos

7:30 pm on Feb 19, 2010 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



If you are going to be e-mail marketing to your users, I would make sure they specifically opt-in to such features (with a checkbox or something). Otherwise, if you bury it in your terms and conditions, your e-mails will most likely start to get marked as spam. And this of course can hurt you in the long run with credibility from an ISP's perspective.

blang

7:51 pm on Feb 19, 2010 (gmt 0)

10+ Year Member



The application will
1) request the user sign up for our email newsletters, and
2) provide a registration-verification email that will do the following:
  • Authenticate the registration against a key in the db.
  • Provide a way for them to unsubscribe right there and then, or
  • Confirm that they are in fact "opting-in" to the newsletter
  • Provide a permanent link for them to unsubscribe


Unless I'm mistaken, two layers (voluntary subscription and opt-in checkbox) are quite sufficient to ward against issues down the road.

So that's basically my point, that they will be able to "opt-in". I'm not trying to hide anything. I simply want to know if there is a standard out there to follow with this sort of "contract".