Resolve cross-tool contact and sequence conflicts

Why use this

1. A sales team may have the same person represented differently across contact and sequencing systems. A correction in one place can leave another system poised to send duplicate or inappropriate outreach.

2. This job could reconcile evidence into an unsent correction queue, with uncertain identity and sequence conflicts held for review. Preserving the human send decision keeps data cleanup from silently becoming a communication campaign.

Why an agent / simpler alternative

Useful judgment

Compare identities and sequence states, detect conflicts and distinguish safe field reconciliation from uncertain merges.

Simpler alternative

Use one authoritative CRM report when all systems share stable IDs and synchronized status.

Unsuitable when

The task would merge uncertain people, override opt-outs or trigger outreach without explicit authorization.

Proposed inputs

1. Name

   Contact snapshots

   Owner

   Authorized sales operations owner

   Minimum scope

   Necessary IDs, business details and sequence states

   Quality check

   Check source dates and unique identifiers

2. Name

   Reconciliation rules

   Owner

   Owner

   Minimum scope

   Authoritative fields, exclusions and allowed staging behavior

   Quality check

   Preserve suppression and do-not-contact flags

Access and setup — proposed or unknown

Proposed minimum

1. Use redacted or synthetic snapshots and a proposed reconciliation table; no live edits, enrolments or sends.

Compatibility unknowns

1. Current cross-tool identifiers, sync behavior, staging support and runtime compatibility are unknown.

External actions requiring approval

1. Record changes, sequence reassignment, data sharing and communications require approval; unresolved edge cases remain held.

Expected deliverable and review checks

Proposed artifact

Unsent correction queue with old/new values, identity evidence, sequence conflicts and reviewer decisions needed.

Critical checks

1. Honor suppressions; distinguish duplicate records from similar names; verify changes will not auto-trigger a sequence.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   Two people share a name and company

   Why it matters

   An incorrect merge can misroute outreach

   Proposed response

   Require stronger identity evidence and hold both records.

2. Signal

   A staged correction activates a sequence

   Why it matters

   Data maintenance produces an unintended send

   Proposed response

   Inspect side effects and choose a nontriggering proposal path.

Effort and cost — unknown

Setup work

1. Define authoritative fields and send-prevention boundaries.

Ongoing review

1. Owner reviews conflicts and separately controls any outreach.

Unknowns

1. Sync delays, trigger behavior, identity quality and service costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent records across three systems with a similar-name conflict, mismatched sequence and suppression flag; propose corrections only.

Acceptance checks

1. Hold uncertain identity; preserve suppression; flag send triggers; enrol or message nobody.

Stop conditions

1. Stop if identity, authority or mutation side effects are unresolved.

Limits

1. Reconciled records cannot establish consent, buying interest or permission to contact a person.