...
| 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:
...
Link:
Priority: 1️⃣
Description:
Once the guest has validate the account, he has to receive a confirmation email '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
...
- Leverage first time user does Sign In complete as event to trigger the confirmation email
| Note |
|---|
The sign up 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. Anna to check if we can limit to the first timeLuke 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