Job changes are one of the highest-value B2B signals. Golden DB detects them automatically (cross-source reconciliation, LinkedIn monitoring, profile changes). Each detected change fires a workflow signal that agents and humans can act on.
How job changes are detected
- LinkedIn monitoring — if a Person record has a LinkedIn URL, periodic checks detect current-position changes.
- Email domain change — if email moves to a different company domain, that's a job-change signal.
- Cross-source reconciliation — if multiple sources start reporting a different employer, that's a confirmed change.
- Manual edit — if a user updates the employer field manually, that's recorded as a job change.
What happens when a change is detected
Three things automatically:
- The Person record's employer is updated; the previous employer moves to history.
- A "job change" signal fires into the signal stream.
- Active sequences targeting the prior employer pause for that Person; sequences can branch on the change.
Why job changes are high-value signals
A new role = a new evaluation window. The person is buying tools at their new employer that they're familiar with; they have political capital from being new and want to make their mark; and they're not loyal to incumbent vendors yet. Reply rates on job-change-triggered outreach are 3–5x cold outbound.
Configuring job-change actions
Signals → Job Change → Configure. Pick which agents react, which sequences run, and how long after the change the agent reaches out (default: 30 days — long enough for the person to be settled, short enough that the buying window is open).
