fix(enrichment): drop Dropcontact from the phone-number cascade

Dropcontact is an email/company-data enrichment service, not a phone-discovery
provider — its phone/mobile_phone fields are unreliable and were surfacing
firmographic data (an employee-count range like "5000-20077") as the phone.
Keep the two purpose-built phone finders (LeadMagic find_mobile, Datagma
find_phone); Dropcontact stays in the work-email and company cascades where
its data is reliable.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: TheodoreSpeaks

apps/sim/enrichments/phone-number/phone-number.test.ts

@@ -23,7 +23,6 @@ describe('phone-number enrichment cascade', () => {
       'prospeo',
       'leadmagic',
       'datagma',
-      'dropcontact',
     ])
   })
 
@@ -102,20 +101,4 @@ describe('phone-number enrichment cascade', () => {
       expect(p.mapOutput({ phone: null })).toBeNull()
     })
   })
-
-  describe('dropcontact', () => {
-    const p = provider('dropcontact')
-    it('enriches via name+company and prefers mobile_phone', () => {
-      expect(p.toolId).toBe('dropcontact_enrich_contact')
-      expect(p.buildParams(nameDomain)).toEqual({ full_name: 'John Doe', website: 'acme.com' })
-      expect(p.buildParams(linkedinOnly)).toEqual({
-        full_name: 'John Doe',
-        linkedin: 'https://linkedin.com/in/johndoe',
-      })
-      expect(p.buildParams({ companyDomain: 'acme.com' })).toBeNull()
-      expect(p.mapOutput({ mobile_phone: '+1555', phone: '+1999' })).toEqual({ phone: '+1555' })
-      expect(p.mapOutput({ phone: '+1999' })).toEqual({ phone: '+1999' })
-      expect(p.mapOutput({})).toBeNull()
-    })
-  })
 })

apps/sim/enrichments/phone-number/phone-number.ts

@@ -7,10 +7,10 @@ import type { EnrichmentConfig } from '@/enrichments/types'
  * Phone Number enrichment. Finds a contact's phone number from a full name plus
  * any available identifiers (company domain, LinkedIn URL) via a waterfall:
  * People Data Labs (name match) → Wiza reveal → Findymail (LinkedIn) → Prospeo
- * mobile → LeadMagic (LinkedIn) → Datagma (LinkedIn) → Dropcontact (name+company).
- * Each provider opportunistically uses whatever identifiers the row provides and
- * self-skips when it has none usable, so adding more inputs widens coverage
- * without reordering. First phone wins; all providers support hosted keys.
+ * mobile → LeadMagic (LinkedIn) → Datagma (LinkedIn). Each provider
+ * opportunistically uses whatever identifiers the row provides and self-skips
+ * when it has none usable, so adding more inputs widens coverage without
+ * reordering. First phone wins; all providers support hosted keys.
  */
 export const phoneNumberEnrichment: EnrichmentConfig = {
   id: 'phone-number',
@@ -137,25 +137,5 @@ export const phoneNumberEnrichment: EnrichmentConfig = {
         return phone ? { phone } : null
       },
     }),
-    toolProvider({
-      id: 'dropcontact',
-      label: 'Dropcontact',
-      toolId: 'dropcontact_enrich_contact',
-      buildParams: (inputs) => {
-        const fullName = str(inputs.fullName)
-        const website = normalizeDomain(inputs.companyDomain)
-        const linkedin = str(inputs.linkedinUrl)
-        if (!fullName || (!website && !linkedin)) return null
-        return filterUndefined({
-          full_name: fullName,
-          website: website || undefined,
-          linkedin: linkedin || undefined,
-        })
-      },
-      mapOutput: (output) => {
-        const phone = str(output.mobile_phone) || str(output.phone)
-        return phone ? { phone } : null
-      },
-    }),
   ],
 }