Contact Changed Jobs? What to Do Before You Hit Send

When a contact changes jobs, the record in your list stops describing a person and starts describing a vacancy. Send to it and one of three things happens: the email bounces and dents your sender reputation, it lands in an inbox someone else now owns or it reaches a person who no longer holds the role you wrote the message for. Checking first costs less than any of those. The better habit is to treat a changed job as four different situations and answer each one differently. Follow the contact if the new company fits. Find the replacement if the account still matters. Drop the record if neither applies. Hold the send when you can't tell. This post lays out that triage and the numbers on how often you'll need it. It also covers how to run the check before a campaign goes out instead of after the bounces arrive.

Key takeaways

• A changed job is a decision, not just a data error. The right move depends on where the person went and whether that company, or the one they left, still fits.
• You'll hit this more often than you think. In January 2026, 20.6% of US wage and salary workers had been with their employer a year or less.
• The worst case doesn't bounce. A departed employee's address can keep accepting mail, so a basic email check passes a record that points at nobody.
• Moved champions are worth chasing. One vendor study of more than 5,000 opportunities found deals involving a previous champion more than doubled win rates, and most of those champions never came back unprompted.
• AvairAI checks at the moment you run it. Enrich Contacts returns the current employer and a Moved badge showing where someone went, and the same check runs at campaign launch.

How often a contact has already moved

The Bureau of Labor Statistics measures this every two years. In its January 2026 release, median tenure with a current employer was 4.1 years, up from 3.9 in January 2024. For workers ages 25 to 34 it was 3.0 years. And 20.6% of wage and salary workers had been with their current employer for a year or less, a group the BLS says includes new hires, job losers who found new work and people who changed employers voluntarily (BLS).

Treat that as a ballpark for your list. It covers every US wage and salary worker, not just B2B buyers. It also includes people entering the workforce, so your own contacts could run higher or lower. Still, the arithmetic is sobering. If roughly one worker in five started somewhere new within the last year, then on a list of 1,000 contacts built a year ago, you'd expect on the order of 200 to be in a different seat today.

Vendors who sell this data say the same thing from the inside. ZoomInfo's own writing puts annual decay for job titles at 25% to 35% and notes that a CRM will keep showing a contact who left 18 months ago as an active record, with a title and phone number that are both wrong (ZoomInfo). Nothing in the record tells you.

The failure that doesn't bounce

A bounce is the polite version of this problem. It tells you something is wrong. The more expensive version is the email that delivers.

Companies handle departed employees' mailboxes in different ways. Some shut them off. Others keep them alive for weeks, forward them to a manager or accept all mail on the domain. A basic validator checks whether an address can receive mail, finds that it can and passes the record. Your message then goes to a stranger, or to a successor reading a pitch addressed to someone else, and nothing in your reporting flags it. This is the gap behind why B2B teams need both email and employment verification: deliverability tells you the mailbox exists, and employment tells you whether the person is still behind it.

Four outcomes, four moves

Once you know a contact moved, the next question is what to do about it. Most teams stop at "remove the record," which throws away the best cases. Sort every moved contact into one of four buckets.

1. They moved to a company that fits

This is the one worth acting on fast. A person who knows your product and lands at a new company walks in with trust you didn't have to earn. UserGems analyzed more than 5,000 sales opportunities and found that previous champions "more than double your win rates," with deals that were 54% larger and sales cycles 12% shorter (UserGems). Read that with care. UserGems sells job-change tracking, and its definition of a champion includes people who evaluated a product, not only buyers. The direction is credible; the exact lift is theirs.

The same team looked at SaaS category leaders with strong NPS scores and found that 91% of their past champions had not come back on their own, even after 90 days in the new job (UserGems). If you wait for them to call, most won't.

Write to the new role, not the old one. A prospect who never replied is a weaker case than a past champion, so don't pretend to a relationship you never had. The move is still a fair reason for a fresh first message, aimed at what their new company is dealing with.

2. They left an account you still want

The company didn't stop mattering because one person left. The seat turned over, and someone now holds the title you were targeting. Find that person by title at that company. A new leader in a senior seat is a leadership change, one of the public events Pain-Signal Targeting reads as evidence a company may be reconsidering how it works, which makes the replacement a sharper target than the person you lost.

3. They moved somewhere that isn't a fit

Take them out of the active campaign. Keep the record if you like, parked and flagged, because people move again. One rule applies regardless: if the contact ever opted out, that suppression follows them. A person who unsubscribed at the old company stays unsubscribed at the new one.

4. You can't tell

Hold the send. "Could not determine" is a real answer, and it beats a guess. Mailing a record you can't confirm trades a small saving in credits or time for risk to the domain every later campaign depends on.

Running the check before you send

AvairAI's Enrich Contacts tool is built for this step. Give it a name and a company and it returns the current employer, title, email, LinkedIn profile and phone, with a grade for every row and the reason behind it: verified, review recommended, confirmed wrong or could not determine. When someone has changed jobs, the row carries a Moved badge and where they went. That maps straight onto the four buckets: a Moved badge with a good new employer is bucket one and a badge on a target account is bucket two. "Could not determine" is bucket four.

It costs 1 credit per contact submitted, drawn from the Tools credits included with your plan, and paid plans can batch up to 200 contacts by CSV. Inside a campaign, the same email and employment check runs at launch as Contact Verification, so a moved contact gets flagged before you spend a touch on them. The tool is part of AvairAI's Tools, and you can run it without creating a campaign.

One honest limit. AvairAI doesn't sit watching your list in the background. It checks when you run it. That's why timing matters: run the check right before you send, not on the day the list was built. The difference between a snapshot and a live check is covered in Static Databases vs Live Search, and the broader case for refreshing records lives in the contact data quality guide.

Frequently asked questions

How do I find out if a contact has changed jobs?

For one or two people, open their LinkedIn profile and check the current employer. For a list, run it through a tool that checks employment, such as Enrich Contacts, so every row gets a current employer and a grade instead of a guess. A bounce is a poor detector, since many people who moved never bounce.

Should I email someone at their new company?

Yes, if the new company fits and you have a real reason to write. Use a verified business address, write to the new role and include a clear way to opt out, the same as any first email. If they opted out before, honor it.

If the old email still delivers, is the contact still there?

Not necessarily. A delivered email only proves the mailbox exists. Some companies keep a departed employee's address active or forward it, so the message can reach someone else entirely.

How often should I recheck a list?

Right before each send. Records change on the person's schedule, not yours, so a check run months earlier can already be out of date. Checking at the moment of use is the only version that matches the data to the send.

Check the person before you write the message

A moved contact is rarely a dead end. Sorted properly, some become your warmest opening, some point you to a better target and some stay out of the way. All of that depends on knowing the person moved before the email goes out. Run the check first, then decide what to write.