Remove email verification step during customer onboarding - Githubissues

livepeer / studio

Livepeer Studio is your home for building, broadcasting, and publishing video on the open internet with the Livepeer Network. Effortlessly manage livestreams, video uploads, API keys, network usage, billing, and more.

https://livepeer.studio

MIT License

73 stars 33 forks source link

Remove email verification step during customer onboarding #666

Closed pglowacky closed 2 years ago

pglowacky commented 2 years ago

Per this proposal, I'd like to remove the step where customers are required to verify their email before being dropped into the dashboard.

Requirements:

Customers should use the registration page to sign up for an account
Customer information is automatically saved into Hubspot (as they are today)
Verification email is still sent, although it is not required to access the account
Copy on the verification email needs to be changed (details below)
Once customer signs up for an account, they are immediately directed to the dashboard (elimination of the screen that requires verification)
IMPORTANT: we will need to be able to easily and quickly roll back these changes.

Customer Experience:

User registers at Livepeer.com/register (no change)

Customer account is created and immediately dropped into an account. Change: removal of the verification step

Customer is sent a verification email to email on file, although there is no incentive to verify

Copy is changed to: Please verify your email address to ensure that you can change your password or receive updates from us.

MRTIBBETS commented 2 years ago

When ready, I'd like to review the pull request for any Verification Email polish, please. Thanks in advance!

adamsoffer commented 2 years ago

@pglowacky I think if we remove email verification we should implement some spam prevention? Recaptca? I think we get a lot of spam sign ups as is.

FullStackTiger commented 2 years ago

@pglowacky Also I think:

form validations
email checking backend API(real email address or not)

adamsoffer commented 2 years ago

@FullStackTiger I've discussed with Paige and opened this issue. https://github.com/livepeer/livepeer-com/issues/699

FullStackTiger commented 2 years ago

After getting the score from Recaptcha API if score < 0.5(maybe the user is spam), we should use an email verification workflow? if score >= 0.5, remove email verification step? @pglowacky @adamsoffer

pglowacky commented 2 years ago

@adamsoffer @FullStackTiger Hang on. I thought that the invisible reCaptcha wouldn't interrupt users? Sending some users to verification will alter the results of this two-week experiment.

adamsoffer commented 2 years ago

@pglowacky this happens in the background. It won't interrupt any user flow. It will simply prevent bots from submitting the form.

adamsoffer commented 2 years ago

Vukasin - if the user is a bot we don't have to take any action, we can just not submit the registration form.

pglowacky commented 2 years ago

@adamsoffer Is there any chance a good user could get marked as a bot? If there's not, I'm okay with proceeding. Just hoping to get clean results 🙏

adamsoffer commented 2 years ago

@pglowacky I'll say it's highly improbable. Nearly every saas product registration form uses it these days without issue. But let's perform a bunch of test registrations on staging so we can have 100% confidence in it!

pglowacky commented 2 years ago

@adamsoffer Sounds excellent! Thanks 👍