How to handle password reset attempts for non-existent accounts in Memberstack without confusing users? Answered

Post author
Jordan Ryskamp

👋 Hey there! My client is having issues with clients thinking they have an account, resetting their password, and never getting a code (obviously, because they don’t have an account).

Main question: Is there a way I can tap into a password reset attempt, check to see if there is an account, and if not, then send the person an email saying “sorry, [client name] doesn’t have an account for you linked to this email”? Happy to use Zapier to handle all that but I need to know if I can get an event to trigger it in Memberstack.

Or are there better ways to handle the communication to minimize these types of end-user issues?

Comments

2 comments

  • Comment author
    A J

    Hey  Jordan Ryskamp, I believe currently there is no event being triggered that we can tap into from Make / Zapier for this. I believe once someone initiates the reset password flow, they are shown the "If this email exists, you'll receive an email with the reset instructions." message.

    You could additionally show a text pop-up after some time on the page which notifies that if they still haven't received the mail, they probably need to create an account via Signup page. Of course, if they have an account already, they can't signup, so that should provide some context for users with no account attempting to reset their password.

    You could also offer passwordless login / signups (if it fits your use-case) as if a user tries to login via passwordless and does not have an account, I believe they will be shown 'The provided email is not found' message which could clear things out for the users. And if passwords are a mandatory requirement, you could collect their passwords during onboarding stage via profile update forms.

    Also was wondering if this approach would work.

    You can have a custom form in place of the reset password form and which triggers a webhook in a Zapier workflow which in turn checks if the member exists and if they don't, send an email with the required notification.

    And on the reset password page, make use of the Memberstack method in the custom code as follows:

    // Send a password reset email 
const response = await memberstack.sendMemberResetPasswordEmail({
    email: "newuser@example.com" 
});
return response;

    So if the user does exist, they will receive an email by Memberstack, if not the use-case is handled by Zapier. I have not tested this approach, but theoretically customizing the reset flow should solve your use-case.

    0
  • Comment author
    Jordan Ryskamp

    Thanks for the reply
    A J! I’ll talk with the client and test out some ideas here!

    0

Please sign in to leave a comment.