To allow for the best review of possible matched records, we set our exact match threshold very high. This is particularly useful when we are bringing in records with limited contact info but there are other data points we can use to enhance a match (alumni status or class year, donor interests, etc).

However, what we are left with are many records with either a single possible match or multiple possible matches but one obvious choice based on an enhanced match score that was applied by a pre-processing dynamic operation. The only way to turn such choices into an Exact Match is to open the form for every record, select the match, and save it.

It would be great to have either a record op on the Constituent Matching Results or an action for a staged data instance that allows inputs of a new Exact Threshold that can be run on staged data that will turn possible to exact matches. Making such matches an exact match should apply the defaults from the job configuration for Constituent Update Rules.