RedHub AIRedHub AI
Tool Gate · How it works

How the roll-up gate works

How the Duplicate & Near-Duplicate Finder gate works

This tool grades one list for exact copies and sneaky near-matches before you double-count or double-pay. It reads 7 records and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.

The 7 records

01Row 3 · Jane Doe, jane.doe@acme.comfix firstexact email-key match to row 1DUPLICATE
02Row 4 · Jane M Doe, jane.doe@mail.acme.comshares phone with row 1, key differsREVIEW
03Row 1 · Jane Doe, jane.doe@acme.comfirst occurrenceUNIQUE
04Row 2 · Bob Smith, bob.smith@widgetco.iono prior matchUNIQUE
05Row 5 · Carla Nguyen, carla.n@northstar.cono prior matchUNIQUE
06Row 6 · Dmitri Volkov, d.volkov@orbit.devno prior matchUNIQUE
07Row 7 · Priya Patel, priya@lumen.studiono prior matchUNIQUE
CLEAN
every record reads UNIQUE
NEEDS REVIEW
worst record shares a field with a different key, no exact match
HAS DUPLICATES
any record is an exact key match to an earlier row
Exact-key duplicate · worsen-only

An exact email-key match to an earlier record is a DUPLICATE no matter what else differs, and a shared name or phone with a different email is only a REVIEW - but one DUPLICATE is enough to hold the whole batch at HAS DUPLICATES, whatever share of records are otherwise unique.

HAS DUPLICATES

Why: Five of seven records are unique and one is a near-match worth a review - a mail-relay alias for Jane Doe sharing her phone number. But row 3 is an exact email match to row 1, so it's a DUPLICATE outright. Batch status is the worst record, never the average, so it reads HAS DUPLICATES. 1 of 7 records exact-duplicate · 1 review · worst-not-average.

Fix firstRow 3, the second jane.doe@acme.com - merge it into row 1 before touching the review; an exact key match is the least ambiguous call in the set.

No single record is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Matches on the fields you provide using exact and shared-field rules; it does not merge records for you and does not identify people beyond the data given.