Who can enrich companies from the registry?

Any member with Companies update access once an admin enables French registry in Setup → Integrations. If disabled, Pilot explains that an admin must enable the integration first.

Will enrichment overwrite fields I edited manually?

In Operations, manually edited fields stay as pending diffs until you approve or dismiss. In Standard views, Enrich shows a confirmation, then overwrites mapped registry fields on the company.

What is BODACC data used for?

Legal announcements from BODACC are stored as pending events until approved. They help teams spot changes like address updates or officer movements without manual monitoring.

Can I enrich from Telegram?

Yes. In direct chat, use inline buttons or reply with the option number or SIREN when Pilot presents registry matches.

Enrich Companies from SIREN and official sources

Enable on-demand enrichment from INSEE, BODACC, and VIES. Members enrich from Operations chat or the Enrich button on Companies in Standard views; admins enable the integration and review pending diffs where Operations protects manual edits.

INSEE

Core fields

Address, legal form, NAF

BODACC

Announcements

Pending until approved

diff

Conflict-safe

Manual edits never silent overwrite

Official French company data

SIREN lookup in Operations with approval gates.

French company records need accurate SIREN, legal form, and address data — not copy-paste from societe.com. Registry enrichment pulls official fields into your Companies object.

Creating a company in Operations or Standard views can use standard creation or registry-enriched context. BODACC announcements surface as pending events until approved; dirigeants can import as Contacts linked to the company.

SIREN / SIRET lookup
Search recherche-entreprises by name or SIREN. Apply address, legal form, NAF, and officer data to company records.
Enrich where you work
Operations chat uses pending diffs for manual conflicts. Standard views Enrich confirms, then overwrites mapped registry fields.
Dirigeants as Contacts
List officers from the registry and import selected dirigeants as Contacts with registry_role metadata.

Enable

Enable once, enrich from Operations or Standard views

Admins turn on French registry in Setup → Integrations. Members with Companies access enrich from plain chat or the company record sidebar in Standard views.

Disabled by default — no automatic enrichment without choosing the path
English or French requests in Operations and Telegram
Standard views: Enrich → pick match → confirm overwrite of registry fields
Admin page supports enrichment outside chat when needed

Sources

Official data sources

INSEE company data, BODACC legal announcements, and VIES VAT validation when applicable.

recherche-entreprises — SIREN, address, legal form, NAF, dirigeants
BODACC stored as pending events until approved
DILA / Etalab attribution on BODACC display

Approval

Two enrichment paths

Operations keeps conflict-safe pending diffs. Standard views asks for explicit confirmation, then overwrites mapped registry fields.

Operations: fields you edited stay pending until you approve or dismiss
Standard views: confirm dialog, then force-apply registry-mapped fields
AI fields on the company recalculate after a successful enrich save

Dirigeants

Dirigeants import workflow

Officers from the registry can become Contacts linked to the company record.

Natural persons map to first and last name
Legal entities use full legal name
Registry contacts never include email or phone

Fields

Registry fields in your schema

SIREN, SIRET, legal_form, bodacc_alert, and contact_source=registry align CRM data with official identifiers.

legal_form is distinct from CRM type/stage picklists
registry_role marks dirigeants imported from the registry
bodacc_alert flags announcements needing review

Questions

Short answers before you request access.

Who can enrich companies from the registry?: Any member with Companies update access once an admin enables French registry in Setup → Integrations. If disabled, Pilot explains that an admin must enable the integration first.
Will enrichment overwrite fields I edited manually?: In Operations, manually edited fields stay as pending diffs until you approve or dismiss. In Standard views, Enrich shows a confirmation, then overwrites mapped registry fields on the company.
What is BODACC data used for?: Legal announcements from BODACC are stored as pending events until approved. They help teams spot changes like address updates or officer movements without manual monitoring.
Can I enrich from Telegram?: Yes. In direct chat, use inline buttons or reply with the option number or SIREN when Pilot presents registry matches.