"Left the company" has many writers and many meanings
Departure sits in status picklists and checkboxes that other processes fill.
SymptomPeople marked as departed are still at their company, or people who left still show as current, depending on which field the sync reads.
The standard move is to read one "departed" field and drop the person from the account. In real CRMs, departure has no single home.
Departure often sits in one value of a status picklist that mostly holds qualification buckets. Such picklists often mix departure with qualification values.
Or it sits in a checkbox that more than one process can tick. An enrichment write-back can tick it from a single email-validator result, which is about an address rather than a person.
So read departure through curated rules that map the field and value pairs for each CRM. Give the employment edge an end date and a reason, and reopen it when the signal behind it is withdrawn.
List every contact field that can mark a person as departed, from the CRM's field metadata. Count the values in each picklist that describe departure and the values that describe qualification. List the automations and integrations that fill each checkbox. A departure that rests on 1 enrichment or email-validation result alone is a gap.
Passes ifEvery process that fills a field marking a contact departed needs more than 1 enrichment or email-validation result.
Access needed:crm-readlocal-config
- 01Map the exact field and value pairs that mean departure in each CRM. Ignore the rest of the picklist.
- 02Record an end date and a reason on the employment link instead of dropping the person.
- 03Keep the field and value that ended the link with the reason. A reader can then see what said the person left.
- 04Reopen the link when the field or value that ended it is withdrawn.