Prospect job-change mid-sequence: update, suppress, or restart
The sequence is live. Enrichment flags a job change. The next step still greets them as "VP Ops at Acme."
That is how agencies burn trust and bounce rates in the same week.
You need a decision matrix, not a shrug. Apollo's sequence-update guidance frames it cleanly: react to data changes with Trigger → Validate → Decide → Update → Measure, and gate high-stakes moves behind confidence thresholds.
First: pause the wrong story
When a company change or hard bounce appears mid-sequence, pause email steps on that contact before the next send window. Keep going with the old employer story and you train the prospect that your "personalization" is stale automation.
Unify's job-change freshness notes make the same ops point: connect detection to action, but do not enroll on a half-confirmed move. A profile update without a confirmed employer is a hold, not a restart.
Decision matrix (agency outbound)
| Signal | Default action | Do not |
|---|---|---|
| Title change, same company | Update persona tag; re-personalize next step | Restart the whole sequence from step 1 |
| Company change (new employer) | Pause; validate; suppress old path or open new contact record | Keep emailing the old company address |
| Hard bounce / bad email | Pause email; re-enrich; verify before any restart | Permanent suppress until verification fails twice |
| Opt-out / DNC | Suppress immediately across active sequences | Re-enroll because "they moved companies" |
| Low-confidence enrichment hit | Human review queue | Auto-restart on a guessed new email |
Apollo's table is useful here: job title at the same company is usually a re-personalize; company change is a pause-and-decide; DNC is immediate suppress with a logged timestamp and source.
Update vs suppress vs restart
Update when the person is still the buyer and only the framing changed (title, scope, team). Keep the thread if one exists. Rewrite the next step against the new evidence and the current client voice brief version.
Suppress when the person left the ICP, opted out, or the old address is dead and you have no verified replacement. Suppression should survive purge in your outbound store so a later list import does not revive them.
Restart when you have a verified new email, confirmed employer fit for the client's ICP, and a reason to treat this as a new motion (often a shorter warm reactivation that references the prior relationship, not a clone of the cold sequence). Forma Norden's job-change workflow splits warm reactivation for the known contact from replacement outreach at the old company — different sequences, different tone.
Confidence thresholds beat vibes
Do not let low-confidence enrichment auto-fire restarts.
- High confidence + verified email → allow automated pause + re-personalize or restart enrollment
- Medium confidence → task a human in the shared inbox or CRM
- Conflict between CRM and enrichment → define source priority (direct CRM input usually wins)
Validity's CRM data-quality research (cited in Apollo's piece) still lands the same warning: incomplete and incorrect records are common. Automation without thresholds just scales the error.
What GTM expects you to keep legible
GTM qualifies against client ICP, writes from prospect evidence, stops sequences on reply, and keeps field provenance plus suppression that survives purge. A job-change mid-sequence is a qualify/write problem first: update the evidence, then decide whether send is still allowed.
If you want that motion in isolated client workspaces, join the waitlist.