Smart views filter on missing fields
01The views your team works from depend on custom fields Clay never fills, so the queue is a partial picture of the real lead pool.
← Stack fixes
Enrichment → CRM
Fix the Clay → Close handoff
Close runs on lead statuses and smart views. If Clay's enrichment doesn't land as clean fields, every smart view filters on data that isn't there.
Where it breaks
What goes wrong between Clay and Close
Lead statuses don't reflect enrichment
02Qualified and unqualified leads carry the same status because nothing translates Clay's ICP verdict into Close's status field.
Duplicates split the history
03Re-pushed records create new leads instead of updating existing ones, splitting call logs and email history across copies.
What the sprint leaves behind
How GTMLane fixes this handoff
This is one seam of the route we inspect in a workflow audit. When the sprint cleans the Clay → Close handoff, your team keeps:
- A Clay-to-Close field map with required fields for every lead that enters a smart view
- Status rules that translate ICP fit and enrichment confidence into Close lead statuses
- Match-and-update logic so re-syncs enrich the existing lead instead of cloning it
Not sure this is the handoff that’s costing you?
A 15-minute fit check confirms whether the problem is this seam, another one, or not a handoff problem at all. The $500 audit maps the whole route — and is credited toward the sprint.