...
Steps | Expected Outcome | Comments |
---|---|---|
Customer support compliance agent blocks customer account on Admin tool |
|
|
Customer opens the WL app or web, to Sign-in/ Sign-up |
|
|
...
Steps | Expected Outcome | Comments | ||
---|---|---|---|---|
Customer support compliance agent blocks customer account on Admin tool |
|
| Same as 1.1. scenario | Same as 1.1. scenario |
Customer opens the WL app to place an order If the logoff process already happened (can take up to one hour), the customer receives an error message, informing that the account has been blocked. | If the account is still logged in, the customer can use the app regularly:
|
|
...
Steps | Expected Outcome | Comments | |
---|---|---|---|
Customer support compliance agent blocks customer account on Admin tool |
| New role with permission to block customer accounts. New blocking button available on admin tool. Force customer account logoff process. Email notifications configured on sanity. Same as 1.1. scenario | Same as 1.1. scenario |
Customer places an order on Kiosk or directly on POS |
|
| |
Customer opens the WL app to generate the OTP code to access the account If the logoff process already happened (can take up to one hour), the customer receives an error message, informing thatthe account has been blocked. |
|
| |
Customer proceeds to place the order |
|
...
Steps | Expected Outcome | Comments | ||
---|---|---|---|---|
Customer support compliance agent blocks customer account on Admin tool |
|
| Same as 1.1. scenario |
|
Customer places an order on call-center |
|
|
...
Steps | Expected Outcome | Comments |
---|---|---|
Customer support compliance agent unblocks customer account on Admin tool |
|
|
As the account was necessarily logged-off, when the customer opens the WL app or web must log-in |
|
|
...