I'm stuck with a problem that has me stumped.
Context: I'm working on a dashboard which gives details about the breakdown of a user's data.
Here's the basic workflow:
1. User Uploads data- Emails and Phone numbers.
2. We then match the emails and phone numbers against our database and show number of matches we found. These are "Actual Matches". An email and phone matched to 1 user makes 1 Actual record.
3. Then, we derive and determine a few things from the matched data. This could be from parter databases, etc. This leads to more matches. These are "Output Matches".
4. Finally, we offer an option to integrate with a 3rd party product which can further increase the matches.
Here's the solution I came up with:
1. I'm unsure if this is understandable for the user. Especially the breakdowns- 100 Emails and 100 Phones only total to 100 Actual matches because they belong to the same record. That is, 1 Phone and 1 Email make 1 Actual record only if they belong to the same record. So, 100 Emails and 50 Phones would have only 50 as the highest possible Actual matches. A lot of users think that the Actual matches is a total of the two. How do I better represent this data?
2. I want to convey to the user that their "Records Uploaded" has gone through layers of matching and computations. To the users, the current view seems like separate entities. How do represent this better?