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.
Info |
---|
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
...
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 Info |
---|
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 | Image RemovedImage Added Info |
---|
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
...
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 | | | Keep track of the current basket contents including rewards Call the Identify endpoint again, which will create a new transaction ID and return selected reward(s) Void the previous transaction Wait for Void Confirmation Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
Guest customizes rewards at will and touches confirm | These Guest customizes reward(s) at will and adds to basket | Info |
---|
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 |
| | 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. Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
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. |
| | | |
Guest adds a reward to basket | | | 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. Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
Guest remove removes a reward from basket | | | 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. Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
Guest goes to checkout screen | Info |
---|
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 |
| | Call the Transaction Validate endpoint to verify that the current basket selection is valid If Transaction Validate was called above when rewards were added to the basket, there is less probability of errors but they could still happen due to issues with regular menu items. Note that the call above may return errors. Please refer to Loyalty API - Error List for details.
|
Guest checks out and pays | | | |
...
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 more rewards to their basket by choosing those rewards in the app and scanning themanother reward directly in the kiosk screen, and finally they ask the cashier to remove one of the added rewards before checking out.
Info |
---|
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 | | | 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 | Image Removed | | |
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. |
| | | |
Guest either scans the second reward’s QR code or inputs 6 digit code into Kiosk | | | Keep track of the current basket contents including rewards Call the Identify endpoint again, which will create a new transaction ID and return the selected reward(s) Void the previous transaction Wait for Void ConfirmationCall the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
Guest customizes rewards reward(s) at will and touches confirm These adds to basket | No action | | Info |
---|
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 |
| | 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. Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
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. |
| | | |
Guest adds a reward to basket | | | 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. Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
Guest removes first reward from order | | | 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. Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
Guest goes to checkout screen | Info |
---|
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 | | | |
...
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 Info |
---|
Note: the pre-selected reward(s) will show in the Kiosk screen after scanning with an option for the user to customize it |
| | | Call the Identify endpoint, which will return the Loyalty User ID, the pre-selected reward, the loyalty points balance and a transaction ID
|
Guest customizes rewards reward at will and touches confirm These reward(s) are adds to basket | Info |
---|
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 | | The replaced reward’s loyalty points are returned to user balance The new reward’s loyalty points cost is temporarily subtracted from the guest’s loyalty points balance Loyalty points that will be accrued after the order will not be added to the guest’s loyalty points balance at this stage Reward pre-selection is cleared
| Keep track of the current basket contents including the past scanned reward Call the Identify endpoint again, which will create a new transaction ID with the new reward Void the previous transaction Wait for Void Confirmation Replace the previous reward in the basket with the new reward Call the Update endpoint with all of the Kiosk basket contents and a status of PENDING
|
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. |
| | | |
Guest adds a reward to basket | Guest selects and adds reward to cart Guests selects reward in Kiosk screen | | | |
Guest clicks on Replace reward | | | |
Guest goes to checkout screen | Info |
---|
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 | | | |
...