BKDE - Sign Up Process
BKDE requested changes to the current sign up process. The request came from their legal team. This document summarizes the changes and the related priority level (on a scale from 1 = high priority to 3 = low priority)
Requirements
Sign Up Page Content:
Priority:
Description: replace the text in the checkboxes to change to include loyalty in the acceptance of the terms and condition. Loyalty & T&C are mandatory, while marketing communication are optional
Tasks:
Tab name changes can be made in Lokalise, check impact on sign up button in site header (Update the naming from “MyBK” to “MyBurgerKing” )
Validate if the change has impact on the button on mobile view
T&C related changes can be made in Sanity document, Feature Account Sign Up Page. Updates below:
Outcome: NOW
Sign Up Page Process:
Priority:
Description:
Germany has currently auto-sign up enabled. The user inputs the email address and the account is created, even though the users does not verify the email address by clicking on the email (see below)
From a legal standpoint we can’t create an account if we don’t have verification of the email (otherwise we could create account with fake emails/on someone else behalf)
We need to change from auto-sign up to sign up with OTP for all new users
Tasks:
The switch should be performed next week to ensure that the process works successfully prior to the launch of loyalty
Outcome: NOW
Sign Up Confirmation Email:
Link:
Priority:
Description:
Once the guest has validate the account, he has to receive a confirmation email (defined as email that references the T&Cs after a successful sign up)
The sign up flow therefore will become as follow:
User inputs the email adress
User receives OTP email
User inputs OTP
User receives an email with the link to the T&C PDF (confirmation email)
In the email we need to include a link to a PDF of the terms and conditions
Tasks:
In sanity we can configure a static page with an option to open a new tab (see BKNZ)
The sign in complete event might not trigger in 100% of the cases. @Fisher, Luke (Deactivated) will validate with Mihai if this can be used as a trigger in AWS. Luke will assess if we can use any back end event
Note that this doesn’t tackle yet the double opt in process for email communications. This will require a dedicate ticket and confirmation of the desired flow
Outcome: NOW
Sign Up Page User Account Deletion:
Priority:
Description: If the user does not validate the account within the 24 hours from the account creation request, by inputting the opt, we need to delete all the user data
Tasks: requires development, not planned for Q2 so far
Outcome: LATER. Ticket: https://rbictg.atlassian.net/browse/IREQ-1797
Account Page:
Priority:
Description: update account page in the date of birth field
Tasks:
The date of birth validation is already in production today, see below:
Outcome: LATER (Requires minor development to switch MM and DD fields) https://rbictg.atlassian.net/browse/IREQ-1798