...

Open questions

• Whether expiring points is required, and if so in which phase(s)

  • Points expiry

    • Proposal not to expire points either on RBI or SessionM, to avoid potential discrepancies

    • This is possible to configure in SessionM

    • ACTION: Valentina to confirm whether this is possible or requires development

    • In RBI Loyalty, points will be configured to expire after 6 months of the points’ issue date, grouped to the end of the month. This means that points accrued on the 15^th of January would expire on the 30^th of June

    • ACTION: Zaira to confirm with RBIberia Legal whether the privacy policy needs to be updated to reflect the monthly grouping

• How do we handle scenarios where guests change loyalty tiers?

  Loyalty tiers

• Proposal to disable downgrades from Superking to King during the migration, to avoid guest frustration since they won’t be able to burn

• Upgrades from King to Superking still allowed

• ACTION: Zaira to confirm whether this is possible on SessionM

ACTION: Valentina to confirm whether this requires development

Point expiration

• Point expiration will be set to 180 days and will expire at the end of each month (confirmed by @Raúl Moreno)

• We will only migrate user’s point expiration based on their active loyalty points. Past loyalty points expiration from previous point balance will not be migrated.

  • ACTION:@Raúl Moreno to confirm by April 3

• After migration, RBI point expiration dates will be different from SessionM since SessionM will expire points daily and RBI will expire points at the end of the month (confirmed by @Raúl Moreno)

• Confirm how SessionM will send us the point expiration date

  • ACTION:@Raúl Moreno to confirm by April 3

• Loyalty Tiers

  • Users will be able to upgrade tiers. Can you confirm how many crowns users need to earn and in how much time for them to become Tier 2?

    • ACTION:@Raúl Moreno to confirm by April 3

  • Users that are in Tier 2 will continue in Tier 2 for the next 6 months once the migration starts  (confirmed by @Raúl Moreno)

• Loyalty Transactions

  • Two years worth of loyalty transactions will be migrated to the RBI app at the end of Phase 1 (confirmed by @Raúl Moreno)

• Cancellations

  • Vendors will send us cancellations using the VOID endpoint (confirmed by @Raúl Moreno)

  • Customer Support team will also have access to the support tool and will cancel orders in RBI support tool as well as Session M support tool only in Phase 2 and onwards (confirmed by @Raúl Moreno)

• When to send Identify and Update Transactions

  • Raul raised potential fraud implications for order to be identified and claimed only when the order is picked up/ delivered for mobile ordering

    • Potential solutions: Homeria creates 2 orders - (1) to claim Rewards only and deduct points right after payment is complete and (2) to earn points after order is delivered or picked up

    • Implications: If the above solution is chosen, then to cancel orders Homeria will need to VOID both order 1 and order 2 to void complete order

    • ACTION:@Raúl Moreno to confirm which solution to be used by April 3

Next actions

• Phase 0:

  • Confirm that we can retrieve loyalty data from SessionM to be ingested by RBI (Miguel-Romero, Almudena)

• Phase 1:

  • Confirm that the existing user sync endpoint can be modified to return the RBI Loyalty ID in addition to the Cognito ID (Miguel-Romero, Almudena)

  • Confirm that Get User Details returns the loyalty points balance and tier (Silva, Carlos)

  • Share testing environment details with all vendors (Lopes da Costa, Valentina)

  • Provide example payloads for endpoints not documented in the standard Loyalty API documentation (Francisco Paglia)

• Phase 2:

  • Define how rewards will be handled (Silva, Carlos)

...