2005 - 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 disadvantaged 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?
- Admin could give a flag to User profile
- Navigate to the user management section.
- Search for the user's profile based on criteria (e.g., email, username).
- Select the option to flag the user for exploiting the booking system.
- Confirm the action to flag the user.
- Admin could remove Flag from User Profile
- Navigate to the user management section.
- Search for and select the flagged user's profile.
- Select the option to remove the flag from the user's profile.
- Confirm the action to remove the flag.
FAQ & Considerations
Are any questions related?
Timeline
Sprint TBD