Keep Contact Data Fresh When Buyers Change Jobs
Keep contact data fresh by detecting possible changes, verifying the person’s current role, updating the correct records, and controlling which address can still enter outreach. Champion tracking adds relationship context: it follows people who already know your product when they move to another company. A detected move is a reason to investigate and possibly reconnect, not automatic proof of buying intent.
Treat job-change detection, contact enrichment, CRM synchronization, and outreach as separate steps with separate failure modes. A tracker can detect a new employer before a usable work email is available. A fresh email can be attached to the wrong company. A correct CRM update can still leave an old address active in a sequence.
What actually changes when a buyer moves?
A person, a job, and a CRM contact record are related but not interchangeable. One person can hold several concurrent roles; a promotion may not change the employer; a company rename may not be a job change. Preserve the evidence and history needed to distinguish these cases.
| Observation | What to verify | Operational consequence |
|---|---|---|
| New employer reported | Same person, actual employer, effective or observed date, current role | Review the new account and contact path; preserve the old relationship history. |
| New title at the same employer | Promotion, temporary assignment, or inaccurate enrichment | Update supported fields without assuming a new buying project. |
| New email found | Address belongs to the intended person and current employer | Review verification and eligibility before using it. |
| Old email bounces | Bounce reason and whether the person actually moved | Pause the address; do not infer a new employer from the bounce alone. |
| Company rename or acquisition | Domain, legal or operating entity, account relationships | Resolve account mapping before creating duplicates. |
| Conflicting sources | Source timing, identity match, and unresolved facts | Keep the record under review rather than overwriting with confidence. |
Distinguish created, updated, and verified timestamps. The date you imported a record is not the date someone confirmed employment. Keep a source URL or provider reference, observation time, and review status for material changes. When the actual move date is unknown, say so instead of substituting the detection date.
Define the people worth monitoring
Start with people whose relationship to your product is documented: former buyers, customer stakeholders, active advocates, or relevant users. Decide what “champion” means for your team. A contact who merely appeared in an old account export should not automatically be described as a supporter.
Use CRM attributes to define the initial population and review the selected people. Include the relationship owner, old company, known role, and the reason the person belongs in the monitored group. The buying-committee workflow helps distinguish a commercial sponsor from an evaluator or end user.
Keep the scope intentional. Monitoring every contact can increase recurring costs and create more low-confidence changes than your team can review. Prioritize relationships and markets relevant to your current ICP and signal criteria. Revisit membership when customers churn, roles change, or the definition of an advocate changes.
How Unify champion tracking works
The current Champions documentation says Unify checks selected people every 30 days and finds updated contact information when it detects a new job. Each tracked champion consumes credits per tracking cycle whether or not a move is found. Review the rate shown in your workspace before enabling the recurring tracking.
In Settings → Champions, choose company conditions, optionally narrow person conditions, inspect the preview, and enable tracking after reviewing usage. The Tracking tab shows monitored people; Job changes shows detected moves and the new company and role. A recent move may appear only in a later cycle as source information becomes available. This is not an instant-notification guarantee.
The documentation also says Unify creates an exclusion for old job records of champions who moved. Review the actual workflow’s exclusion settings before relying on that protection. Detection and creation of an exclusion do not establish that every existing sequence, integration, or external sender has applied it.
Use the Job change signal in person filters to define a relevant lookback period. A saved audience can change as new moves are detected, and a champions trigger can route people through a play for qualification, outreach, or a Slack alert. Review rerun settings so repeated observations do not produce repeated outreach to the same person.
Separate champion checks from general data refresh
The documented 30-day champion check should not be generalized into a promise that every field in every contact record is reverified every 30 days. Different sources, fields, and workflows can have different update behavior. Ask what is checked, what counts as a successful result, and what happens when sources disagree.
Unify’s company and contact data product provides access to multiple data sources. Multiple sources can expand retrieval options, but they do not establish a universal match rate for your population or guarantee current employment. Test your priority segments and retain unresolved cases.
Use the contact enrichment workflow after identifying the new company and appropriate role. Verify that returned details belong to that person’s current job. An email verification result alone does not establish the employer relationship, consent to outreach, or inbox placement.
Update CRM records without erasing relationship history
Decide how your CRM represents employment history before allowing automatic changes. Preserve the old account’s opportunities, activities, and ownership context. Do not move all historical revenue or conversations to the new company just because a person’s current employer changed.
Review Salesforce field mappings or HubSpot property mappings for source ownership and write behavior. Reading a new value, filling an empty field, and overwriting an existing field are different operations. Identity and relationship changes deserve explicit review when a wrong match could alter customer history.
If you import reviewed updates, the import workflow explains domain-based company matching and email-based person matching. A changed email may therefore require careful identity reconciliation; do not assume it will automatically merge with the person’s old record. Use the CRM implementation guide to test associations, creation rules, and protected fields.
Qualify the new account before reconnecting
A familiar buyer can move to a company that does not fit your product, already uses it, belongs to another rep, or is subject to an exclusion. Recheck the destination company instead of carrying the old account’s eligibility forward.
Use research agents for bounded qualification questions about the new company. Test expected matches and non-matches, inspect supporting research, and route ambiguous cases for review. The account-data maintenance workflow helps keep those decisions connected to the CRM.
Apply the customer and competitor exclusions at the new account. For users assigned to an engagement policy, its exclusions replace sequence ruleset exclusions. Check ownership, user assignment, and actual block behavior; an exclusion existing somewhere in the workspace is not enough.
Reconnect in a way that reflects the real relationship
The following is an illustrative message template: “I saw your move to [verified company]—congratulations. We worked together on [accurate, appropriate description of the prior relationship]. If [relevant problem] falls within your new role, happy to reconnect when useful.” Omit the relationship sentence if you cannot support it, and avoid disclosing private usage or commercial details from the prior employer.
Do not write as though the person is already evaluating your product at the new company. Use the research-to-outreach motion to turn the verified context into an appropriate question. If you require draft approval, the chat or list agentic-sequence route supports that review; enrollment from a person’s record can begin without separate draft approval.
Monitor freshness as an operational queue
Create review states such as detected, identity confirmed, contact details unresolved, CRM updated, eligible for outreach, and closed without action. Assign an owner to exceptions. Decide which steps can run automatically and which require review, rather than treating every detected move as a successful activation.
For a reporting cycle, freeze the monitored population and take a documented cutoff snapshot. Detection review completion is the number of detected changes with a completed review divided by all detected changes in that cycle. Pending and unresolved reviews stay in the denominator and are listed separately. If no changes were detected, report N/A with the count of people monitored.
To measure confirmed fresh contact coverage, divide monitored people with current employer, role, and an accepted contact path verified under your stated criteria by all people in the frozen monitored population. Report missing and conflicting records separately and retain them in the denominator. If the population is empty, report N/A. This measure does not estimate every job change the tracker may have missed.
Choose review cadence from relationship value, source availability, and the consequences of stale information. Track recurring credits and human review effort using current pricing and usage terms. The goal is a reliable path from changed evidence to the right next action, while preserving history and respecting the buyer’s current situation.
Frequently asked questions
How often does Unify check tracked champions?
The current Champions documentation specifies checks every 30 days. A recent move may become visible in a later cycle as new information becomes available.
Are champion credits used only when a move is found?
No. Each tracked champion consumes credits per tracking cycle whether or not a job change is found. Review the rate in your workspace before enabling tracking.
Does a detected job change prove buying intent?
No. Verify the current role, qualify the new company, check exclusions and ownership, and decide whether reconnecting is appropriate.
Should I overwrite the old CRM contact when a person moves?
Follow your CRM identity and employment-history policy. Preserve old account activities and opportunity history, and review matching and associations before changing records.
Does monthly champion tracking mean all contact data is verified monthly?
No. The documented champion-check cadence should not be generalized to every field or record. Verify the behavior of the specific source and workflow.
About the author: Austin Hughes is Co-Founder and CEO of Unify, outbound AI for sellers where AI agents and reps work side by side, from finding the buyers already in market to reaching them with the right message. Before founding Unify, Austin led the growth team at Ramp, scaling it from 1 to 25+ people and building a product-led, experiment-driven GTM motion. Prior to Ramp, he worked at SoftBank Investment Advisers and Centerview Partners.
