It is primarily benefical for the company
I start with companies that have a large community, for example amazon. They have 244 million users and therefore many e-mails to send and to reply to. Most of the sent e-mails probably are automatically generated shipping confirmations telling you not to reply, because this address was just created for sending e-...
There are already good answers on optimizing the existing success page. I want to add an alternative.
Skip the success page and log the user in immediately. There are a lot of examples of web applications, which allow access before verifying your email address. The user may browse the content, configure his profile, ... but public content ...
Quirky employs a variation of Option #1. Instead of asking to unsubscribe, they tell you that they've unsubscribed you, giving you an option (and incentive) to re-subscribe.
I was pretty impressed with this strategy. I didn't resubscribe, but I appreciated them taking me off their list based on my viewing habits.
I would recommend against an auto-correct as domain name extensions are about to change drastically, to the point where an email ending with "sitename.anything" will be valid.
Consider an inline check, which means it doesn't cause the frustration of the usual
ENTRY > SUBMIT > ERROR MESSAGE > RE-ENTRY > SUBMIT
[!] Did you mean .com?
You can't send "forgotten password" links to a single account if you have the same e-mail address, unless the user specifies a unique username. But what happens if the user forgets the username as well? Then you need to reset password on all accounts associated with the e-mail address.
Emails were never intended as a form of chat type messaging. Remember that they are electronic versions of mail, so trying to modify them to be something they weren't designed for is a mistake.
As to the reasons why we write the subject line first:
The subject line is part of the header of an email (see the original RFC822 and the newer RFC5322), and ...
Both seem perfectly fine to me but as far as preference goes, I'd say go with the second option.
For any questions, please consult our Help Desk – or reply to this email.
The reason being that it eradicates confusion. If you write the email address, a lot of people would think it is different from the one you sent and would write a new email to reply. ...
This one is quite easy, you simply can't.
If you would use an address on an emailing list where the recipient has opt-out you violate the 6'th requirement of the CAN-SPAM Act.
Doing so is violating the law and will enable the recipient to sue your company:
Each separate email in violation of the law is subject to penalties of
up to $16,000, and more ...
I would personally recommend the equivalent of firstname.lastname@example.org, which is the format I use. I agree with your assessment — to me, emails like email@example.com and firstname.lastname@example.org seem a bit too playful or informal. I like to use one email address across all the services I use, so something that is completely neutral is key. Hard to get more neutral than ...
Does the user need to know the specifics of what's happening?
Resubscribe or Subscribe would seem to be more consistent for the user as their perspective would be more with regard to whether or not they are receiving the notifications and not so much the how.
There are no security problems. If two people share an email account, and one of them has an account on your site, either of them can reset the password on the account (since they both have access to the place where the "forgot username" and "forgot password" emails get sent). Both people have the ability to take control of the account, and that's ...
The options to choose
Option 4: continue to send the emails
If people don't want your emails they will tell you
Option 5: imply everyones getting the email
This is a little dishonest but... well, no judgments. Just send them an email; seemingly out of the blue asking if they want to continue with your emails. Something along the lines of
"We want ...
Relax. I get many emails a day from services that I am interested in, but the timing just isn't right (Meetup, Groupon, mailing lists). If I don't want them, I know how to unsubscribe, but usually seeing the first line or two without opening them is all I need. I'd be annoyed if you chastised me for not opening them.
Maybe a more useful strategy is--if ...
It's better to use a special one-time login url.
Reasoning: You want to make the process as easy as possible to have the lowest drop-off rate. Sending someone a temporary password requires them to either retype a password that they haven't chosen, or copy and paste it. It also provides no additional security benefits.
We have spent the last months battling with what to do with email confirmation/verification - prior the user had to give all their details at sign up (way too many actually!) but couldn't actually login until they had confirmed their email address by clicking a link.
We stood back and looked at why we did this - three reasons really, one being we wanted ...
Personally, I find this really annoying and really bad UX.
There is a large music equipment online store in Europe, which does it differently, and I always enjoy interacting with them. When you reply to an invoice, you do not get just email@example.com or firstname.lastname@example.org, no, you actually get a direct email to the customer support ...
Sadly there is no standard for the name of such an email - all your suggestions are used. But consider the following:
Verification Email - used when you can still access services, but need to verify your email in the meantime.
Activation Email - used when services (account) are not accessible until email activation takes place. You can argue that there is ...
There isn't any major security reason behind them expiring. The main reason that this is done is to be able to clean up the database of old unused verification information.
From a UX side, some people argue that having a shorter verification time encourages people to verify sooner rather than later, but I haven't seen any evidence supporting that. It does ...
The second time you are asked to enter your email you may notice it says "confirmation." That's all it is really, just confirmation that you are entering the correct email.
In some instances, asking for an email twice is crucial. Consider signing up for an email list for example. If the user makes a mistake and enters their email incorrectly, they may leave ...
It depends on the app. You need to establish whether messaging is an integral part of the workflow for your users.
Social platforms and collaboration apps often include an internal messaging mechanism. Other types of apps - not so much.
But don't get hung up on the term "email" itself, because it will restrict your thinking to the conventional email - with ...
Do not insert hyphens, not even soft hyphens ­ (which only appear if the browser forces a line break). This is because the user might hand-write it or read-dictate it to someone else with the hyphen. Which would be inaccurate and bad.
You could however use the <wbr> element to indicate an optional word break opportunity. This will tell the ...
The most common way is to:
Ask the user to enter her password before changing e-mail (even if she is currently logged in): this will help to avoid stealing of the account if user has forgotten to logout or somebody simply got user's cookies or something like this.
Send an activation link to the new address and don't switch e-mails until the new one will be ...
It's the same as the floppy disk icon: if there was a natural successor, you would already know what it was. If you don't, it means that no natural successor has emerged. And if one hasn't, frankly, who cares?
Essentially, what it comes down to... is are you dealing with USERS or PEOPLE on your site.
Most companies prefer to have a relationship with a person. Exceptions would be reddit and other sites which are designed with anonymity in mind and are almost purely online communities.
A verified email is a verified person behind the email. Prevents some simple ...
First, I'd suggest reading my answer from a few years ago which explains the importance of the wording.
Secondly, if you can eliminate the delay that'd be ideal. Even with changing the instructions, you're still going to get some complaints with a 5 minute delay.
But assuming the delay is here to stay, here's how I'd write it...
I would say that (option 2) sending a verification code is more secure as users will have to input their verification code before the verification is complete, particularly if this is part of login ( 2 step verification).
This being said if the ...
As someone working in customer support, which of the following would make it easier for you to decide which mails you answer, which you forward to the technical staff, and which ones you ignore?
If you got these e-mails to your contact address:
Please implement feature X, we really need it!
I bought product Y from you but it doesn't work
Wow i liked the ...