Versions Compared

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 the Loyalty code page on the RBI app

  • N/A

  • Loyalty code page is displayed:

  • Not applicable

Guest taps on the Kiosk screen to start a new order

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

  • N/A

  • Not applicable

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

  • Kiosk authenticates the guest and shows the home page

  • Scanner remains active

  • Guest receives a successful confirmation modal

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

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

  • No action

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

  • A unique offer code is generated

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

Info

Note: if a user pre-selects more offers in the app, all pre-selected offers will show in the Kiosk screen after scanning with an option for the user to customize each offer

  • Offer(s) are shown on the Kiosk and guest has an option to customize

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

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

  • Void the previous transaction

  • Call the Identify endpoint again, which will create a new transaction ID and selected offers

  • Update the basket with the offers returned

Guest customizes offers at will and touches confirm

  • These offer(s) are incrementally added to the cart and do not replace any of the existing cart items

  • No action

  • No action

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

  • Added incrementally

  • No action

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

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

1.3. Using offer pre-selection

...

Steps

Expected results (Kiosk)

Expected results (RBI app)

Loyalty API usage (Kiosk)

Guest opens an offer on the RBI app

  • N/A

  • Offer page is displayed:

  • No action

Guest taps “Use at restaurant”

  • N/A

  • 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

  • N/A

  • No action

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

Info

Note: if a user pre-selects more offers in the app, all pre-selected offers will show in the Kiosk screen after scanning with an option for the user to customize each offer

  • Offer(s) are shown on the Kiosk and guest has an option to customize

  • 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

Guest customizes offers at will and touches confirm

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

Guest customizes offers at will and touches confirm

  • These offer(s) are incrementally added to the cart and do not replace any of the existing cart items

  • No action

  • No action

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

Info

Note: the flow is exactly the same if the guest pre-selects multiple offers.

  • No action

  • Only the second offer is added to the guest’s pre-selection

  • A unique offer code is generated

  • No action

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

Info

Note: if a user pre-selects more offers in the app, all pre-selected offers will show in the Kiosk screen after scanning with an option for the user to customize each offer

  • Offer(s) are shown on the Kiosk and guest has an option to customize

  • 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

Guest customizes offers at will and touches confirm

  • These offer(sKeep track of the current basket contents including offers

  • Void the previous transaction

  • Call the Identify endpoint again, which will create a new transaction ID and selected offers

  • Update the basket with the offers returned

Guest customizes offers at will and touches confirm

  • These offer(s) are incrementally added to the cart and do not replace any of the existing cart items

  • No action

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

Guest adds offer to basket

  • Added incrementally

  • No action

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

 

...

Steps

Expected results (Kiosk)

Expected results (RBI app)

Loyalty API usage (Kiosk)

Guest opens a reward on the RBI app

  • No action

  • Reward page is displayed:

  • No action

Guest taps “Redeem in Restaurant”

  • No action

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

  • A unique reward 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

  • N/A

  • No action

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

  • Pre-selected reward(s) are shown on the Kiosk and guest has an option to customize

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

  • The reward’s loyalty points cost is temporarily subtracted from the guest’s loyalty points balance at this moment

  • Reward pre-selection is cleared

  • Call the Identify endpoint, which will return the Loyalty User ID, a list of reward(s) pre-selected, loyalty points balance and a transaction ID

Guest customizes rewards at will and touches confirm

  • These reward(s) are incrementally added to the cart and do not replace any of the existing cart items

  • No action

  • No action

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

Info

Note: the flow is exactly the same if the guest pre-selects multiple rewards.

  • No action

  • Only the second reward is added to the guest’s pre-selection

  • A unique reward code is generated

  • No action

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

  • Pre-selected reward(s) are shown on the Kiosk and guest has an option to customize

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

  • The reward’s loyalty points cost is temporarily subtracted from the guest’s loyalty points balance at this moment

  • Reward pre-selection is cleared

Guest customizes rewards
  • Keep track of the current basket contents including rewards

  • Call the Identify endpoint again, which will create a new transaction ID and selected offers

  • Void the previous transaction

  • Wait for Void Confirmation

  • Call the Update endpoint with full Kiosk basket contents

Guest customizes rewards at will and touches confirm

  • These reward(s) are incrementally added to the cart and do not replace any of the existing cart items

  • No action

  • No action

On the Kiosk UI, navigates to the rewards page

Info

Note: this step is only possible if the market has decided to allow showing rewards on the UI.

  • Rewards are displayed

  • No action

  • Query Sanity to Display Rewards in the Kiosk

Guest adds a reward to basket

  • Guest selects and adds reward to cart

  • The reward’s loyalty points cost is temporarily subtracted from the guest’s loyalty points balance in the app

  • No modal is shown

  • Call the Update endpoint with full Kiosk basket contents

Guest removes first reward from order

  • Guest removes the first reward from the Kiosk cart

  • Basket is updated accordingly

  • Guest sees the first reward’s loyalty points returned to their loyalty points balance in the app

  • No modal is shown

  • Call the Update endpoint with full Kiosk basket contents

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

Guest checks out and pays

  • Order number shows up on the screen

  • Receipt is printed

  • Guest sees updated points balance

 

  • Call the Transaction Update endpoint with a status of CLAIMED

2.4. Limit one reward per purchase

...