Versions Compared

Old Version 19

changes.mady.by.user Lopes da Costa, Valentina

Saved on

compared with

New Version 20

changes.mady.by.user Lopes da Costa, Valentina

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Steps

Expected results (Kiosk)

Expected results (RBI app)

Loyalty API usage (Kiosk)

Guest opens an offer on the RBI app

  • No action

  • Offer page is displayed:

  • No action

Guest taps “Use at restaurant”

  • No action

  • Offer is added to the guest’s pre-selection

  • A unique offer code is generated

  • No action

Guest taps on the Kiosk screen to start a new order

  • Loyalty sign in page shows up on the Kiosk and scanner becomes active

  • No action

  • No action

Guest scans the loyalty code or inputs 6 digit code in Kiosk

Info

Note: the pre-selected offer will show in the Kiosk screen after scanning with an option for the user to customize it

  • Offer is shown on the Kiosk and guest has an option to customize

Image RemovedImage Added

  • Modal is shown to guest confirming that the offer has been added to cart

  • Loyalty points balance is not updated, since the guest is scanning an offer

  • Offer pre-selection is cleared

  • Call the Identify endpoint, which will return the Loyalty User ID, the offer pre-selected, the loyalty points balance and a transaction ID

Guest opens a second offer on the RBI app, chooses to redeem in restaurant

  • No action

  • User will see modal in the app letting user know that only 1 offer can be added per order and prompting user to replace current offer

  • No action

Guest taps Replace

  • No action

  • New offer is added to the guest’s pre-selection and old offer is removed from pre-selection cart

  • No action

Guest either scans the Offer’s QR code or inputs 6 digit code into Kiosk

Info

Note: the pre-selected offer will show in the Kiosk screen after scanning with an option for the user to customize it

  • New offer replaces the previous selected offer in the Kiosk basket

  • Other items in the Kiosk basket are not removed or replaced

  • New offer is added to basket and guest has the option to personalize the offer

Image RemovedImage Added

  • Modal is shown to guest confirming that the offer has been added to cart

  • Loyalty points balance is not updated, since the guest is scanning an offer

  • Offer pre-selection is cleared

  • Keep track of the current basket contents including past scanned offer

  • Void the previous transaction

  • Call the Identify endpoint again, which will create a new transaction ID with the new offer

  • Replace the past scanned offer in the Kiosk basket with the new offer

On the Kiosk UI, navigates to the offers page

Info

Note: this step is only available in markets that have decided to show offers on the Kiosk UI.

Offers are displayed:

  • No action

Guest selects an offer

  • Details displayed

  • No action

  • No action

Guest adds offer to basket

  • Guest sees modal in the Kiosk letting user know that only 1 offer can be added per order and prompting user to replace current offer

  • Example screen to be added here when available

Info

Note: If an offer can’t be redeemed because the offer rules are not met, the Kiosk displays a modal to the guest explaining why the offer can’t be added to cart

  • No action

  • Call the Transaction Validate endpoint to verify that the current basket selection is valid

  • Note that the call above may return errors. Please refer to Loyalty API - Error List for details.

Guest checks out and pays

  • Order number shows up on the screen

  • Receipt is printed (ideally the receipt would include the points earned and/or burned + the updated loyalty points balance)

  • Guest sees updated points balance

 

  • Call the Transaction Update endpoint with a status of CLAIMED to complete the order

  • After this call it is not possible to modify the loyalty transaction anymore

...