Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for crm managers

Marketing Lead Data Repair Agent

Clean, deduplicated lead imports with a reversible repair log.

Marketing Lead Data Repair Agent: what goes in, what the agent does and what you get

What it does

Malformed lead data, such as bad emails, wrong campaign IDs and duplicates, ruins sales follow-up and reporting. Before an import, this agent checks every field against the CRM schema and fixes only the fields it is allowed to normalize, like casing, country codes and phone formats. It looks for records that seem to be the same person. It merges only when they share verified identifiers, and sends the rest to review. All repairs go to a staging list with an undo log, and record counts must match before and after. The CRM administrator approves the import and any merge. Edge case: two leads share a surname and company but have different verified emails, so they stay separate.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueApprovedNo 1 STARTS WHEN Lead file ready 2 USES A TOOL Validate fields against the CRM schema 3 DOES Normalize allowed fields 4 CHECKS THE RESULT Do apparent duplicates share verified identifiers? If not: keep separate and send to review. Back to step3. 5 USES A TOOL Write repairs to staging and reconcile counts 6 YOU APPROVE CRM administrator approves the import and merges 7 RESULT Validated lead import and repair log
Read the steps as a list
  1. Lead file ready
  2. Validate fields against the CRM schema
  3. Normalize allowed fields
  4. Do apparent duplicates share verified identifiers?If not: keep separate and send to review. Back to step 3.
  5. Write repairs to staging and reconcile counts
  6. CRM administrator approves the import and mergesThe agent waits here for your OK.
  7. Validated lead import and repair log

How it decides

It repairs from schema rules and never merges records with conflicting verified identifiers.

  • Merge only when records share a verified identifier.
  • Record counts must reconcile exactly before import.
  • Every repair is written to staging with an undo entry.

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Fields the agent may normalize
  • Which identifiers count as verified (default email and CRM ID)
  • Count tolerance (default zero difference)
  • Reviewer for ambiguous merges

What keeps you in control

It always asks you first

  • Production merges
  • Outreach
  • Collecting new personal data

Hard limits

  • Staging only.

It stops when

  • Done: import ready.

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensA trade-show file with 1,240 leads arrives on 12 September. The agent fixes 85 phone formats and 31 campaign IDs. It finds 46 apparent duplicates. The identifier check fails for 9 pairs with different verified emails, so those go to review. Count reconciliation first shows 1,203 versus 1,204; it finds a dropped row and restores it. The CRM administrator approves 37 merges and the import.

More agents for crm managers