...
Info |
---|
What is the context and status quo of the opportunity |
When the customer places orders through the kiosk in the restaurant, the order can be associated to their account.
In this case, in the POS system, the customer account is identified through the Loyalty ID.
If there is any customer support request related with these transactions, searching for the Loyalty ID is the only way to do it. This is the only common identifier between the Admin tool and the POS tool.
Request ID:
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
🎯 Problem Statement
Info |
---|
Summary of the opportunity's main findings and what is going to be addressed |
The loyalty ID is the only common identify between the Admin tool and the POS system.
The most common and relevant use case:
The restaurant employee register customers orders with the same loyalty ID, when the customer doesn’t inform or require that a certain order is associated to their account. In these cases, the management team might find a suspicious behavior when there are too many transactions associated to a specific loyalty ID in the POS system. In order to find out the ID associated to the Loyalty ID, the admin tool must be used and the only common identifier is the Loyalty ID. Searching by Loyalty ID allows the identification of the fraudulent employee.
❔ Expected Outcome
Info |
---|
What are the goals the opportunity is going to address |
...