Resolving conflicting evidence in database verification calls

Describe the conflict at field level

A record is not simply correct or incorrect. Its phone number may be current while its job title is stale; its website may show a new office while the billing system retains the valid legal address. Verification should identify the exact field, competing values, sources, timestamps, and intended use. Broad labels such as bad data hide what must be decided.

Distinguish a source observation from an approved database value. A caller can observe that a number reaches a shared reception desk, hear a contact state a new title, or see a returned email. Those facts become evidence. They do not automatically authorize edits to identity, ownership, consent, legal, or financial fields.

Preserve the old value while the conflict is open. Deleting it removes the comparison point and can break connected records. Use a pending value or conflict object that records the proposed change without presenting it downstream as settled truth.

Apply a field-specific evidence hierarchy

Source authority varies by field. An official account administrator may control billing contacts; the individual may control their communication preference; a public website may support an office switchboard but not a private direct number. Write precedence rules for each material field and include recency, identity confidence, and whether the source is authorized to make the claim.

When strong sources disagree, do not choose the newest automatically. A recent scraped page can be less authoritative than an older verified account instruction. Compare the purpose and stewardship of each source. The data owner should define when recency breaks a tie and when direct review is required.

Unknown and disputed should remain valid states. Forcing a final value encourages callers to select something merely to complete the task. Downstream systems need to know whether they may continue using the prior value, pause contact, or route work to an owner while the conflict remains unresolved.

Collect verification evidence without leading the answer

The caller should not read every competing value and ask the contact to pick one. That can disclose old personal information and bias the response. Use the approved identity step, ask an open or minimally revealing question, and record the answer in the person’s words. Confirm only the portion necessary for the field and task.

Shared lines, assistants, receptionists, and group mailboxes require attribution. They may know routing information but lack authority over a person’s role, consent, or account ownership. Record who provided the information and the relationship they described. Do not attach another person’s confidence to the subject of the record.

If the interaction creates a new conflict, preserve it. A person may state that the company website is wrong, while an account administrator later disagrees. The caller should not defend one source or pressure the contact. Route the evidence and avoid further use that the safe-state rule prohibits.

Control approval, propagation, and rollback

Low-risk formatting changes may be applied automatically, while material changes need a steward. Define thresholds using sensitivity, downstream reach, reversibility, and business impact. Changing a phone label can be minor; changing an account owner or suppression state can affect many systems and communications.

When approved, update the authoritative system first and propagate with an event or controlled job. Record which consumers succeeded. Partial propagation should create an exception with an owner, not a misleading completed state. Keep enough history to roll back an incorrect change without restoring unrelated stale data.

Audit both approvals and rejections. Check evidence quality, rule version, approver, before and after values, connected-system results, and later corrections. Track conflicts by field and source pair, time unresolved, false overwrite, rollback, and repeat verification. These patterns reveal where integrations or stewardship need repair.

Use a scenario test before launch: the website lists headquarters, the CRM lists a branch, a receptionist gives a remote number, and the named contact says they changed companies. Ask the caller to separate observations, identify protected fields, choose the safe interim state, and route each decision. The saved record should let a steward reproduce every conclusion.

Design the reviewer queue around decision risk

Prioritize conflicts by likely harm and downstream reach rather than by arrival order alone. A disputed punctuation style can wait; an uncertain suppression state, legal identity, account owner, or payment destination may require immediate containment. Show the reviewer which processes consume the field and whether any outbound action is already scheduled from the disputed value.

Set service targets for review without pretending every conflict can be solved quickly. The target can require acknowledgment, a safe interim state, and a named owner before it requires final truth. Some evidence depends on an external administrator or the subject of the record. Report pending dependency separately from unattended work so managers do not pressure stewards into unsupported closure.

Publish a short decision note after resolution. It should cite the accepted value, rejected alternatives, governing evidence rule, effective time, systems changed, and any future verification date. This helps later callers understand why one source prevailed and prevents the same conflict from reopening simply because another import repeats the losing value.

Protect the conflict workflow from bulk imports. A nightly file should not overwrite a steward-approved value without evaluating source authority and effective time. Quarantine repeated losing values, alert the source owner, and preserve how often the conflict recurs. Recurrence can reveal that the upstream system, not the verified contact, needs correction. Until that source is repaired, the release process should prevent its lower-authority value from reappearing in calling lists.

Give callers a way to see resolved conflicts without exposing restricted evidence. A concise marker can show the approved value, decision date, steward, and next review point while detailed documents remain access-controlled. If the contact supplies genuinely new evidence, the caller opens a new review rather than deleting the earlier decision. This preserves accountability while allowing records to change when reality changes.