Deciding whether a plus-addressed webinar signup is the Jonas already sitting in your CRM is not a formatting rule, it is a judgement against your dedupe policy. Claude Code searches on the email, the person's name and the company domain before it changes anything, which is exactly the order the instructions demand. It then fixes what your standards cover, notes the duplicate, and leaves the merge to a human.
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Pricing page form
elena vargas-morales
EmailELENA.VARGAS@grupo-nortech.com.mx
Notefirstname: elena | lastname: VARGAS-morales | email: ELENA.VARGAS@grupo-nortech.com.mx | company: grupo nortech s.a. de c.v. | phone: 5215512349876 | jobtitle: Sr. Procurement Mgr. | country: mexico | lifecyclestage: (empty) | hs_analytics_source: Pricing page form | notes: (empty)
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect HubSpot
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Data standards
Your rules for a contact record in your own words: which fields are required, how names, phone numbers, countries, and company names should be formatted, and how lifecycle stages are set. The agent fixes only what you describe here and touches nothing else.
Dedupe policy
What makes two records the same person for you, for example same email domain plus same full name, or a plus-address of an existing email, and which record wins when they clash, the older one or the one with the deal.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Three searches happen before a single field is written, so a duplicate surfaces while it is still a note rather than after two reps have worked the same account.
Spam entries, plus-addressed emails and near-matching company names are where a hasty agent does damage. Reading the whole record before acting keeps it to a note and a Slack line.
Each run is still short, and the reads are the point, because the searches are what turn a blind formatter into something that catches the duplicate. Cost is per contact, so the case to plan for is a bulk import: a few thousand records means a few thousand runs, and you are better off pausing the agent for the load.
Free to start. Guided setup, a test run against staged conversations, and it's live.