PROFESSIONAL WORK · Recruiting data & AI
Provider contact verification
Finds provider contact details, verifies them by phone within calling windows and spend caps, and hands confirmed records to the CRM.
BuiltProductionDocumented October 15, 2026
My contribution
Built and hardened sourcing, verification, worker controls, and staged CRM writeback.
Tools
Python · PostgreSQL · Parquet · FastAPI · Voice APIs · Bullhorn
How it works
- InputProvider researchIdentities and candidate phone numbers
- CheckEligibility & suppressionOpt-outs, ownership, specialty, mobile eligibility
Human-verified data overrides research signals
- CheckArmed workerStarts disarmed; local calling windows, retry limits, spend and call caps
- StepVerification callVoice APIs
- StepClassify the outcomeAnswered, voicemail, wrong number, or disconnected
- OutputCRM handoffMatch an existing record or stage a new one
Timed-out write → check the CRM before retrying
Decisions that mattered
Workers start disarmed
An explicit arm action, local-time calling windows, retry limits, and spend/call caps bound execution.
Verification is a specific claim
Answered verification, voicemail confirmation, wrong numbers, and disconnected numbers remain different outcomes. A confirmed number is not a qualified candidate.
Human evidence wins
Research signals do not override a human-verified identity or suppression. Specialty mapping and mobile eligibility are checked before downstream use.
Resolve uncertain writes before retrying
A timed-out CRM request may already have committed. Reconciliation checks the destination before another create is attempted.
Results
From September 11 to October 6, 2026, the system made 21,641 call attempts and confirmed 1,173 numbers (784 answered verifications and 389 voicemail confirmations). It also identified 530 bad numbers. At the same checkpoint, CRM handoff had created 990 new records since September 17.
Scope & limits
These figures measure verification and CRM handoff. Submissions and placements weren’t tracked in this checkpoint.