A bounce is a forwarding notice nobody read
A sequencer treats a bounce as the end of a lead. It stops sending and moves on. For a recruiter it is news. Work mailboxes are closed when people leave, so a hard bounce on a hiring manager usually means a change of employer. That is two facts at once: someone who knows you is sitting inside a company you may not work with yet, and the account they left has lost your contact.
So each bounce is two jobs, in this order. Find where the person is today, then find the address that works there. Doing only the second is how a record ends up with a fresh address at the wrong company.
This play starts where checking a list before you send stops. That one gives verdicts and finds nothing. This one takes the addresses that failed in a live campaign and repairs the people behind them.
What you get back
Your bounce list, one row per person: the result of the second check on the old address, still at the employer or moved, the company and title for the movers, the replacement address with the provider it came from and its verdict, and what the row cost. Rows that could not be fixed say why: no LinkedIn URL, no profile found, no address found, or found and undeliverable.
Beside it sits a review list of proposed CRM changes. Nothing is written until you approve rows, and nobody is enrolled in a campaign again.
Variations worth knowing
Client contacts who moved. A mover is a lead at the company they joined and a gap at the account they left. Follow your client contacts when they move company qualifies that company and drafts both messages.
Candidates with a work address on file. Old databases often hold a candidate's work email. When it bounces, the fix is a personal email, not the address at their next employer.
No LinkedIn URL on the row. The job-change check needs one. A name and an employer can often be resolved to a profile first, as its own approved step. Those matches are weaker and each is marked.
Where this goes wrong
Soft bounces treated as moves. A full mailbox or a server outage bounces too. That is why the old address gets one more check before anything dearer runs.
The dead address comes back. A provider can hand back the very address that bounced. It is compared with your bounce list and counted as a miss.
A profile nobody updated. The check reads a public profile. Someone who left last month and has not edited theirs shows as still there. Those rows are worth a phone call to the switchboard.
Sending to the fix straight away. A replacement address has never heard from you. Start it at the top of your normal sequence, not at the step where the old one died.
