Guest looks at the Kiosk screen

• A page shows up inviting the guest to start an order

• N/A

• No action

Guest touches the screen to start a new order

• Guest is prompted to sign in

• No action

• No action

Guest decides to continue without signing in

• Kiosk order screen show up. This screen does not show either offers or rewards tabs

• Guest can sign in at any time by using the scanner or touching a sign in button

• No action

• No action

Guest taps on the Coupons tab

• Guest is prompted to sign in.

Image Added

• No action

• No action

If, instead of signing in, the guest clicks in “I have a code”, the guest will be able to input a short code for open offers.

(Example: campaigns that do not involve loyalty but offer a coupon)

• No action

• No action

After signing in, the guest will see a page with all offers available for him displayed

• Guest sees a list of offers. If offers are closed, they show up as “Sign in to redeem” and there is a clear way for guests to sign up to use them. If offers are open and the market has decided to show open offers, then it should be possible for guests to add them to their basket.

Image Removed

Offers are displayed:

Image Added

• No action

• Listing Global Offers Listing Offers and Rewards for Kiosk UI

Guest opens the RBI app without signing in, and selects an offer that is available when users are signed out (known as a “open offer”)

• Offer page is displayed to be scanned:

  Image RemovedImage Removed

• No action

Guest scans offer (static) alphanumerical code

• Offer is added to the basket

• If the offer was configured for single redemption use, it will disappear from the app after 15 minutes

• For static codes, we don’t show a confirmation in the RBI app

• No actionListing Personalized OffersPersonalized Offers Integration

Guest selects an offer

• Details displayed

Image Added

• 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

• 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

Image Removed

Image Added

• Receipt is printed

• Ideally, guests would be shown the number of points they could have earned, and they are prompted to sign up

• No action 

• No action

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

• Guest sees updated points balance

Image Added

• 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

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

• No action

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

• 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 (keeping basket information)

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

• Update the basket with the offers returned

Guest customizes offer(s) at will and adds to basket

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

• No action

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

On the Kiosk UI, guest navigates to the offers Coupons page

Offers are displayed:

As the user is already signed in, there is no prompt to sign in on the locked offers.

• No action

• Listing Global Offers Listing Offers and Rewards for Kiosk UI

• Listing Personalized Offers Personalized Offers Integration

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

• 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