What pipeline hygiene actually means to an agent

"Keep the CRM clean" is uselessly vague as an instruction to an agent, because cleanliness is not one thing. Break it into six jobs the agent can each be measured on, and you can actually wire them.

• Deduplication , the average company runs 20-30% duplicate contacts, leads and accounts, and duplicates alone overstate pipeline by roughly that much. The benchmark to aim for is under 5%. An agent matches on fuzzy signals (domain, normalised company name, email) and merges or flags.
• Enrichment , filling the blank fields that make a deal unroutable and unforecastable: missing close date, blank deal owner, no next step, empty stage. When the majority of records are incomplete, the forecast is built on guesses.
• Standardisation , one spelling of every value. "Closed Won", "closed-won" and "Won" are three rows to a pivot table and one outcome to a human.
• Decay detection , flagging records that have gone stale. Email addresses decay at around 3.6% a month, so the agent re-verifies rather than trusts a six-month-old contact.
• Stage integrity , catching deals whose stage and activity disagree (stage 4, zero meetings logged).
• Phantom culling , surfacing deals with no activity inside a threshold so a human can kill or revive them.

Not every job is the agent's to do silently. Draw a hard line. Deterministic, reversible corrections the agent does autonomously: standardising a picklist value, merging an obvious duplicate, filling a close date from the contract. Judgement calls the agent surfaces for a human: killing a 60k deal, changing a forecast category, reassigning an owner. The rule of thumb is the one good operators use for any automation, if it is reversible and unambiguous, automate it; if it is irreversible or contestable, the agent prepares the decision and a human makes it. An agent that silently deletes deals will be switched off within a week, and rightly so. The full mechanics of each job live in the CRM data hygiene playbook; here the point is that hygiene becomes wirable only once you decompose it into named, measurable rules.