...
Table of Contents | ||
---|---|---|
|
Review & Approval:
First Round
Internal only. The objective is to include any comments/concern and establish which are the deliverables we can accommodate prior to loyalty launch
- Anna
- Anton
- Luke
- Carlos
- Valentina
- Daniel
- Joana
Second round
- Mariann
Requirements
Sign Up Page Content:
Priority: 1️⃣
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”
...
)
Note |
---|
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:
- Ich möchte E-Mails mit Aktionen zu Burger King Produkten und MyBurgerKing erhalten. Der Versand erfolgt entsprechend unserer Datenschutzerklärung.
- Ich akzeptiere die Nutzungsbedingungen und möchte Kronen sammeln, um personalisierte Angebote und Prämien zu erhalten.
...
Outcome:
Status colour Green title NOW
...
Priority: 1️⃣
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:
- Set up OTP email (Sanity)Switch Content to be updated in Sanity email template (not available directly to FZs)
- Disable LaunchDarkly flag hereSwitch from auto-signup to sign up with OTP
...
Link:
Priority: 1️⃣
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)
Info |
---|
The sign up flow therefore will become as follow:
|
In the email we need to include a link to a PDF of the terms and conditions
Tasks:
- Set up email for all new users
- Create a copy of the email also for existing users
In sanity we can configure a static page with an option to open a new tab (see BKNZ)
- Leverage first time user does Sign In complete as event to trigger the confirmation email
Note |
---|
The sign in complete event might not trigger in 100% of the cases. Fisher, Luke 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 |
---|
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:
Status colour Green title NOW
...
Priority: 2️⃣
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:
. Ticket:Status colour Red title LATER Jira Legacy server System Jira serverId 255417eb-03fa-3e2f-a6ba-05d325fec50d key IREQ-1797
Account Page:
Priority: 3️⃣
Description: update account page in the date of birth field
Tasks:
...
Outcome:
(Requires minor development to switch MM and DD fields)Status colour Red title LATER Jira Legacy server System Jira serverId 255417eb-03fa-3e2f-a6ba-05d325fec50d key IREQ-1798