Closed Bug 1485098 Opened 8 years ago Closed 7 years ago

Sending out a Newsletter for Common Voice

Categories

(Marketing :: Email, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lsaunders, Assigned: bhaack)

Details

Attachments

(2 files)

Hello, We would like to send out this letter to people from the common voice email list https://docs.google.com/document/d/1EB4EnQz1SIcqH9rCmKbLUYLDko-A19dZuc_lTf4uXLU/edit We will need help setting up a template. Please let me know what further information you need. Thanks! Lindsay
Thanks for filing, Lindsay! I'm so excited to hear that you're ready to engage with your audience :) Per our email thread, your goal is to send this email on Sept 4th, but could delay pending the new homepage launch. You have been trained on our email platform before, so you just need to know where to create the content and how to send it. Given this, and that you're out of the office for next week's usual LCM intake mtg, we'll use this bug to sync async. Action items: * Lindsay to code email Check out this copied version of your welcome email to start coding: My Emails > Common Voice > EXAMPLE COPY ME - MoCo_GLOBAL_INVO_2018_NUR_HTML_Common-Voice-Welcome_ALL_EN_EML_ Please remember to use the naming conventions: https://docs.google.com/spreadsheets/d/11rvrVdF4fj5GaKOvlnLcNjnWB7U7yKV_MHmlBwRE-WA/edit#gid=2060558790 And remember our how-to doc: https://docs.google.com/document/d/17TWKutMwke3K4sdJryMr23BVYAvWIK9CjaK34I9H42s/edit# * LCM to setup audience (SFDC Report) and Salesforce Initiated send for you to be able to send. * LCM to be on call to walk through sending/scheduling together, and answer any questions that pop up while you're in the system. Question/flags - please review and respond here: 1) Audience for this email: You have a list of stakeholders in a gdoc spreadsheet as audience for this email - is that who you want to send this email to? Or do you want to send this email to all Common Voice email subscribers? 2) Language: Common Voice email subscribers are all EN (English) - even if they opt-ed in from a non-EN Common Voice website. The Common Voice website is localized. The opt-in form checkbox is also localized (See screenshots). The email program is "English only" in it's function and description on the email preference center. Please update your opt-in language on the l10n website to indicate that this email program is currently in English only. Non-EN email optins will have gotten the English subscription confirmation email, and if they confirmed, would see that the email program is "English Only" in the email pref center, and then received a welcome email in English. So I think it's okay that we email *all* Common Voice subscribers, regardless of language. We do have Source URL from signups and can tell who signed up with a non-EN locale if you want to expand the email communications to non-EN. Expanding to non-EN is out of scope for this request, but please file a new bug if you want us to work with you to support non-EN. (We can technically do it of course! We just need to talk LOE/scope/timelines for the infrastructure setup on our end, and your team would need to send over the newsletter language field upon signup.) 3) Content: That newsletter content is rich! And super long. I recommend breaking out the one large email into smaller one-topic announcement emails to stretch out email, and Common Voice product, engagement over time vs. telling them allofthethings right now in one email.
Flags: needinfo?(lsaunders)
Oh! And here's our recommended gdoc template to use to produce your email content (please make a copy of this template for each email you want to send): https://docs.google.com/document/d/1Cyv0F3J441QmFZXAODV0kvOmG9nLF5zIqN0hL9P917w/edit#
1) Audience for this email: We would like to send this email to all Common Voice email subscribers 2) Language: Please update your opt-in language on the l10n website to indicate that this email program is currently in English only. (For Michael when he returns) 3) Content: I have talked to the team about this and we're currently looking at the content. We may cut some but also feel that this is all timely and important so will keep you posted.
Flags: needinfo?(lsaunders)
Thanks Lindsay! Brynne is setting up your sending audience and infrastructure this week. She'll add the details of where/how to send here when it's ready. QQ: What's a good reply-to email address for email replies to this audience? (do you have a commonvoice@mozilla.com ? Like you did with equalrating@mozilla.com ? or might I suggest creating a broader "open-innovation@mozilla.com" email group alias?) Details on how to set a new email reply-to google group/alias up can be found here: https://docs.google.com/document/d/1hTXGyVvMIy4miLQmZLSAvJgdjU0irLHzTNmvpokw9nQ/edit
Assignee: nobody → bhaack
Flags: needinfo?(lsaunders)
Sorry for the delay on this. The best email is commonvoice@mozilla.com I'll set it up today. Thanks!
Flags: needinfo?(lsaunders)
No worries! Everything is now set up for sending. The 'Salesforce Send' is located here (in Marketing Cloud): Salesforce Sends > Common Voice > MoCo_GLOBAL_COMMON-VOICE_NEWS_HTML_SUBS_ALL_EML The 'Salesforce Report' that contains Common Voice subscribers is here: https://mozillasalescloud.my.salesforce.com/00O0B0000037e9s Note: You don't need to do anything with this report as it is already selected in the 'Salesforce Send' mentioned above Below are links to a few 'how to' docs that may be helpful: How To: Email Campaign Set Up Guide: https://docs.google.com/document/d/17TWKutMwke3K4sdJryMr23BVYAvWIK9CjaK34I9H42s/edit?usp=sharing Sending Via a Salesforce Send: https://docs.google.com/document/d/1hBWjNhCiSMSWCK5wbJVuKfdU8lSEr9V0a_0h6wbEsq4/edit?usp=sharing Please let us know if you have any questions or need any additional help! Brynne
Hi Lindsay! Please be sure to add this send (and all future sends) to the Email Communications Calendar. Details on the calendar can be found here: https://docs.google.com/document/d/1IcYiEEVzPn_B5gNuY9Og66sHC15xivCEExpYTGz_W9o/edit?usp=sharing Thanks!
Lindsay's first email went out earlier this week \o/
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: