Skip to content
Astera Technology

Review bilingual company-name variants before merging leads

Use a confirmed organisation relationship rather than treating similar names as automatic aliases.

Record match evidence and contradictory evidence

Synthetic candidates use “North Sample Studio” and “北方示例工作室”. A staff translation note alone does not establish one organisation. The fixture accepts a customer-confirmed relationship to internal organisation ORG-17 as sufficient match evidence. A third record with similar wording belongs to ORG-18 and stays separate. Preserve each submitted display name so staff can recognise the enquiry later.

Filled synthetic operating record
CandidateEvidenceConflictDecision
L-76 / L-77Staff says names translateNo confirmed organisation linkReview; no automatic merge
L-76 / L-77 after confirmationCustomer confirms ORG-17None in supplied fixtureLink to ORG-17; retain aliases
L-78Confirmed ORG-18Similar name; different organisationKeep separate
Download editable CSV ↓

Move from name similarity to a supported relationship

  1. Keep submitted names
  2. Collect relationship evidence
  3. Check contradictory identifiers
  4. Record link and accepted aliases

Conflicting organisation links block consolidation until the responsible data owner resolves them.

Can L-78 join ORG-17 because its English name differs by one word?

Show the worked answer

No. Its confirmed ORG-18 relationship contradicts that merge. Name similarity does not override the evidence.

This example avoids claiming a legal entity-verification method. The evidence threshold is synthetic and must fit the actual CRM entity model.

Related resources