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

# Track champions when they change jobs

> Check whether a contact has left or moved from their previous employer with Waterfall Job Change, then use the result in your CRM workflow.

Check whether a customer champion has changed employers with Waterfall Job Change. Start with a professional email, or the previous company plus a supported contact identifier, and get an employment outcome with a profile when available.

Use it to check customer contacts, former buyers, and important CRM records. Your workflow decides when to check again and how to follow up on a change.

## Check a known contact

LinkedIn is not required. Use a `professional_email` on its own, or pair `contact_full_name` with the previous `company_domain`. You can also include `contact_full_name` with a professional email.

A `contact_linkedin` or `personal_email` needs either `company_domain` or `company_linkedin`. A name with only `company_linkedin` is not a supported combination. See the [supported inputs](https://docs.waterfall.io/v1/job-change-launcher.md) for all options.

This request uses illustrative identifiers:

```bash theme={null}
curl --request POST 'https://api.waterfall.io/v1/job/change' \
  --header "x-api-key: $WATERFALL_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "company_domain": "example.com",
    "contact_full_name": "Jordan Lee",
    "custom_fields": {
      "crm_contact_id": "contact_582"
    }
  }'
```

The result is returned in the same response. Read `output.job_change_status` for the employment outcome; the top-level `status` describes the API job.

## Use the outcome in your workflow

| Outcome | Meaning | A possible next step |
| - | - | - |
| `moved` | A move to a different company was identified. | Review the returned profile and check whether the new account fits your target market. |
| `left` | The person was found to have left the previous company. | Flag the old employer association for review. |
| `no_change` | No change from the supplied company was identified. | Keep the record and check again on your schedule. |
| `unknown` | The check could not establish a reliable outcome. | Keep the employment status unresolved. |

Inspect `output.person` when a profile is returned. It can be empty when no matching profile is found. Email and phone channels are redacted from Job Change results; use [Contact Enrichment](https://docs.waterfall.io/v1/contact-enrichment-launcher.md) if you need contact details for a resolved profile.

## Does this create an ongoing watch?

Each request performs a check. To track a list over time, schedule checks in your application or automation platform, compare results with your saved records, and route meaningful changes to the right owner. Retrieving a saved job through [Job Change Finder](https://docs.waterfall.io/v1/job-change-finder.md) returns that job's result rather than running a new employment check.

## Does the response tell me when the move happened?

The job's `start_date` and `stop_date` describe processing time. Available employment history may contain role dates, but the time you discover a change is not necessarily the time the person changed jobs.

[Open the Job Change reference](https://docs.waterfall.io/v1/job-change-launcher.md), [review usage costs](https://docs.waterfall.io/v1/inline-usage.md), or [evaluate results on known contacts](https://docs.waterfall.io/v1/evaluate-waterfall.md).


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