Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

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:

  • Link: https://www.burgerking.de/signup

  • 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” )

Validate if the change has impact on the button on mobile view

  • 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: NOW

Sign Up Page Process:

  • Link: https://www.burgerking.de/signup

  • 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:

  • 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

The switch should be performed next week to ensure that the process works successfully prior to the launch of loyalty

  • Change content of the email (to be provided by Mariann)

  • Outcome: NOW

Sign Up Confirmation Email:

  • Link:

  • Priority: 1️⃣

  • Description:

    • Once the guest has validate the account, he has to receive a confirmation email '

    • In the email we need to include a link to a PDF of the terms and conditions

image-20240314-162402.png

  • 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)

image-20240314-162600.png

  • Leverage first time user does Sign In complete as event to trigger the confirmation email

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

  • Outcome: NOW

Sign Up Page User Account Deletion:

  • Link: https://www.burgerking.de/signup

  • 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: LATER. Ticket: IREQ-1797 - Getting issue details... STATUS

Account Page:

  • Switch the positioning from Year / Month / Day to the common one Day / Month / Year
  • Have a validation rule if the users inputs a birthdate that implies he under 16 years, we should have an alert in red and small below ““Du erfüllst nicht das Mindestalter.”

The date of birth validation is already in production today, see below:

image-20240314-155408.png
  • Outcome: LATER (Requires minor development to switch MM and DD fields) IREQ-1798 - Getting issue details... STATUS

  • No labels