Official filings and OpenStreetMap-backed places should both deepen employer research. This release enriches officer contacts from public registries with clearer personal context, and lets Platform CRM optionally create company records from unmatched OpenStreetMap places when you want map coverage without a prior register match.
Registry officer detail
People enrichment from public registries now fills nationality, birth year, and fuller address fields on officer contacts — so CRM people rows from filings look more complete when you research who sits on a company.
What you will notice:
- Nationality and birth year on matching registry officer contacts
- Fuller registered addresses when the dump provides them
- Change-history attribution that still names the registry pipeline as the source
Optional companies from unmatched OpenStreetMap places
Not every OpenStreetMap business place finds a register company to attach to. Admins can optionally create CRM company records from unmatched places so store phones, websites, and locations still land in Platform CRM — ready for later register linking or identity peels when a better match appears.
What you will notice:
- Unmatched map places no longer have to stay invisible forever
- Created companies keep OpenStreetMap attribution in change history
- Existing register matches stay preferred — optional create is for leftovers, not forced merges
Admin control over unmatched places
Optional create stays behind admin configuration and limits so a noisy map extract cannot flood Platform CRM with weak company rows.
What you will notice:
- Unmatched places remain staged until you opt into creates
- Created rows stay attributable to OpenStreetMap in change history
- Register matches continue to win when both exist
Built for denser registry and OpenStreetMap-backed CRM
Whether you are reading an officer filing or covering a retail place that never hit a public registry, this release keeps Platform CRM able to absorb the source without inventing a false identity match.