Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Member Survey Process #157

Open
3 tasks
alexandrastubbs opened this issue Jun 21, 2020 · 11 comments
Open
3 tasks

New Member Survey Process #157

alexandrastubbs opened this issue Jun 21, 2020 · 11 comments

Comments

@alexandrastubbs
Copy link
Member

Overview

New member survey is built, although new members are not receiving it. Identify the right medium to share the survey and set up a process to facilitate dissemination & collection.

Dependency

100Automations/futureautomations#8

Action Items

  • Research potential mediums for survey sharing & create proposal (and current process)
  • Attain approval for proposed collection process
  • Put process into place

Resources/Instructions

New Member Survey Link
Survey Comparison Board
Greet Bot

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 25, 2020

@alexandrastubbs I added greetbot link to the Resources section above. It is installed on our slack account. So all we have to do is use it is have one of the slack admins (I am one of them), message GreetBot and make changes.

I changed the current "sent right after anyone joins" message to say the following:
Screen Shot 2020-06-25 at 9 57 41 AM

I did not add anything about the survey. I think we should discuss what we want that message to be. Additionally we are on the free plan which entitles us to configure one scheduled message only.

Screen Shot 2020-06-25 at 10 08 25 AM

They have the following info on their site:

Do you offer special pricing?
Yes, we do offer a discount for registered non-profits and educational institutions. Get in touch with us to find out about special pricing options.

So next steps will be

  1. Reaching out to CfA to ask them if they have a relationship with them. And if they don't I can write directly to GreetBot for details.

  2. And, we should put one of the UX team members on finding out if the timing of the greetbot is working for people and as well as just considering other options (e.g., having it wait an hour, or 10 min, etc.).

@alexandrastubbs
Copy link
Member Author

@ExperimentsInHonesty do you have contact info for the individual to connect with at CfA? I will reach out to start to inquire.

@alexandrastubbs
Copy link
Member Author

Before creating a proposal for where and when we should share new member survey, looking to get clarity on these things (@ExperimentsInHonesty, we can chat during our next TB):

  1. What are the key differences between remote onboarding survey and new member survey?
  2. What is the goal of the new member survey? To learn about the individual or to gauge effective of HFLA site?
  3. Where in the journey should someone be answering these questions? (Slack feels right, but would like to discuss after answering above questions)
  4. What are we doing/plan to do with the data that we collect?

@alexandrastubbs
Copy link
Member Author

@ExperimentsInHonesty will reach out to Tracy to get the template used to source API licenses so it can be mimicked for slack request.

@ExperimentsInHonesty
Copy link
Member

@alexandrastubbs Here is the website for the greet bot we use that currently only allows one message to be configured
https://greet.bot/. Its definitely worth writing to them. I sent you a copy of what tracy wrote. When I am asking for things, I make the following information clear. We are fiscally sponsored by Code for America which is a 501c3. And we will write a case study in the form of a medium article if they will give us a free licence to use. Can you write the first draft?

If that does not work, it turns out that someone has written an open source version of this, although we would have to pay for hosting. But if we can't get what we want, writing our own is not a bad idea. https://github.com/CivicTechTO/slack-greeting-bot
Here is a tutorial for building our own slackbot: https://www.freecodecamp.org/news/how-to-build-a-basic-slackbot-a-beginners-guide-6b40507db5c5/
https://api.slack.com/community
https://github.com/mishk0/slack-bot-api

@alexandrastubbs
Copy link
Member Author

Thanks for sharing, @ExperimentsInHonesty. This is on my to-do list to get done in the next two days. Will circle back with a first draft.

@alexandrastubbs
Copy link
Member Author

@ExperimentsInHonesty do you mind clarifying where you sent the copy of Tracy's note? Apologies, but I cannot seem to find it.

@alexandrastubbs
Copy link
Member Author

Email has been sent to Greet Bot to learn about non-profit pricing options for the tool.

@alexandrastubbs
Copy link
Member Author

Received word that we are eligible for special pricing with Greetbot. The discount is 50% for non-profits, which brings the price down to $6. Need to evaluate if we have any budget (does that exist?) to spend on this, or if it is worth the spend.

@alexandrastubbs
Copy link
Member Author

@ExperimentsInHonesty will create 100 Automations proposal to build our own Greetbot tool

@ExperimentsInHonesty
Copy link
Member

I opened a new issue with a automation proposal 100Automations/futureautomations#8

@ExperimentsInHonesty ExperimentsInHonesty transferred this issue from hackforla/website Jun 28, 2021
@Rabia2219 Rabia2219 moved this to Review by Bonnie in P: CO: Project Board Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Review by Bonnie
Development

No branches or pull requests

2 participants