[GoodID-flow] Segmentation Dispute

patpedrosa commented 7 months ago

Business Description

What the feature is and why we're doing it (business & user benefit)

Our automated checks will populate the user's GoodID with data that may not be accurate or match the user's preferences. The Dispute functionality allows the user to indicate if the automated check as returned a result with which they disagree. Potential examples include:

users identified by the system as one gender but with a different gender identity, or
users located by the system as being located in a country they are not in (e.g. due to IP re-routing).

With the Segmentation Dispute, the user is able to indicate which segmentation values are incorrect and provide a suggested response.

Users may dispute:

Gender
Age
Location By selecting an alternate value via a drop-down. Drop-down values below images.

Drop-down values:

See this notion page!

Disputed items display as "Unverified-[name of type-field]" in the user's GoodID (a gray GoodDollar badge) on the Confirmation screen (see #4200 and subsequently in their "GoodID" view area (e.g. "GoodID" in the GoodDapp).

Dispute does not affect eligibility of users who were previously identified as eligible or ineligible. Only G$ Verified methods determine eligibility.

Technical Design

Disputes are not stored, however are tracked via an Amplitude event that corresponds to the GoodID (for troubleshooting) Dispute values are also tracked

Technical Implementation

[x] - Add the screens to the SegmentationWizard on step 2 and 3
[x] - Add goToSteps wizard handlers to navigate a user to the approriate screens
[x] - A user should go to step 2 when clicking on 'No, I am not' button on the SegmentationScreen
[x] - A user should go to step 4 or 5 when clicking on 'Yes, I Am' following the existing logic seen here: https://github.com/GoodDollar/GoodWeb3-Mono/pull/136

Wallet-Implementation: TBA Dapp-Implementation: TBA

Design Reference

Figma: https://www.figma.com/file/ihw1PxBvLxacTHnN2aj4lC/3.-Product?type=design&node-id=13532%3A19695&mode=design&t=PjmtdwLycc9FSyi0-1 (Preview-Mobile)

L03TJ3 commented 7 months ago

@patpedrosa are you saying here we don't do anything with the disputed data, just.. don't store it?

decentralauren commented 6 months ago

Open Items

[x] Where and how are disputed values stored?
[x] Update UI with new copy
[x] What is a reasonable dispute process for MVP? Maybe use videos as part?
[x] Can people who dispute still be eligible for the MVP offer?

patpedrosa commented 6 months ago

@drptiago Can you please review your data architecture plan for the dispute case?

drptiago commented 6 months ago

Dispute / GoodID Declined Steps from here

After goodid_declined

Any suggestion here is valid, but I think to trigger one event to each info changed

goodid_gender_dispute -> when change the gender goodid_age_dispute -> when change the age goodid_country_dispute -> when change the country goodid_dispute_confirm ->-> when click in "NEXT"

decentralauren commented 5 months ago

[ ] Update UI and offers logic for disputed GoodID (all disputes are automatically ineliglble) [ ] Implement Post-hog survey modal for capturing dispute values

@decentralauren

decentralauren commented 4 months ago

@sanajamm can you please update this ticket with the new figma file and screen shot?