Improved onboarding

[ryanwilsonperkin]

Our onboarding needs to be better to help retain volunteers. Going to use this issue to catalogue things that aren't good enough just yet.

[ryanwilsonperkin]

It'd help to have some metrics for funnel analysis to see where people are dropping off and to look at different cohorts. We've got data on how many volunteers signed up, and which requests they handled (if any) but we don't have a lot of insight into volunteers that never completed a request, which is about two thirds of them. This seems like a pretty rough top of funnel that could use some focus on conversion.

[ryanwilsonperkin]

We don't use google analytics for user privacy purposes, but something that's backend-only could work fine for our needs.

[ryanwilsonperkin]

Onboarding right now:

• Users hit our landing page, read the copy, get sold on the vision, and click on one of the signup CTAs
• On the signup page they set an email and a password
• Next they land on the user account creation page. This is jarring, it doesn't tell them anything about what to do next except offer them a form to add their name and phone number. Maybe we should be asking for that during signup if it's that important. Below the fold is where the actual next step is, which is to signup to be a chef/deliverer/organizer. This should probably be more prominent
• Next, they're on the chef/deliverer/organizer application page. This is a form with a few sections they have to fill out, listing their availability and agreeing to TOS. They submit the form
• After submitting the form, they're taken to a page that just says (basically) "Thanks, we'll be in touch". Then their application is in a pending state, so they can't see the requests page until after they've been approved. In theory, a volunteer organizer will come along shortly and approve it at which point...
• They get an email telling them they've been approved, as well as a link to our guidelines. Notably, this email does not link them to what the next step should be. We should preemptively send them these guidelines so they can review them while they're waiting for approval (or maybe we should consider removing the approval step)
• They're approved, and can now visit the website, go to the requests page, and start signing up for requests.