Please confirm your email address
bvckup.tumblr.com
bvckup.tumblr.com
"Use a verb or verb phrase for the title of a push button. The title you create should describe the action the button performs—Save, Close, Print, Delete, Change Password, and so on."
http://developer.apple.com/library/mac/#documentation/UserEx...
The difference between "Email confirmation" and "Please confirm your email" is like that between "Ok" and "Save."
Imagine yourself as a user of this service. You sign up, get the "email confirmation", think everything is good. A day later you notice that it isn't working, check up, actually read the email and click the link.
Now you want to report a bug. What do you say? How do you explain that you got it to work, but it could have worked better? When there's a large helpdesk, this kind of feedback is nearly impossible to give in any meaningful way. Even if you could speak to the coders concerned, often it's hard to get them to think in a different way and see the problem.
So it's obvious but it's hard.
And some things are obvious to you and amazing to others http://sivers.org/obvious
Anyone else cares to share their numbers?
Currently I use:
====
Please open this link to confirm your email:
http://www.postjobfree.com/a.aspx?k=c3d26a0fc5d145cf88898a92...
This link will expire on: 8/19/2011 10:29:11 PM EST.
====
Thanks for the tip about subject for email confirmation!
In the past I was using "Link to confirm your PostJobFree email", but your new version with clear call to action ("Please confirm your email address") should perform better.
If you write the date as "August 8, 2011" it should be trivial to parse for everyone. (Except for people using different calendars)
Why not just say "The link is valid until August 19", and then let it expire some time after all the world has moved on to the 20th? (No MM/DD or DD/MM. Please.)
I personally prefer the old fashioned "Just reply to this mail" method, which many mailing lists use for confirmation, to opening a browser window - in the worst case I have to wait for my browser to launch, too - and I'm going to close that window immediately anyway so I can get back to what I was actually doing, so I just think "I'll get to that later", but then I don't, and when I remember [did I click that link? I'm pretty sure I did, so there's probably a bug in their list somewhere and I shall ignore them henceforth], the link has probably expired anyway [can't be bothered checking what time and day it is in "EST" (Estonia?)] so I'll just browse around for funny kittens instead. And all of that just because somebody wanted me to click on a link. They're sooo cute!
Maybe it's just that the email way is too rarely used, but it makes me pause. I prefer a link, that's much more of a no-brainer.
But the suggestions overall are valid - thanks!
What's better:
1) "The link will expire 2011 August 19"
2) "The link is valid until 2011 August 19"
3) "The link is valid for one day until 2011 August 19"?
Personally, I would say "August 19th", not "19".
(I'm a native English speaker, not from the US where "through" seems more common)
If the duration is less than three months, the year can be inferred from the date of the email.
This gives people a sense of urgency, but doesn't discourage them from trying the link if they're a little late. "Through" is (to my ears) an Americanism.
Next Step: Confirm your email address
Thinking along the lines of how "Follow me on Twitter" tests better than "If you liked this blog entry, please follow me on Twitter." Just give people a direct order. "Next step" might make it clearer that they're not yet finished with the process?
I think rewarding the user for singing up would be an interesting incentive. "Click the link to receive your first email".
Having said that, unlike registration confirmations, where I would like to get back out of my inbox to your site. For mailing lists, I don't need to go back to your site, really. I'd much rather stay in my inbox if that's ok. I'd quite like to see an A/B test between the usual method and a request for people reply to the email, rather than click a link. "Reply to this email to start receiving updates": simple order, direct resulting action. It also makes it sound like a similar action will be required to stop receiving updates.
Wonder how many people are using web-based mail clients and whether that would impact a preference to reply or click?
I send the confirmation emails through Google's email servers (Google Apps).
update: If I break it down by domain, I see gmail->80%, yahoo->70%, and hotmail->66%.
Good point regarding the sender name. I will play with it once HN wave subsides.
It gave people an incentive to verify their email!
Check out blurts.com and qbix.com for examples
Little details can make such a big difference.
And the email I send has the subject: "Please confirm your subscription"
Between the two, the message is fairly clear. Yet, I still receive emails from novice users once in a while, who aren't familiar with the concept of "confirming" a subscription. Usability isn't easy.
That is, downsized screenshot, with graphics drawn on top. I think the original looks too much like a real window.
Maybe even have a popup that triggers if that link is clicked that says something like: "Sorry, this is just a screenshot. Please check your email inbox for this message"
Can't rate them high enough.
The button says "Post Analytics". That makes me think "send analytic to SEOmoz". But what they really mean is "view this blog post's analytics".
Do we even really need to confirm email addresses?
Admittedly, it might be someone ELSE'S email address, but they could manually unsubscribe from your mailing list later.
That's half the point of verifying e-mail addresses. Doing this is likely to engender significant ill-will in anyone who is an unintended recipient of your e-mails.
---
You are receiving this email because someone (presumably you)
subscribed $(email) to the $(maillist-name). Subscription
request was received from a network address of $(ip) on $(date).
If you did not request this subscription, or would like to be
removed from the maillist for another reason, visit this link
to unsubscribe - $(link).
A bit of a mouthful, but essentially this simply piggy-backs the confirmation request on an actual mailing list message. Thoughts?1) Enter email on web page.
2) Open confirmation link in email inbox.
If you skip second step - there is a risk that email ends up in spam folder and is constantly delivered there. Another risk - user did not really request your subscription. That would often result in your emails being marked as spam.
1. Before the near-universal requirement for confirmed opt in, it was a reasonably common attack/prank to sign up someone else for tons of lists, causing them to receive unmanageable amounts of email per day. Alternatively, sign them up for lists they'd consider offensive, or that'd get them in trouble at work. Confirmed opt-in stopped this attack.
2. We've (computer geeks, security experts, etc.) spent years trying to teach users that no, they really shouldn't click on that link in an unexpected email, even if it promises cute kittens. That continues to be a problem. I don't know how an expert, much less random Joe, could tell a real "click here to unsubscribe" link from a fake one, if you have no idea who the sender is. Researching if its a legitimate unsubscribe link—and not a link that'll confirm to a spammer that you're reading his email, or pull up a page full of the latest browser or Flash exploits, makes it far more expensive for the random person to handle an opt-out than it is for the person who wants the subscription to handle a confirm.
Confirm emails are easy for a random person to handle: just ignore them. You won't receive any more emails if you take no action.
3. Not all email addresses are nearly-free to send to. Well, they're all nearly free for the sender, but not the recipient. Some email addresses cost 20¢ per message (e.g., SMS gateway). Some email addresses page people, waking them at night. These addresses aren't always very different from other people's addresses (I've personally had misdirected mail to both types). Someone can also do this as an attack. Sending a single message is bad enough, but is the minimal harm you can do; but imagine if anyone could subscribe your text message address or pager number to linux-kernel.
4. Realistically, while some mailing lists are very easy to get off of (e.g., development list for a random open source project), many commercial lists aren't. I've had people give my email address (assumably by mistake) to the College Board on their PSAT (hundreds of emails per month, many from different senders, no way at all to stop them); sign me up for an Xbox account (took me at least half an hour to figure out how to stop that—-apparently you're supposed to phone Microsoft; thankfully I finally found another way); sign me up for various things at EA (nothing on their web site, contacting support was absolutely useless); etc.
5. Your ISP probably has policies against sending unsolicited bulk and/or commercial email. If you aren't confirming your subscriptions, you can expect your ISP to receive complaints, and you are probably in violation of their TOS.
Not sure how much this still happens, with spam being so much cheaper to send with botnets.
Secondly, if I can sign someone else up without their knowledge and get you to send then unsolicited mail, you're risking legal problems.
I'm a tech writer, and I hope that not too much self-advertising for my first post here.