\n| High bounce rate after enrichment<\/td>\n | Appending unverified emails; stale domains; suppression not applied<\/td>\n | Deliverability Rate and Bounce Rate by source list and by date enriched<\/td>\n | Add verification + suppression before send; write back only verified emails; refresh older segments first<\/td>\n<\/tr>\n |
\n| Recruiters complain numbers do not work<\/td>\n | Office\/switchboard numbers treated as mobile; low-confidence matches written back<\/td>\n | Connect Rate by channel type; wrong-party notes; gatekeeper frequency<\/td>\n | Separate mobile vs office fields; route low-confidence to review; suppress switchboards for direct-to-provider sequences<\/td>\n<\/tr>\n |
\n| Duplicate providers multiply in ATS<\/td>\n | No pre-enrichment dedupe; no writeback key; multiple imports<\/td>\n | Duplicate rate by NPI; conflicting contact values across records<\/td>\n | Gate enrichment behind NPI dedupe; enforce a single external ID; merge rules before writeback<\/td>\n<\/tr>\n |
\n| Good enrichment results, but campaign performance still weak<\/td>\n | Message-market mismatch; wrong channel timing; poor segmentation<\/td>\n | Reply Rate by specialty\/location; Answer Rate by time-of-day<\/td>\n | Segment by specialty and setting; adjust call windows; tighten outreach templates to the job constraints<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Metric definitions (use these consistently):<\/strong><\/p>\n\n- Connect Rate<\/strong> = connected calls \/ total dials (per 100 dials).<\/li>\n
- Answer Rate<\/strong> = human answers \/ connected calls (per 100 connected calls).<\/li>\n
- Deliverability Rate<\/strong> = delivered emails \/ sent emails (per 100 sent emails).<\/li>\n
- Bounce Rate<\/strong> = bounced emails \/ sent emails (per 100 sent emails).<\/li>\n
- Reply Rate<\/strong> = replies \/ delivered emails (per 100 delivered emails).<\/li>\n<\/ul>\n
<\/span>Weighted Checklist:<\/span><\/h2>\nUse this as your enrichment readiness checklist and your low-confidence routing policy. Score each line 0\/1 and multiply by weight. If you score below your internal go\/no-go threshold, fix inputs before you run a batch.<\/p>\n |
![\"54310\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/batch-contact-enrichment-5cc8d630.png.webp\")
<\/p>\n