...
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage | |
---|---|---|---|---|
Guest opens the RBI app without signing in, and selects an offer that is not available when users are signed out (known as a “closed offer”) |
|
| ||
Guest taps “Use at restaurant” |
|
| ||
Guest is worried about his privacy and decides not to use this offer. Guest opens an offer that is available when users are signed out (known as an “open offer”)
|
|
| ||
Cashier is prompted to add a loyalty code |
|
| ||
Guest either scans the (static) offer code, or tells the alphanumerical code to the cashier |
|
|
| |
Guest opens a second offer that is available when users are signed out (known as an “open offer”) |
|
|
| |
Guest either scans the (static) offer code, or tells the alphanumerical code to the cashier |
|
|
| |
Cashier finalizes the order and guest pays at POS | POS Cashier finalizes the order and guest pays at POS |
|
|
|
1.2. Authenticating with Loyalty Code
...
Steps | Expected results (POS) | Expected results (RBI app) | Loyalty API usage |
---|---|---|---|
Guest opens the Loyalty code page on the RBI app |
|
|
|
Cashier is prompted to add a loyalty code |
|
|
|
Guest either scans the loyalty code, or tells the 6 digit code to the cashier |
|
|
|
Guest opens an offer on the RBI app, chooses to redeem in restaurant |
|
|
|
Guest either scans the offer’s QR code, or tells the 6 digit code to the cashier |
|
|
|
Cashier finalizes the order and guest pays at POS |
|
|
|
| |||
|
1.3. Using offer pre-selection
...