Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
You check sources, rules and decisions. ChatGPT drafts only from the checked material.
Prepare the checked inputs
Draft per-pair consent histories
Check pairs and history completeness
Draft proposals and conflict log
Approve or hold
Use: You
Have ready: the lead list with confirmed duplicate pairs, the consent capture records per source and the approved merge policy.
Use: ChatGPT
Ask ChatGPT for source, purpose, channel, status and date histories, with gaps marked.
What to paste into the tool
Task: Per-pair history table with gaps marked. For each pair ID, list each record's source, capture context and consent status per purpose and channel with date. Mark any purpose or channel where history is missing. Do not infer consent.
Use: You
Check each pair is the same person and histories are complete per purpose and channel. Mark incomplete pairs.
Incomplete history means no merge is proposed for that pair.
Use: ChatGPT
Apply only supplied precedence per purpose, channel and date to checked pairs; keep unresolved conflicts unmerged in a conflict log.
What to paste into the tool
Task: Merge proposals and conflict log. Apply only the attached precedence rules. Where the rules do not resolve a purpose or channel, keep both records' consent separate and add it to the conflict log. Keep lineage of both source records on every survivor. Never write one merged consent status.
Use: You
Decide every conflict the policy does not resolve and approve the proposal set for import by a person.
Decide every conflict the policy does not resolve and approve the proposal set for import by a person. No merged permission is proposed for an unresolved purpose or channel. No CRM record is changed and no contact is made by this workflow.
Gemini joins consent histories. You check pairs, apply policy by formula, decide conflicts and approve proposals.
Prepare the checked inputs
Join both consent histories
Check pairs, enter rule table
Apply rule table, log unmatched
Approve or hold
Use: You
Have ready: the lead list with confirmed duplicate pairs, the consent capture records per source and the approved merge policy. Load the pair list and consent records as separate tables with pair ID, source, purpose, channel, status and date.
Check every pair ID and date survived the load.
Use: Gemini
Ask Gemini to show both records' consent per purpose, channel and date side by side.
What to paste into the tool
Task: Both records' histories side by side. Use only the consent table I supply. Do not fill missing cells.
Use: You
Check each pair against sources, same-person identity and completeness. Enter precedence as a rule table by purpose, channel and date.
Incomplete history means no merge is proposed. Test the rule table against the policy text on known-outcome pairs.
Use: You
Apply the rule table by sheet formula; anything with no matching rule goes to the conflict log unmerged.
No merged permission for an unresolved purpose or channel.
Use: You
Decide every conflict the policy does not resolve and approve the proposal set for import by a person.
No CRM record is changed and no contact is made by this workflow.
You check sources, rules and decisions. Claude drafts only from the checked material.
Prepare the checked inputs
Draft proposals using the policy
Approve or hold
Use: You
Have ready: confirmed duplicate pairs and consent capture records. Build histories by hand by purpose, channel and date, marking gaps.
Check same person and completeness per purpose and channel; incomplete pairs get no merge proposal.
Use: Claude
Store the policy in a Claude project; ask for merge proposals and a conflict log from the reduced history table.
What to paste into the tool
Task: Draft proposals and conflict log. Apply only the policy in project knowledge. Keep both records' consent separate where the policy does not resolve a purpose or channel. Keep lineage of both records. Do not write a single merged consent status.
Use: You
Check every proposal against the policy and table, decide unresolved conflicts and approve the proposal set for import by a person.
No CRM record is changed and no contact is made by this workflow.
Best when: You want drafting, file analysis and web research together
What it does: ChatGPT drafts; you check sources and decide
Strong at: Writes and summarises text; analyses files and searches the web
Limit: Free plan limits uploads, images, voice and data analysis
Free plan: Yes, limited; uploads and data analysis capped
Best when: You want data work within a spreadsheet
What it does: Gemini joins histories; you apply policy and decide conflicts
Strong at: Analyses spreadsheet data from plain-language requests
Limit: The free plan has usage limits
Free plan: Yes
Best when: You want text drafted and edited from supplied material
What it does: Claude drafts; you check sources and decide
Strong at: Drafts and edits text; summarises documents and analyses images
Limit: Usage capped in 5-hour and weekly windows
Free plan: Yes, limited; usage resets every five hours
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Deciding between ChatGPT and Claude for this? See the comparison.
Every option applies the supplied precedence per purpose, channel and date, keeps both records' lineage, and leaves unresolved conflicts unmerged for the privacy owner.
Nothing is merged, sent or changed in the records until you approve the proposals.
Check the result against your original inputs. Approve it before sharing or acting.