Verification
Check field values against an external source, so a field is trusted because it is true rather than because it is filled in.
Values that were right once. The phone number worked in 2023. The website redirects to a company that acquired them. The address is a floor they moved out of. Nothing about the record looks wrong, because a stale value and a correct one are the same shape.
Every other tool here makes the CRM internally consistent. Verification is the one that asks whether it still agrees with the world.
Filled in is not the same as correct, and no completeness measure can tell the difference. A field that has held the same wrong value for two years scores as well as one that is right.
Checking is not correcting. Verification reports what disagrees with the source, and what happens next is a decision: correct it, clear it, or flag the record for somebody to look at.
How a pass runs
The detail
Three answers
Collapsing them is how verification tools destroy good data.
A source that has never heard of a phone number has not told you the number is wrong. It has told you nothing. A tool that treats silence as contradiction will clear correct values across a whole book, and the damage is invisible because the fields it emptied were the ones nobody was looking at.
So confirmed, contradicted and unknown stay three separate answers all the way through, and only one of them is a reason to change a record.
For agents
Reads are free and need no permission to write. Anything that changes a record is a separate grant.
list_filterable_fields the fields available to check readdispatch_run start a verification run writeWhere to start
The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.