This page documents the expected user experience when RBI guests redeem rewards when they place orders using the Kiosk, part of Customer Journey Scenarios - Kiosk. See also Kiosk - Redeem Offers and Kiosk - Edge Cases.
Note:
Adding a modifier(s) to a reward could have an extra cost
Cost is set by the market and Kiosk/POS vendor
Example: extra patty on a Whopper reward costs $1 more than the base reward price of $0
Contents
1. While signed out
Redeeming rewards while signed out is not possible. Rewards are only available to guests who have an account and have enrolled in the Loyalty program.
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest looks at the Kiosk screen |
|
|
|
Guest touches the screen to start a new order |
|
|
|
Guest decides to continue without signing in |
|
|
|
Guest taps on the rewards tab Note: this step is only possible if the market has decided to allow showing rewards on the UI. |
|
|
|
Guest chooses to add menu items instead, checks out and pays |
Note: (optional) guests would be shown the number of points they could have earned, and they are prompted to sign up for their next order |
|
|
2. Authenticating with the Loyalty Code
In this scenario, guests do not pre-select any rewards and instead start their journey by scanning their Loyalty code at the POS. The guest in this scenario does a second scan to add a reward after the initial identification. The guest then adds a following reward from the Kiosk UI to the basket.
This scenario assumes that the market allows for multiple rewards to be redeemed in the same order
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest opens the Loyalty code page on the RBI app |
|
|
|
Guest taps on the Kiosk screen to start a new order |
|
|
|
Guest scans the loyalty code or inputs 6 digit code in Kiosk |
|
|
|
Guest opens an reward on the RBI app, chooses to redeem in restaurant |
|
|
|
Guest either scans the reward’s QR code or inputs 6 digit code into Kiosk |
|
|
|
Guest customizes reward(s) at will and adds to basket |
Note: If a reward can’t be redeemed because the reward rules are not met, the Kiosk displays a modal to the guest explaining why the reward can’t be added to cart |
|
|
On the Kiosk UI, navigates to the rewards page Note: this step is only possible if the market has decided to allow showing rewards on the UI. |
|
|
|
Guest adds a reward to basket |
|
|
|
Guest removes a reward from basket |
|
|
|
Guest goes to checkout screen |
Note: If an reward can’t be redeemed because the reward rules are not met, the Kiosk displays a modal to the guest explaining why the reward can’t be added to cart |
|
|
Guest checks out and pays |
|
|
|
3. Using reward pre-selection
In this scenario, guests pre-select rewards on the RBI app and continue their journey in the Kiosk by scanning the generated code. Then they add another reward directly in the kiosk screen, and finally they remove one of the added rewards before checking out.
This scenario assumes that the market allows for multiple rewards to be redeemed in the same order
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest opens a reward on the RBI app |
|
|
|
Guest taps “Redeem in Restaurant” |
|
|
|
Guest taps on the Kiosk screen to start a new order |
|
|
|
Guest either scans the reward’s QR code or inputs 6 digit code into Kiosk |
|
|
|
Guest opens a second reward on the RBI app, chooses to redeem in restaurant Note: the flow is exactly the same if the guest pre-selects multiple rewards. |
|
|
|
Guest either scans the second reward’s QR code or inputs 6 digit code into Kiosk |
|
|
|
Guest customizes reward(s) at will and adds to basket |
Note: If a reward can’t be redeemed because the reward rules are not met, the Kiosk displays a modal to the guest explaining why the reward can’t be added to cart |
|
Check if needed:
|
On the Kiosk UI, navigates to the rewards page Note: this step is only possible if the market has decided to allow showing rewards on the UI. |
|
|
|
Guest adds a reward to basket |
|
|
|
Guest removes first reward from order |
|
|
|
Guest goes to checkout screen |
Note: If an reward can’t be redeemed because the reward rules are not met, the Kiosk displays a modal to the guest explaining why the reward can’t be added to cart |
|
|
Guest checks out and pays |
|
|
|
4. Limit one reward per purchase
This scenario only happens if the market has decided to limit redemption of one reward per purchase. This is currently the case in PLK ES and BK ES for example.
Steps | Expected results (Kiosk) | Expected results (RBI app) | Loyalty API usage (Kiosk) |
---|---|---|---|
Guest opens a reward on the RBI app |
|
|
|
Guest taps “Redeem in Restaurant” |
|
|
|
Guest taps on the Kiosk screen to start a new order |
|
|
|
Guest either scans the reward’s QR code or inputs 6 digit code into Kiosk Note: the pre-selected reward(s) will show in the Kiosk screen after scanning with an option for the user to customize it |
|
|
|
Guest customizes reward at will and adds to basket |
Note: If a reward can’t be redeemed because the reward rules are not met, the Kiosk displays a modal to the guest explaining why the reward can’t be added to cart |
|
|
Guest opens a second Reward on the RBI app, chooses to redeem in restaurant |
|
|
|
Guest taps Replace |
|
|
|
Guest either scans the reward’s QR code, or tells the 6 digit code to the cashier |
|
|
|
On the Kiosk UI, navigates to the rewards page Note: this step is only possible if the market has decided to allow showing rewards on the UI. |
|
|
|
Guests selects reward in Kiosk screen |
|
|
|
Guest clicks on Replace reward |
|
|
|
Guest goes to checkout screen |
Note: If an reward can’t be redeemed because the reward rules are not met, the Kiosk displays a modal to the guest explaining why the reward can’t be added to cart |
|
|
Guest finalizes the order and pays at Kiosk |
|
|
|
Next: Kiosk - Edge Cases