This document will draft out the enablement plan for BK DE Loyalty. We will include risks to the launch and actions to take if those risks happen
Overview
Milestone | Status | Description |
---|---|---|
POS deployed | DONE | Toshiba deploys the new version of the software, Loyalty-capable. By default the loyalty integration should remain disabled to allow testing before use. |
RAM updated | DONE | RAM must be configured to indicate whether a given store supports loyalty. This update should be made in advance to ensure only stores that participate in Loyalty result in the guest’s point balance being updated. |
Loyalty tested on the POS | DONE | There are two main scenarios to test in-store March 5-6:
These tests will require to be synced with Kiosk test stores the following setup:
|
Loyalty tested on the Kiosk | DONE | Like for POS, there are two scenarios to test in-store March 5-6:
These tests will require to be synced with POS test stores the following setup:
|
Loyalty reset | DONE | RBI change to zero the loyalty points balance for all users prior to activation.
|
Soft launch | IN PROGRESS | Enabling loyalty (see detailed steps below) without announcements and CRM communications. The purpose would be to limit initial traffic - if any issues occur, they can be fixed with less impact to guests. Timeframe: 4 weeks for soft launch phase. We are aiming to Soft Launch on April 2nd, 2024 |
Go Live | NOT STARTED | The following changes must happen at the same time:
|
RBI Enablement Plan
Step | Action | Status | Owner |
---|---|---|---|
1 | BK DE to set in RAM Portal if a store has loyalty or not for all stores
Note: if this is not set for all restaurants when we enable loyalty, all stores will accept loyalty. | DONE | Mariann to complete RAM Valentina to run Sanity query |
2 | Run script to clear loyalty points of users in the platform for the first time in Production
| DONE | Loyalty Team |
3 | Run script to clear loyalty points of users in the platform for the second time and right before launch in Production overnight
SCRIPT RESULTS:
| DONE | Loyalty Team |
4 | Turn on Loyalty flags for all the users at 7:30am on Tuesday morning, April 2.
| DONE | Valentina |
5 | Have QA team do a smoke test of the Loyalty Online flows | IN PROGRESS | Loyalty QA Team |
6 | Work with BK DE team for them to test Loyalty Online and In-Store flows on April 2. Ask for team to bring friends and family to help mimic real restaurant. Setup two testing stores:
| IN PROGRESS | BK DE Team Loyalty QA Team |
7 | Monitor the launch for the next 24 hours
| IN PROGRESS | Loyalty team RBI Team BK DE Team |
8 | Have weekly check points in the next 3 weeks to monitor launch
| TO DO | Joana Loyalty Team |
Content Managagement
Navigation Bar in Sanity
ACTION: push content of navigation bar from staging to production on launch date
Vendor Config
All Toshiba PLUs for Reward and Offers need to be included inside the
Partner
field in SanityUsers cannot redeem Rewards on Delivery service mode
Day Part:
https://rbictg.atlassian.net/wiki/spaces/COG/pages/3657498694/Feature+Menu#Day-Parts
Remove Day Part on Feature Menu;
Remove Daypart from all items within Rewards
Double check on Lokalise Strings to ensure all strings are translated to German
ACTION: Change all “MyBK” strings to “MyBurgerKing”
signUp
signInOrCreateAccount
- MyBK Konto und RegistrierungRegister
ACTION: Update sign up / sign in strings in terms and condition
acceptTermsAndPrivacyIntro
-Ich akzeptiere die {termsOfServiceLink} und möchte Kronen sammeln, um personalisierte Angebote und Prämien zu erhalten. Es gilt unsere {privacyPolicyLink}.termsOfService
- NutzungsbedingungenacceptEmailsAndSpecialOffers.bk
- Ich möchte E-Mails mit Aktionen zu Burger King Produkten und MyBurgerKing erhalten.privacyPolicy
- Datenschutzerklärung
ACTION: Update Store Locator loyalty strings that indicates if restaurant has loyalty
loyaltyStoreLocatorInStore - Update it to MyBurgerKing
loyaltyStoreLocatorMobile - Update to empty
ACTION:
signUpToGetStartedWith
- Jetzt anmelden und Vorteile genießen {rewardsPolicyLink}royalPerks
- von MyBurgerKing Check at 10PM UTC (12AM CET)
ACTION:
loyaltyBannerLoggedOutMessage
- Herzlich Willkommen! Mit jedem Einkauf kannst du Kronen sammeln und sie zum Einlösen von Prämien verwenden.
Loyalty Static page in Sanity
ACTION: Push the static page /myburgerking to production
ACTION: Push both the terms and conditions static page to production: http://burgerking.de/nutzungsbedingungen and http://burgerking.de/nutzungsbedingungen-myburgerking
ACTION: Push the privacy policy changes to production http://burgerking.de/datenschutz
ACTION: push to production https://www.burgerking.de/datenschutzerklaerung
ACTION: push to production https://www.burgerking.de/faq
Marketing Tile in Sanity
ACTION: Push the new marketing tiles to production
Feature Loyalty UI
Ensure all the fields are filled in for German and English languages and push to production
Push to production
Loyalty Not Authenticated
dropdown to include loyalty incentive information for users to login. When users are logged out and click on “MyCode” navigation bar button, they will see this information.
CRM
Send-out timelines of each of the below deliverable to be confirmed by Mariann
Set up weekly standups to look at Amplitude Loyalty & CRM Dashboard
CRM Enablement plan
Campaign | Status | Link | Start Date | Comment | Checkbox |
---|---|---|---|---|---|
Postal Code | ACTIVE | 27/3 | Campaign paused (50K users with ZIP filled) |
| |
T&C | READY | 2/4 | Test Link prior send-out. To be sent in the afternoon around 3:30pm. | ||
Confirmation email | IN PROGRESS | 2/4 | Test Link prior send-out | ||
New Users Email | READY (Missing image) | 9/4 | |||
New Users IAM | READY | 9/4 | Send test to Mariann | ||
Existing Users IAM | READY | 9/4 | Send test to Mariann | ||
Existing Users Email | READY (Missing image) | 9/4 | |||
Dynamic Tier | READY | 9/4 | |||
First Reward | READY | 9/4 |
Rollback plan
Before we rollback we need to communicate to the guests that there will be a change in T&C contract.
Turn off In-Store Loyalty (impact majority of sales for BK DE)
Change Identification Code Type to
Static
variation
Turn off Online Loyalty (impact small percentage of sales for BK DE)
Change Enable Loyalty in the Apps to
False
Toshiba Enablement Plan
Activation of function Monday / Tuesday night after EOD
disable payback screen
To be completed by today afternoon
ACTION: Jens to confirm when this step complete
enable payback button in payment menu
enable MyBK or BK-App button
To be completed by today afternoon
ACTION: Jens to confirm when this step complete
Tillster Enablement Plan
Tillster to run the following LogMeIn tasks
To enable Loyalty Stores:
BKG - RBI - Loyalty - Enabled
To enable Non-loyalty stores:
BKG - RBI - Turn to Non-Loyalty RBI store with ability to redeem offers from app
Completely switch off RBI loyalty and roll back the project (Payback will be enabled)
BKG - Payback - Loyalty - Enabled (rollback from RBI)
Risks
Below we have mapped the potential risks to the BK DE Loyalty Program launch. On the agreed launch date, the table below will guide the Go/No-go decision.
Risk Description | Impact | Likelihood | Mitigation Strategy | Go/No-go Decision | |
---|---|---|---|---|---|
1 | Less than 80% of franchisees have been onboarded. | High – poor UX, large potential impact on sales since many stores wouldn’t accept offers (high % of market sales). | High – very fragmented franchisee system, slow progress so far. |
| Not launch. Wait until % is reached. |
2 | Forter integration not complete. | Medium – fraud concerns, users could create multiple accounts to abuse initial point balance. | None – integration completed. |
| Launch, enable Forter post-loyalty launch. |
3 | Tillster hasn't complete full integration (i.e. multi-scanning, deposits). | Medium – Reward and Offers cannot be scanned multiple times in the same order in Tillster Kiosks | Low – Tillster has committed to mid December to finish multi-scanning and deposits Dev work |
| Launch, have clear communication in Tillster Kiosks letting users know they can only scan once. Have plan to enable multi-scanning in next couple of weeks |
4 | Ops trainings not complete. | High – Loyalty launch requires a significant change in customer behavior which needs to be supported by stores' team members. | Low – Loyalty flows for stores with loyalty are aligned. Pending alignment on stores w/o loyalty. |
| Not Launch, wait until training is complete. |
5 | Comms not ready. | High – guests might not understand the loyalty program. | Low |
| Not Launch, wait until communications are ready. |
6 | Reporting not ready. | Low – this will not affect the user journey. | Medium – work still ongoing as of end of Nov. Requires coordination with Sotec. |
| Launch. Send data manually until required reports are ready. |