> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Job changes and CRM cleanup

> Ask your agent to review job changes before proposing CRM repairs.

[Agent guide: CLI and SDK instructions →](/docs/plays/play-job-change-alerts)

## 1. Have your context ready

Have known contacts with stable CRM IDs, current stored employer information, and your acceptance policy.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-gtm Review possible job changes with Deepline for these contacts. Establish the same person across records and compare dated employment evidence. Separate a confirmed change from ambiguous identity, stale data, and provider failure. Propose field-level updates and champion-tracking actions with reasons. Pilot a small sample after approval, but do not overwrite the CRM or trigger outreach yet.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

A job-change proposal has person identity and sufficiently current employer evidence. A changed title alone does not establish a new employer.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Check your understanding

Does a company-name mismatch alone prove a person moved employers?

> **Show the answer**
>
> No. Compare company identity, domain, profile, and source evidence. Keep
> unresolved differences distinct from confirmed moves.

## Related guides

* [Champion tracking](/docs/human/plays/signal-champion-tracking)
* [Find LinkedIn Profile](/docs/human/plays/task-find-linkedin-profile)
* [Find Work Email](/docs/human/plays/task-find-work-email)
* [Personalize Outbound with a Deepline Play](/docs/human/plays/play-personalize-outreach)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.