Compliance handling<\/strong>: opt-outs and do-not-call flags are logged and honored.<\/li>\n<\/ul>\nFor Heartbeat.ai specifically, we also evaluate whether we can provide ranked mobile numbers by answer probability<\/strong>. That\u2019s a prioritization signal, not a promise\u2014your cadence and local time windows still matter.<\/p>\n<\/span>Step 5: Email testing\u2014what we test (and what we don\u2019t)<\/span><\/h3>\nEmail outcomes are a system result: your sending domain + your content + your list + recipient filters. In a pilot, we focus on measurable outcomes you can audit:<\/p>\n
\n- Deliverability Rate<\/strong> and Bounce Rate<\/strong> (per 100 sent emails) to quantify acceptance vs rejection.<\/li>\n
- Reply Rate<\/strong> (per 100 delivered emails) to separate list quality from sending volume.<\/li>\n<\/ul>\n
We do not<\/strong> treat \u201cdelivered\u201d as \u201cin inbox.\u201d Delivered means accepted by the receiving system; inbox placement is a separate layer.<\/p>\n<\/span>Step 6: Run a 2-week pilot (controlled execution)<\/span><\/h3>\nHere\u2019s the structure that keeps pilots honest and fast:<\/p>\n
\n- Setup (before Day 1)<\/strong>: finalize definitions, fields, suppression rules, and sampling. Confirm your compliance review path (phone and email).<\/li>\n
- Week 1 (baseline)<\/strong>: run the same outreach play across Vendor A\/B (or A vs current). Keep recruiter behavior consistent.<\/li>\n
- Week 2 (repeat)<\/strong>: repeat the same play to check stability and variability across days and time windows.<\/li>\n<\/ol>\n
Fairness controls (do not skip):<\/strong><\/p>\n\n- Same local-time call blocks and same day-of-week coverage across vendor arms.<\/li>\n
- Same caller ID strategy and same number of attempts per record.<\/li>\n
- Same email copy, same cadence, same sender domain.<\/li>\n
- Same suppression list applied to all arms, with change control if updates are required.<\/li>\n<\/ul>\n
<\/span>Step 7: Analyze results with denominator discipline (and variance checks)<\/span><\/h3>\nReport phone and email separately, and keep denominators fixed:<\/p>\n
\n- Phone<\/strong>: Connect Rate (connected calls \/ total dials, per 100 dials) and Answer Rate (human answers \/ connected calls, per 100 connected calls).<\/li>\n
- Email<\/strong>: Deliverability Rate (delivered \/ sent, per 100 sent), Bounce Rate (bounced \/ sent, per 100 sent), Reply Rate (replies \/ delivered, per 100 delivered).<\/li>\n<\/ul>\n
Measure this by\u2026 exporting a daily attempt log with one row per dial and one row per email send, then computing each metric from those rows (not from a dashboard summary). Keep a change log for any suppression or cadence updates.<\/p>\n
Decision logic (no thresholds):<\/strong><\/p>\n\n- Stability<\/strong>: results should be directionally consistent across both weeks, not a one-day spike.<\/li>\n
- Not recruiter-driven<\/strong>: improvements should hold across recruiters, not just one outlier.<\/li>\n
- Wrong-party reviewed<\/strong>: spot-check \u201cwins\u201d to confirm you reached the intended person.<\/li>\n
- Suppression honored<\/strong>: opt-outs and do-not-contact flags must be enforced across all vendor arms.<\/li>\n<\/ul>\n
![\"54136\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/how-we-test-contact-data-quality-55cb09be.png.webp\")
<\/p>\n