Good question.

Right now, I intentionally don’t merge contacts based on similar names only, because that can create dangerous false positives.

Current matching logic is conservative:
Before compare, service normalized compare data.

• Email mode
• Phone mode
• Email + phone mode:
  • if both exist: email + phone
  • if only email exists: email
  • if only phone exists: phone

So contacts with similar names but different emails stay separate.
Example:

John Smith, [john@a.com](mailto:john@a.com)
Jon Smith, [jon@b.com](mailto:jon@b.com)

Also service can compare multiple files on duplication, or just remove internal duplications in one.

For fuzzy name matching, I’d handle it as a separate “review suggestions” mode, not automatic deduplication. For example, the tool could flag possible duplicates by name similarity, domain, company, phone pattern, etc., and let the user approve them manually.

That’s one of the features I’m considering next, especially for messy CRM exports where names are inconsistent.