Closed Bug 984389 Opened 11 years ago Closed 11 years ago

Streamline account activation email

Categories

(support.mozilla.org :: Knowledge Base Software, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED
2014Q2

People

(Reporter: atopal, Assigned: rehandalal+mozilla)

References

Details

(Whiteboard: u=contributor c=wiki p=1 s=2014.7)

The account activation email can be improved for users and contributors. Specifically, for users and contributors: * Make text shorter * Add big blue button if possible * for contributors: Customize account verification links, so people are forwarded to the right page after signing up on the account verification page.
Re where to send contributors after signing up: * Redirect forum contributors directly to support forum after signing up * Redirect KB editors directly to the article after signing up * Redirect L10n contributors to "localize Firefox" help article * Redirect AoA contributors to Army of Awesome main page
(In reply to Kadir Topal [:atopal] from comment #1) > * Redirect KB editors directly to the article after signing up To what article?
See Comment 2. Also, this isn't trivial because we don't really track what they were interested in other than they want to become a contributor. But I do want to create that mini survey form to go with the registration so we can track what contributors are interested in, etc. I'll file that bug shortly.
Flags: needinfo?(a.topal)
Sorry, the KB article is: https://support.mozilla.org/en-US/kb/improve-knowledge-base We will know what they are interested in when we implement bug 984377 But a survey is coming for the first page of the get involved flow. To see what percentage of people are false positives = landed on the get-involved page, but was not interested in becoming a contributor.
Flags: needinfo?(a.topal)
(In reply to Kadir Topal [:atopal] from comment #4) > We will know what they are interested in when we implement bug 984377 Not really. We need to start tracking it in the backend is what I meant.
Right, I meant people will tell us what they are interested in, right now there is no way to do even that. Not sure if you want to file a specific bug for the tracking.
(In reply to Kadir Topal [:atopal] from comment #0) > * for contributors: > Customize account verification links, so people are forwarded to the right > page after signing up on the account verification page. Right now, the account verification page looks like this: http://cl.ly/image/0J2g2x1b383m That is, the contributor needs to actually sign in after verifying their account. So we can't really send them to any of those pages. Are you proposing that we send them to one of those four other pages after they sign in? It might be worth splitting this into two bugs: * the email UI improvements * the behavior after account verification and sign int
Flags: needinfo?(a.topal)
Yeah, there might actually be several bugs here.
Flags: needinfo?(a.topal)
2-3pts. Going with 3 for now.
Whiteboard: u=contributor c=wiki p= s=2014.6 → u=contributor c=wiki p=3 s=2014.6
This missed the sprint. Moving to next.
Whiteboard: u=contributor c=wiki p=3 s=2014.6 → u=contributor c=wiki p=3 s=2014.7
Q1 is over. Bring it on, Q2!
Target Milestone: 2014Q1 → 2014Q2
Kadir, you mentioned the text for the email is in some etherpad. Can you provide it? We are only doing the email changes in this bug. Then we will file a bug for * the behavior after account verification and sign in
Assignee: bram → rdalal
Flags: needinfo?(a.topal)
Also, this is probably now 1pt.
Whiteboard: u=contributor c=wiki p=3 s=2014.7 → u=contributor c=wiki p=1 s=2014.7
The account activation email text that I had proposed went a little something like this: Hi [username], Thanks for joining Mozilla Support! To complete registration, you need to verify your email address. [Click here to verify your email address] <-- big button If the link above doesn’t work, click here: [Activation URL in <a> or plaintext] Once you’ve clicked on the link, you can throw away this email. Thanks, The Mozilla Support team
Flags: needinfo?(a.topal)
I wanted to point out that when a user is registering through AAQ, the email is slightly different. Was that considered? Should we make them the same. See the email here: https://github.com/mozilla/kitsune/blob/master/kitsune/questions/templates/questions/email/confirm_question.html {% extends 'email/base.html' %} {% block content %} <p><strong>{{ _('Please confirm your Firefox Help question') }}</strong></p> <p>{{ _('Hi {username},')|f(username=username) }}</p> <p> {% trans %} Before your Firefox Help question ({{ email_data }}) can be seen by our support community, you need to confirm the account you just created by clicking on the link below: {% endtrans %} </p> <p> <a href="https://{{ domain }}{{ activate_url }}?reg=aaq">https://{{ domain }}{{ activate_url }}?reg=aaq</a> </p> <p> {% trans %} If you did not ask a question or changed your mind, simply delete or ignore this email; you will not receive any more email from us. {% endtrans %} </p> <p> {% trans %} Thanks again for asking the question -- we're sorry you're having trouble with Firefox, but our community of volunteers is looking forward to helping you get it resolved as quickly as possible. {% endtrans %} </p> <p> {% trans %} As you may know, Firefox Support (like all of Mozilla) is community powered -- help is provided by users like you! Want to take part? <a href="https://{{ domain }}/questions?filter=unsolved">Browse other users' questions</a> -- you might just make someone's day! {% endtrans %} </p> {% endblock %} {% block footer %}{% endblock %}
Flags: needinfo?(bram)
Flags: needinfo?(a.topal)
In my opinion, I think that the new AAQ user verification email could also be shortened (ie. make it the same text). It achieves the objective that we want the most, which is getting users to click “Verify”, without clogging it with more links that will actually need registration. Keep in mind that the reader of the AAQ verification email wants to see their questions posted, not to contribute. S/he might contribute later, but right at the moment, the focus is on getting her/his question posted and answered. To me, putting a link to “Browser other users’ questions” seems a little bit like putting the cart before the horse. So why not take everything out and just focus on the subject at hand, which is verification? That’s what I’m thinking. What about you, Kadir?
Flags: needinfo?(bram)
That makes a lot of sense, Bram! Let's use this for both cases. Ibai, let us know if you think differently.
Flags: needinfo?(a.topal) → needinfo?(ibai)
+1 to Bram's suggestion. We need to keep it simple and frictionless.
Flags: needinfo?(ibai)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.