1023 - User Flagging
Overview
| Product Name | User Flagging |
|---|---|
| Epic | User Flagging Feature for Abusive Booking Prevention |
| Team Channel | |
| Product Manager | [@Umam Syarief](javascript: void;) |
| Designer | [@Scene](javascript: void;) |
| Engineer | |
| QA Engineer | [@team-qa](javascript: void;) |
| Technical Writer |
Objective
Implement a User Flagging feature within the platform to address fraudulent user behavior, prevent fake bookings, and ensure a more transparent and secure booking process for all parties involved.
Background
Instances of fraudulent user behavior, such as fake bookings and no-shows (from the restaurant), have been identified as significant issues affecting the platform. These actions lead to dissatisfaction especially for restaurants. The implementation of a User Flagging feature aims to mitigate suspicious activities and enforce prepayment measures as a preventive measure.
Possibilities
Gain
- Lead to a safer and more respectful environment
- Help restaurants to reduce the disadvantage behaviour from the users
Pain *
Goals & Success Metrics
What are the goals or objectives of this product? What are success metrics that indicate the goals have been achieved?
- Flagged User could only make booking with Pre-Payment method
- The flagged user attempts to make a booking
- By default, "Pay Now" switch button always turn on
- The user won't be notified about his/her flag status
FAQ & Considerations
Can user request to remove the flag status?
For the worst case, The user feels he/she has tried all the restaurants but all of them still use the pre-payment method. He/she can contact CS to confirm this issue. but user won't know about his/her status
if a restaurant only have pay on site option and doesn't want pre payment how would the user proceed the booking?
only packages with pre payment option can be forced to pre payment/ if it doesn't have one, it should still be on pay on site
Timeline
Sprint TBD