Closed Bug 895060 Opened 12 years ago Closed 12 years ago

Send confirmation email to users after they enter an event at webmaker.org/events

Categories

(Webmaker Graveyard :: Events, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: matt, Assigned: jon)

References

()

Details

Attachments

(2 files)

* GOAL: once a user enters an event at webmaker.org/events, we want to be able to send them a thank you email. * This helps to recognize and thank them, provide them links to helpful resources, ways to report back, and travel up an engagement ladder * QUESTION: how do we do this? ** Is there a way to use Blue State Digital (BSD) for this? ** Users are asked to opt-in to the BSD announcement list when they create their account. Are there ways to leverage that here? * Brett: going to mark this as "needinfo" for you, because not sure who else to ask
Flags: needinfo?(brett)
* Amira will provide the copy and content for the email itself. * Amira can you paste an etherpad draft here when you're ready so that mentor team can review?
* Amira: now that we have event data, should we tackle this one next?
* QUESTIONS FOR DEV TEAM: * 1) How difficult is this? Is this a reasonable scope of work? * 2) What's the mechanism for sending the mails? (Do we use BSD for this?)
Updated text for emails once entered event and after event is completed: https://etherpad.mozilla.org/ReplyEmailEvents
* One potential process for this: * 1) Amira or intern batch exports event organizer data to CSV. (Say on a weekly basis.) * 2) Amira or intern imports data into Blue State Digital (BSD). Into a new segment we will create for "Maker Party 2013") * 3) BSD sends new imports to the segment an auto-response email. This process means we could essentially do the work ourselves, through BSD -- instead of requiring dev to do anything.
@ question for Laura / Erica S: what's the process for us to get BSD access and do list management? (e.g., create a new list segment, etc.)
I can get you BSD access, but that's not the same as providing the orientation to the BSD system you (may/maynot?) need... I think connecting with Watershed is probably a good first step for that: "Fran Navarro" <fnavarro@mrss.com> Alternately, I have access to the mailing lists (and relevant experience) for whatever is needed in the short term.
Thanks Rebeccah! I've emailed Fran a link to this ticket to see if she has suggestions for us. Here's what we'd need BSD help with specifically: 1) Create a "Maker Party 2013" list segment. So that we can identify and communicate specifically with Maker Party event hosts. 2) Set up an auto-responder email for that segment. So that when we import new individuals to that segment, they automatically receive a boilerplate welcome email from us. 3) Work out an import process. We'll be importing in batches. From a .CSV into BSD. Rebeccah: are you able to help us do any of those? Or do we need to seek help for all three?
@ Brett: one question for you before we push ahead with this: * do you agree that this is the best short-term approach? * exporting and importing into BSD in batches is obviously not as ideal as a more integrated and automated process. But it has the virtue of being something we can largely do ourselves, without requiring work from devs. * Let us know if you think this is the right approach?
+ adding Bobby * Bobby: see comment 8 above. We are BSD noobs, and could use some guidance. Are you able to help with any of those 3 things?
Adding Jon and myself. Jon, can you weigh in on this for Matt?
I don't believe BSD is the solution for this. I just added bug #895541 - there is a solution that Mozilla Web Dev uses. This would be seperate from engagement emails. These are "event based", ie, when a user signs up, adds an event, or their work is remixed. Jon and I discussed building a prototype of this during our work week. Brett
Depends on: 895541
Flags: needinfo?(brett)
As a compromise, can we do both (a UX solution for information triggered by the user as well as .CSV export of Webmaker Account emails)? These contacts should definitely be in BSD and accessible to Comms for outreach. (I will defer to you guys re: the need for email based notifications of webmaker account activity.) As I mentioned before, I can import the list in the interim until we have a dedicated email human.
When users signup, they can choose to subscribe to the webmaker mailing list so they're already being captured in BSD
Assignee: nobody → jon
Status: NEW → ASSIGNED
Attachment #790463 - Flags: review?(david.humphrey)
Attachment #790465 - Flags: review?(david.humphrey)
Comment on attachment 790463 [details] [review] https://github.com/mozilla/webmaker-events/pull/26 Question about env var being false, and one copy/paste error. Looks fine otherwise.
Attachment #790463 - Flags: review?(david.humphrey) → review-
Comment on attachment 790465 [details] [review] https://github.com/mozilla/webmaker.org/pull/329 Similar question here about using 'false'
Attachment #790465 - Flags: review?(david.humphrey) → review-
Comment on attachment 790465 [details] [review] https://github.com/mozilla/webmaker.org/pull/329 Habitat does coerce booleans properly, so this is okay
Attachment #790465 - Flags: review- → review?(david.humphrey)
Comment on attachment 790463 [details] [review] https://github.com/mozilla/webmaker-events/pull/26 However, process.env still gets a string, so I just did a type equality comparison for "true".
Attachment #790463 - Flags: review- → review?(david.humphrey)
Attachment #790463 - Flags: review?(david.humphrey) → review+
Attachment #790465 - Flags: review?(david.humphrey) → review+
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Attachment mime type: text/plain text/plain → text/x-github-pull-request text/x-github-pull-request
Hey Jon, Can you update the current text on this email with the text in this doc? https://docs.google.com/document/d/1NG7IafekCgxs9ESG1m3TJQ8ltrh-eX8k4BtaOBb6QhQ/edit?usp=sharing
Sure thing! Could you file a new bug and assign it to me? Thanks!
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: