Outcome. Contacts linked to more than one company always have a clear primary company on record, instead of leaving reports and account-based routing to guess which one counts.
flowchart TD
A[Contact has 2+ associated companies] --> B[Custom code: read labeled company associations]
B --> C{Company count}
C -->|1| D[Status: Single company - ok]
C -->|2+, has primary| E[Status: Primary confirmed]
C -->|2+, no primary| F[Status: Needs review]
F --> G[Add to review list + create task]

When to use it, when not to
- UseUse it when reps or integrations sometimes link a contact to a second company (a former employer, a partner organization) without ever confirming which one is primary.
- UseUse it alongside data-quality-006 (auto-association from email domain) and data-quality-007 (missing company flag): this fiche assumes an association already exists and checks which one is marked primary.
- SkipDo not use it on a portal where contacts are only ever linked to a single company. There is nothing to enforce.
- SkipDo not use it expecting the workflow to pick a primary company on your behalf when the answer is not obvious, such as two current employers. That decision goes to a human.
or the data quality pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





