{"id":54135,"date":"2026-02-01T12:21:22","date_gmt":"2026-02-01T18:21:22","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/accuracy-and-metrics-definitions\/"},"modified":"2026-02-27T13:31:07","modified_gmt":"2026-02-27T19:31:07","slug":"accuracy-and-metrics-definitions","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/","title":{"rendered":"Connect rate definition for recruiters (canonical formulas + how to measure)"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png.webp\" alt=\"54134\" \/><\/p>\n<h1>Connect rate definition for recruiters<\/h1>\n<p><strong>By Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 Keep stable; update-controlled; linkable citation target.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_65 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\r\n<div class=\"ez-toc-title-container\">\r\n<p class=\"ez-toc-title\" >What&rsquo;s on this page:<\/p>\r\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\r\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Who_this_is_for\" title=\"Who this is for\">Who this is for<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Quick_Answer\" title=\"Quick Answer\">Quick Answer<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Framework_%E2%80%9CDenominator_discipline%E2%80%9D_pick_a_denominator_and_stick_to_it\" title=\"Framework: \u201cDenominator discipline\u201d: pick a denominator and stick to it\">Framework: \u201cDenominator discipline\u201d: pick a denominator and stick to it<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Step-by-step_method\" title=\"Step-by-step method\">Step-by-step method<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Step_1_Standardize_your_event_vocabulary_before_you_touch_a_dashboard\" title=\"Step 1: Standardize your event vocabulary (before you touch a dashboard)\">Step 1: Standardize your event vocabulary (before you touch a dashboard)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Step_2_Use_canonical_metric_definitions_formulas_denominators\" title=\"Step 2: Use canonical metric definitions (formulas + denominators)\">Step 2: Use canonical metric definitions (formulas + denominators)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Step_3_Map_tool_outcomes_to_the_definitions_so_the_math_is_reproducible\" title=\"Step 3: Map tool outcomes to the definitions (so the math is reproducible)\">Step 3: Map tool outcomes to the definitions (so the math is reproducible)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Step_4_Build_a_weekly_scorecard_that_cant_drift\" title=\"Step 4: Build a weekly scorecard that can\u2019t drift\">Step 4: Build a weekly scorecard that can\u2019t drift<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Diagnostic_Table\" title=\"Diagnostic Table:\">Diagnostic Table:<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Weighted_Checklist\" title=\"Weighted Checklist:\">Weighted Checklist:<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Outreach_Templates\" title=\"Outreach Templates:\">Outreach Templates:<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Phone_opener_30_seconds\" title=\"Phone opener (30 seconds)\">Phone opener (30 seconds)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Email_1_identity-first\" title=\"Email 1 (identity-first)\">Email 1 (identity-first)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Email_2_details_next_step\" title=\"Email 2 (details + next step)\">Email 2 (details + next step)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Common_pitfalls\" title=\"Common pitfalls\">Common pitfalls<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#1_Counting_%E2%80%9Cconnected%E2%80%9D_differently_across_dialers\" title=\"1) Counting \u201cconnected\u201d differently across dialers\">1) Counting \u201cconnected\u201d differently across dialers<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-17\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#2_Measuring_replies_on_sent_instead_of_delivered\" title=\"2) Measuring replies on sent instead of delivered\">2) Measuring replies on sent instead of delivered<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#3_Blending_wrong-person_outcomes_into_%E2%80%9Cnot_interested%E2%80%9D\" title=\"3) Blending wrong-person outcomes into \u201cnot interested\u201d\">3) Blending wrong-person outcomes into \u201cnot interested\u201d<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-19\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#4_Treating_suppression_as_a_manual_side_task\" title=\"4) Treating suppression as a manual side task\">4) Treating suppression as a manual side task<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#5_Uniqueness_hook_Trust_hub_as_product_prevent_definition_drift\" title=\"5) Uniqueness hook: Trust hub as product (prevent definition drift)\">5) Uniqueness hook: Trust hub as product (prevent definition drift)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#How_to_improve_results\" title=\"How to improve results\">How to improve results<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Measurement_instructions_required\" title=\"Measurement instructions (required)\">Measurement instructions (required)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-23\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Operational_levers_that_usually_move_the_numbers\" title=\"Operational levers that usually move the numbers\">Operational levers that usually move the numbers<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#ATSCRM_field_map_compact\" title=\"ATS\/CRM field map (compact)\">ATS\/CRM field map (compact)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Legal_and_ethical_use\" title=\"Legal and ethical use\">Legal and ethical use<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Evidence_and_trust_notes\" title=\"Evidence and trust notes\">Evidence and trust notes<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#FAQs\" title=\"FAQs\">FAQs<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#What_is_the_connect_rate_definition_for_recruiters\" title=\"What is the connect rate definition for recruiters?\">What is the connect rate definition for recruiters?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-29\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Whats_the_difference_between_connect_rate_and_answer_rate\" title=\"What\u2019s the difference between connect rate and answer rate?\">What\u2019s the difference between connect rate and answer rate?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-30\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#How_do_you_define_deliverability_rate_and_bounce_rate_for_recruiting_email\" title=\"How do you define deliverability rate and bounce rate for recruiting email?\">How do you define deliverability rate and bounce rate for recruiting email?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#How_do_you_calculate_reply_rate\" title=\"How do you calculate reply rate?\">How do you calculate reply rate?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-32\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#What_should_we_log_to_make_these_metrics_auditable\" title=\"What should we log to make these metrics auditable?\">What should we log to make these metrics auditable?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-33\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#Next_steps\" title=\"Next steps\">Next steps<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-34\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#About_the_Author\" title=\"About the Author\">About the Author<\/a><\/li><\/ul><\/nav><\/div>\r\n<h2><span class=\"ez-toc-section\" id=\"Who_this_is_for\"><\/span>Who this is for<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This page is for recruiting ops and leaders who need consistent measurement across teams, tools, and time. If you\u2019ve ever had a weekly meeting derailed by \u201cwhat counts as a connect?\u201d or \u201care we measuring replies on sent or delivered?\u201d, this is your standard.<\/p>\n<p>Use it as the canonical link target for dashboards, SOPs, and stakeholder updates.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Quick_Answer\"><\/span>Quick Answer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<dl>\n<dt>Core Answer<\/dt>\n<dd>Connect Rate = connected calls \/ total dials. Report it per 100 dials to separate phone reachability from messaging and keep weekly reporting comparable.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Most reporting drift comes from denominator changes. Lock definitions, log the raw events, and publish per-100 rates with raw counts.<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiting ops + leaders needing consistent measurement.<\/dd>\n<\/dl>\n<blockquote>\n<p><strong>Compliance &amp; Safety<\/strong><\/p>\n<p>This method is for legitimate recruiting outreach only. Always respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.<\/p>\n<\/blockquote>\n<h2><span class=\"ez-toc-section\" id=\"Framework_%E2%80%9CDenominator_discipline%E2%80%9D_pick_a_denominator_and_stick_to_it\"><\/span>Framework: \u201cDenominator discipline\u201d: pick a denominator and stick to it<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Outreach metrics fail when teams mix denominators. One report uses dials, another uses connected calls, and a third uses \u201cattempts\u201d that exclude voicemails. You can\u2019t compare weeks, teams, or vendors if the denominator moves.<\/p>\n<ul>\n<li><strong>Define each metric with a fixed numerator and denominator.<\/strong><\/li>\n<li><strong>Report in a consistent unit<\/strong> (<strong>per 100 attempts<\/strong> within each channel, and do not blend channels: phone per 100 dials; email deliverability\/bounce per 100 sent emails; email reply metrics per 100 delivered emails).<\/li>\n<li><strong>Log the event that creates the numerator<\/strong> so the metric is reproducible.<\/li>\n<li><strong>Separate data quality from execution<\/strong> (reachability vs timing vs targeting vs message-market fit).<\/li>\n<\/ul>\n<p><strong>Worked example (no guessing):<\/strong> If you place <em>D<\/em> dials and get <em>C<\/em> connected calls, Connect Rate = <em>C<\/em>\/<em>D<\/em>. Report as (<em>C<\/em>\/<em>D<\/em>) \u00d7 100 connected calls per 100 dials, alongside the raw counts (<em>C<\/em> and <em>D<\/em>).<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Step-by-step_method\"><\/span>Step-by-step method<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Standardize_your_event_vocabulary_before_you_touch_a_dashboard\"><\/span>Step 1: Standardize your event vocabulary (before you touch a dashboard)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Your dialer, email provider, and ATS\/CRM won\u2019t agree on naming. Start by listing the events you can actually capture, then map them to stable definitions.<\/p>\n<ul>\n<li><strong>Phone events<\/strong>: dial placed, connected call, human answer, voicemail, busy, no answer, failed, wrong person confirmed, do-not-contact\/opt-out.<\/li>\n<li><strong>Email events<\/strong>: sent, delivered, bounced (hard\/soft), replied, unsubscribed\/opt-out, complaint.<\/li>\n<li><strong>Identity events<\/strong>: person match confidence, wrong-person confirmed, duplicate merged, suppressed.<\/li>\n<\/ul>\n<p>Decide what counts as an \u201cattempt\u201d per channel. For phone, an attempt is a dial. For email, an attempt is a sent email. Keep channels separate unless you\u2019re intentionally building a blended model.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Use_canonical_metric_definitions_formulas_denominators\"><\/span>Step 2: Use canonical metric definitions (formulas + denominators)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>These are the canonical definitions for recruiting outreach measurement. They are designed to be implementable in any reporting stack.<\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Metric<\/th>\n<th>Canonical definition<\/th>\n<th>Formula<\/th>\n<th>Report as<\/th>\n<th>Primary diagnostic use<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><strong>Connect Rate<\/strong><\/td>\n<td>Share of dials that result in a connected call (not necessarily a human answer).<\/td>\n<td><strong>connected calls \/ total dials<\/strong><\/td>\n<td>Connected calls per 100 dials<\/td>\n<td>Phone reachability + dialer execution<\/td>\n<\/tr>\n<tr>\n<td><strong>Answer Rate<\/strong><\/td>\n<td>Share of connected calls that are answered by a human.<\/td>\n<td><strong>human answers \/ connected calls<\/strong><\/td>\n<td>Human answers per 100 connected calls<\/td>\n<td>Call timing + caller ID trust + targeting<\/td>\n<\/tr>\n<tr>\n<td><strong>Deliverability Rate<\/strong><\/td>\n<td>Share of sent emails that are delivered (not bounced).<\/td>\n<td><strong>delivered emails \/ sent emails<\/strong><\/td>\n<td>Delivered emails per 100 sent emails<\/td>\n<td>List hygiene + domain reputation<\/td>\n<\/tr>\n<tr>\n<td><strong>Bounce Rate<\/strong><\/td>\n<td>Share of sent emails that bounce (hard + soft).<\/td>\n<td><strong>bounced emails \/ sent emails<\/strong><\/td>\n<td>Bounced emails per 100 sent emails<\/td>\n<td>Bad addresses + sending practices<\/td>\n<\/tr>\n<tr>\n<td><strong>Reply Rate<\/strong><\/td>\n<td>Share of delivered emails that receive a reply.<\/td>\n<td><strong>replies \/ delivered emails<\/strong><\/td>\n<td>Replies per 100 delivered emails<\/td>\n<td>Message-market fit + targeting<\/td>\n<\/tr>\n<tr>\n<td><strong>Positive Reply Rate<\/strong><\/td>\n<td>Share of delivered emails that receive a positive reply (interested, send details, open to talk).<\/td>\n<td><strong>positive replies \/ delivered emails<\/strong><\/td>\n<td>Positive replies per 100 delivered emails<\/td>\n<td>Offer fit + targeting precision<\/td>\n<\/tr>\n<tr>\n<td><strong>Hard Bounce Rate<\/strong><\/td>\n<td>Share of sent emails that permanently fail (invalid address, non-existent domain).<\/td>\n<td><strong>hard bounces \/ sent emails<\/strong><\/td>\n<td>Hard bounces per 100 sent emails<\/td>\n<td>Address validity<\/td>\n<\/tr>\n<tr>\n<td><strong>Soft Bounce Rate<\/strong><\/td>\n<td>Share of sent emails that temporarily fail (mailbox full, transient server issue, rate limiting).<\/td>\n<td><strong>soft bounces \/ sent emails<\/strong><\/td>\n<td>Soft bounces per 100 sent emails<\/td>\n<td>Temporary deliverability issues<\/td>\n<\/tr>\n<tr>\n<td><strong>Recency<\/strong><\/td>\n<td>How recently a contact point (email\/phone) was verified or observed as valid.<\/td>\n<td>Now \u2212 last verified\/observed date<\/td>\n<td>Days since last verification<\/td>\n<td>Decay risk<\/td>\n<\/tr>\n<tr>\n<td><strong>Refresh cadence<\/strong><\/td>\n<td>How often you re-verify and update contact points for your active segments.<\/td>\n<td>Scheduled interval<\/td>\n<td>Days between refresh runs<\/td>\n<td>Freshness operations<\/td>\n<\/tr>\n<tr>\n<td><strong>Wrong-person rate<\/strong><\/td>\n<td>Share of outreach attempts that reach someone other than the intended candidate.<\/td>\n<td>wrong-person confirmations \/ total attempts (phone: dials; email: delivered emails)<\/td>\n<td>Wrong-person outcomes per 100 attempts<\/td>\n<td>Identity resolution quality<\/td>\n<\/tr>\n<tr>\n<td><strong>Suppression<\/strong><\/td>\n<td>Operational rule that prevents outreach due to opt-out, complaint, wrong-person, or risk flags.<\/td>\n<td>suppressed records \/ total records evaluated<\/td>\n<td>Suppressed per 100 evaluated<\/td>\n<td>Compliance + reputation protection<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><strong>Variable-only examples (for clean reporting):<\/strong><\/p>\n<ul>\n<li><strong>Answer Rate<\/strong>: if you have <em>H<\/em> connected calls and <em>A<\/em> human answers, Answer Rate = <em>A<\/em>\/<em>H<\/em> (human answers per 100 connected calls = (<em>A<\/em>\/<em>H<\/em>) \u00d7 100).<\/li>\n<li><strong>Deliverability Rate<\/strong>: if you send <em>S<\/em> emails and <em>L<\/em> are delivered, Deliverability Rate = <em>L<\/em>\/<em>S<\/em> (delivered per 100 sent = (<em>L<\/em>\/<em>S<\/em>) \u00d7 100).<\/li>\n<li><strong>Bounce Rate<\/strong>: if you send <em>S<\/em> emails and <em>B<\/em> bounce, Bounce Rate = <em>B<\/em>\/<em>S<\/em> (bounces per 100 sent = (<em>B<\/em>\/<em>S<\/em>) \u00d7 100).<\/li>\n<li><strong>Reply Rate<\/strong>: if you have <em>L<\/em> delivered emails and <em>R<\/em> replies, Reply Rate = <em>R<\/em>\/<em>L<\/em> (replies per 100 delivered = (<em>R<\/em>\/<em>L<\/em>) \u00d7 100).<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Map_tool_outcomes_to_the_definitions_so_the_math_is_reproducible\"><\/span>Step 3: Map tool outcomes to the definitions (so the math is reproducible)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Define two terms in your ops doc and keep them stable:<\/p>\n<ul>\n<li><strong>Connected call<\/strong>: the carrier connects the call (a connection event), regardless of whether a person answers.<\/li>\n<li><strong>Human answer<\/strong>: a person answers the call (a human-answer event), not voicemail or an automated message.<\/li>\n<\/ul>\n<p>Then create a mapping table that says which raw outcomes count toward each numerator\/denominator. If you change dialers, update this table the same day.<\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Raw outcome (example)<\/th>\n<th>Counts toward total dials?<\/th>\n<th>Counts toward connected calls?<\/th>\n<th>Counts toward human answers?<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Connected (carrier connected)<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<td>Connected does not imply a human answered.<\/td>\n<\/tr>\n<tr>\n<td>Human answered<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Yes<\/td>\n<td>Use a consistent rule for what qualifies as \u201chuman.\u201d<\/td>\n<\/tr>\n<tr>\n<td>Voicemail reached<\/td>\n<td>Yes<\/td>\n<td>Depends on dialer<\/td>\n<td>No<\/td>\n<td>If your dialer marks voicemail as connected, document it and keep it consistent.<\/td>\n<\/tr>\n<tr>\n<td>Busy \/ no answer \/ failed<\/td>\n<td>Yes<\/td>\n<td>No<\/td>\n<td>No<\/td>\n<td>Still counts as a dial attempt.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>For email, do the same mapping: sent \u2192 denominator for deliverability and bounce; delivered \u2192 denominator for reply and positive reply; bounced \u2192 numerator for bounce (split hard\/soft).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Build_a_weekly_scorecard_that_cant_drift\"><\/span>Step 4: Build a weekly scorecard that can\u2019t drift<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Publish a scorecard with per-100 rates and raw counts. If someone challenges a number, you should be able to trace it back to events.<\/p>\n<ul>\n<li>Phone: total dials, connected calls, human answers, wrong-person confirmations, opt-outs\/suppressions.<\/li>\n<li>Email: sent, delivered, hard bounces, soft bounces, replies, positive replies, unsubscribes\/complaints, suppressions.<\/li>\n<\/ul>\n<p>The trade-off is\u2026 per-100 reporting is easy to read, but it can hide volume changes. Always show raw counts next to rates so leaders can see whether performance changed or volume changed.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Diagnostic_Table\"><\/span>Diagnostic Table:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Use this to triage performance without guessing. It\u2019s written for recruiting ops: what broke, where to look, and what to change.<\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Symptom<\/th>\n<th>Most likely cause<\/th>\n<th>Where to check<\/th>\n<th>What to do next<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Connect Rate drops<\/td>\n<td>Number decay, carrier filtering, or dialer config change<\/td>\n<td>Dialer outcome codes; recency distribution; time-zone call blocks<\/td>\n<td>Increase refresh cadence for active segments; adjust call windows; review caller ID strategy<\/td>\n<\/tr>\n<tr>\n<td>Connect Rate stable, Answer Rate drops<\/td>\n<td>Timing mismatch or caller ID trust issue<\/td>\n<td>Answer Rate by hour\/day; spam labeling reports; caller ID settings<\/td>\n<td>Shift call blocks; rotate caller IDs; tighten targeting to reduce low-intent connects<\/td>\n<\/tr>\n<tr>\n<td>Deliverability Rate drops<\/td>\n<td>Domain reputation or list hygiene issue<\/td>\n<td><strong>Google Postmaster Tools<\/strong> reputation signals; bounce breakdown (hard vs soft)<\/td>\n<td>Pause risky segments; remove hard bounces; slow sending; improve authentication and warm-up practices<\/td>\n<\/tr>\n<tr>\n<td>Hard Bounce Rate rises<\/td>\n<td>Invalid or stale addresses<\/td>\n<td>Hard bounce logs; email recency<\/td>\n<td>Refresh active segments; suppress known-invalid; verify before sending<\/td>\n<\/tr>\n<tr>\n<td>Reply Rate flat, Positive Reply Rate falls<\/td>\n<td>Offer mismatch or role confusion<\/td>\n<td>Reply sentiment tagging; wrong-person confirmations<\/td>\n<td>Fix role\/facility context; tighten filters; include concrete schedule\/call details earlier<\/td>\n<\/tr>\n<tr>\n<td>Wrong-person rate increases<\/td>\n<td>Identity resolution drift (shared lines, similar names, recycled numbers)<\/td>\n<td>Wrong-person flags by source; match confidence<\/td>\n<td>Feed wrong-person outcomes into suppression and matching rules; require identity confirmation in first touch<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Weighted_Checklist\"><\/span>Weighted Checklist:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Score each item 0\u20132 (0 = not in place, 1 = partial, 2 = solid). Multiply by weight. This prioritizes changes that reduce wasted attempts and protect deliverability.<\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Area<\/th>\n<th>Check<\/th>\n<th>Weight<\/th>\n<th>Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Definitions<\/td>\n<td>All teams use the same formulas and denominators (per 100 dials; per 100 sent; per 100 delivered)<\/td>\n<td>5<\/td>\n<td>Stops reporting drift and makes tests comparable<\/td>\n<\/tr>\n<tr>\n<td>Instrumentation<\/td>\n<td>ATS\/CRM captures dial outcomes, delivery\/bounce type, replies, positive replies, and suppression reasons<\/td>\n<td>5<\/td>\n<td>Without fields, you can\u2019t audit or improve<\/td>\n<\/tr>\n<tr>\n<td>Phone reachability<\/td>\n<td>Phone records include recency metadata and a refresh cadence for active segments<\/td>\n<td>4<\/td>\n<td>Prevents wasted dials and repeated carrier failures<\/td>\n<\/tr>\n<tr>\n<td>Email reputation<\/td>\n<td>Deliverability monitored with Google Postmaster Tools; hard\/soft bounces tracked separately<\/td>\n<td>4<\/td>\n<td>Protects domain and keeps the delivered denominator real<\/td>\n<\/tr>\n<tr>\n<td>Suppression<\/td>\n<td>Central suppression list enforced across tools (opt-outs, complaints, wrong-person)<\/td>\n<td>4<\/td>\n<td>Reduces risk and prevents repeat mistakes<\/td>\n<\/tr>\n<tr>\n<td>Identity quality<\/td>\n<td>Wrong-person outcomes are logged and fed back into matching rules<\/td>\n<td>3<\/td>\n<td>Improves candidate experience and recruiter efficiency<\/td>\n<\/tr>\n<tr>\n<td>Execution<\/td>\n<td>Call blocks and email sends are scheduled by time zone and role patterns<\/td>\n<td>3<\/td>\n<td>Improves Answer Rate and reply likelihood without more volume<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_Templates\"><\/span>Outreach Templates:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>These templates are designed to reduce wrong-person outcomes and produce clean measurement. Keep the structure stable while you test one variable at a time.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Phone_opener_30_seconds\"><\/span>Phone opener (30 seconds)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Confirm identity:<\/strong> \u201cHi Dr. [Last Name]\u2014this is [Name]. Quick check: is this still the best number for you?\u201d<\/li>\n<li><strong>If yes:<\/strong> \u201cThanks. I\u2019m recruiting for a [Role] at [Facility\/Group] in [Location]. Do you have 60 seconds now, or should I call back at [two specific windows]?\u201d<\/li>\n<li><strong>If wrong person:<\/strong> \u201cAppreciate it\u2014sorry about that. I\u2019ll remove this number.\u201d (Log wrong-person + suppress.)<\/li>\n<li><strong>What to log:<\/strong> dial outcome, connected flag, human answer flag, wrong-person flag, suppression reason if applicable.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Email_1_identity-first\"><\/span>Email 1 (identity-first)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Quick confirm \u2014 [Role] at [Facility\/Group]?<\/p>\n<p>Hi [First Name] \u2014 I\u2019m recruiting for [Role] at [Facility\/Group] in [Location]. Before I send details, can you confirm this is the right email for you?<\/p>\n<p>If not, reply \u201cno\u201d and I\u2019ll suppress you.<\/p>\n<p>\u2014 [Name], [Title] at Heartbeat.ai<\/p>\n<p><strong>What to log:<\/strong> sent, delivered, bounce type (if any), reply, positive reply, suppression reason.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Email_2_details_next_step\"><\/span>Email 2 (details + next step)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Details + call window?<\/p>\n<p>Thanks, [First Name]. The role is [2\u20133 specifics: schedule\/call\/setting]. If you\u2019re open to a quick call, what\u2019s a good window this week?<\/p>\n<p>If you\u2019d rather not get outreach from me, reply \u201copt out\u201d and I\u2019ll suppress you.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Common_pitfalls\"><\/span>Common pitfalls<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"1_Counting_%E2%80%9Cconnected%E2%80%9D_differently_across_dialers\"><\/span>1) Counting \u201cconnected\u201d differently across dialers<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Some dialers treat voicemail as connected; others don\u2019t. If you change dialers and don\u2019t update your mapping table, your Connect Rate will jump or drop without any real change in reachability.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Measuring_replies_on_sent_instead_of_delivered\"><\/span>2) Measuring replies on sent instead of delivered<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Reply Rate is replies \/ delivered emails. If you use sent as the denominator, you can hide list hygiene problems and misread message performance.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Blending_wrong-person_outcomes_into_%E2%80%9Cnot_interested%E2%80%9D\"><\/span>3) Blending wrong-person outcomes into \u201cnot interested\u201d<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Wrong-person is an identity\/data failure. \u201cNot interested\u201d is a targeting\/offer failure. Keep them separate so you fix the right thing.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"4_Treating_suppression_as_a_manual_side_task\"><\/span>4) Treating suppression as a manual side task<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Suppression must be enforced across tools. If opt-outs live only in an inbox label, you will re-contact people and create avoidable complaints.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"5_Uniqueness_hook_Trust_hub_as_product_prevent_definition_drift\"><\/span>5) Uniqueness hook: Trust hub as product (prevent definition drift)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If definitions live in multiple docs, they will drift. Run your trust hub like a product: one stable, linkable definitions page that every metric\/claims page points to, with a visible <strong>Last reviewed<\/strong> date and a lightweight <strong>Change log<\/strong> that records what changed and why.<\/p>\n<ul>\n<li><strong>Owner:<\/strong> recruiting ops (or RevOps) owns the definitions; marketing can format, but ops owns meaning.<\/li>\n<li><strong>Cadence:<\/strong> review on tool changes (dialer\/ESP\/ATS) and quarterly otherwise.<\/li>\n<li><strong>UI note:<\/strong> publish a hub \u201ccard grid\u201d for Definitions \/ Testing \/ Sources \/ Ethics \/ Not HIPAA \/ Editorial \/ Corrections \/ Security, and show \u201cLast reviewed\u201d + \u201cChange log\u201d on each page.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"How_to_improve_results\"><\/span>How to improve results<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Improvement starts with measurement hygiene. If you can\u2019t trust the denominator, you can\u2019t trust the change.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Measurement_instructions_required\"><\/span>Measurement instructions (required)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Measure this by\u2026 building a weekly scorecard that reports each metric with its canonical denominator and includes raw counts next to the rate.<\/p>\n<ul>\n<li><strong>Connect Rate<\/strong> = connected calls \/ total dials. Report: connected calls per 100 dials + raw counts (connected calls, total dials).<\/li>\n<li><strong>Answer Rate<\/strong> = human answers \/ connected calls. Report: human answers per 100 connected calls + raw counts.<\/li>\n<li><strong>Deliverability Rate<\/strong> = delivered emails \/ sent emails. Report: delivered per 100 sent + raw counts.<\/li>\n<li><strong>Bounce Rate<\/strong> = bounced emails \/ sent emails. Report: bounces per 100 sent, split hard\/soft + raw counts.<\/li>\n<li><strong>Reply Rate<\/strong> = replies \/ delivered emails. Report: replies per 100 delivered + raw counts.<\/li>\n<\/ul>\n<p>Also track wrong-person rate per channel (phone: wrong-person per 100 dials; email: wrong-person per 100 delivered emails) and suppression volume by reason.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Operational_levers_that_usually_move_the_numbers\"><\/span>Operational levers that usually move the numbers<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Connect Rate<\/strong>: refresh active segments; call in role-appropriate windows; reduce repeated attempts to stale numbers; keep caller ID strategy consistent. Heartbeat.ai supports workflows that include <strong>ranked mobile numbers by answer probability<\/strong> so recruiters spend dials where answers are more likely.<\/li>\n<li><strong>Answer Rate<\/strong>: adjust call blocks; tighten targeting; confirm identity in the opener to reduce defensive screening.<\/li>\n<li><strong>Deliverability Rate<\/strong>: monitor domain reputation signals (Google Postmaster Tools), suppress risky segments quickly, and keep bounce handling strict.<\/li>\n<li><strong>Reply Rate<\/strong>: shorten the first email, confirm identity, and ask for a specific next step (a call window). Keep the template stable while testing one variable at a time.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"ATSCRM_field_map_compact\"><\/span>ATS\/CRM field map (compact)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Here\u2019s a minimal field map that supports the definitions above and keeps reporting auditable across tools.<\/p>\n<div class=\"table-scroll\" style=\"overflow:auto;-webkit-overflow-scrolling:touch;width:100%\">\n<table class=\"separated-content\">\n<thead>\n<tr>\n<th>Metric<\/th>\n<th>Minimum fields\/events to log<\/th>\n<th>System of record<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Connect Rate<\/td>\n<td>dial_timestamp, dial_outcome, connected_flag<\/td>\n<td>Dialer (synced to ATS\/CRM)<\/td>\n<\/tr>\n<tr>\n<td>Answer Rate<\/td>\n<td>human_answer_flag, call_duration_seconds (optional), answer_timestamp<\/td>\n<td>Dialer<\/td>\n<\/tr>\n<tr>\n<td>Deliverability Rate<\/td>\n<td>email_sent_timestamp, delivered_flag, bounce_flag, bounce_type<\/td>\n<td>Email provider \/ outreach tool<\/td>\n<\/tr>\n<tr>\n<td>Bounce Rate<\/td>\n<td>bounce_flag, bounce_type (hard\/soft)<\/td>\n<td>Email provider \/ outreach tool<\/td>\n<\/tr>\n<tr>\n<td>Reply Rate<\/td>\n<td>reply_flag, reply_timestamp, reply_thread_id<\/td>\n<td>Email provider \/ outreach tool<\/td>\n<\/tr>\n<tr>\n<td>Positive Reply Rate<\/td>\n<td>positive_reply_flag (manual tag or classifier), tag_timestamp<\/td>\n<td>ATS\/CRM (review workflow)<\/td>\n<\/tr>\n<tr>\n<td>Wrong-person rate<\/td>\n<td>wrong_person_flag, wrong_person_channel, confirmation_timestamp<\/td>\n<td>ATS\/CRM<\/td>\n<\/tr>\n<tr>\n<td>Suppression<\/td>\n<td>suppression_flag, suppression_reason, suppression_timestamp<\/td>\n<td>ATS\/CRM (enforced across tools)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Legal_and_ethical_use\"><\/span>Legal and ethical use<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This page defines measurement terms and operational logging. It is not legal advice. Use these metrics to run legitimate recruiting outreach with clear opt-out handling and respectful contact frequency.<\/p>\n<ul>\n<li><strong>Honor opt-outs<\/strong> and suppress across all tools.<\/li>\n<li><strong>Minimize data<\/strong>: store what you need to recruit and measure; avoid collecting sensitive information you don\u2019t need.<\/li>\n<li><strong>Be transparent<\/strong>: identify yourself, your purpose, and provide a simple opt-out path.<\/li>\n<\/ul>\n<p>Do not represent any dataset as \u201cHIPAA compliant,\u201d \u201csafe harbor,\u201d or \u201cguaranteed accurate.\u201d Heartbeat does not provide legal counsel.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Evidence_and_trust_notes\"><\/span>Evidence and trust notes<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>This page is part of the Heartbeat trust methodology hub. If you want the broader context for how we define and test quality, start here: <a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/\">Heartbeat trust methodology<\/a>.<\/p>\n<p>Related trust detail: <a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/how-we-test-contact-data-quality\/\">How we test contact data quality<\/a>.<\/p>\n<p>Implementation notes and editorial stability should follow user-first documentation principles. References:<\/p>\n<ul>\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/creating-helpful-content\">Google: Creating helpful, reliable, people-first content<\/a><\/li>\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/fundamentals\/e-e-a-t\">Google: E-E-A-T<\/a><\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"FAQs\"><\/span>FAQs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"What_is_the_connect_rate_definition_for_recruiters\"><\/span>What is the connect rate definition for recruiters?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Connect Rate = connected calls \/ total dials. Report it as connected calls per 100 dials, and keep the definition stable across teams and tools.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Whats_the_difference_between_connect_rate_and_answer_rate\"><\/span>What\u2019s the difference between connect rate and answer rate?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Connect Rate is connected calls per 100 dials. Answer Rate is human answers per 100 connected calls. Use both so you can separate reachability from call timing and trust.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_you_define_deliverability_rate_and_bounce_rate_for_recruiting_email\"><\/span>How do you define deliverability rate and bounce rate for recruiting email?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Deliverability Rate = delivered emails \/ sent emails (delivered per 100 sent). Bounce Rate = bounced emails \/ sent emails (bounces per 100 sent), split into hard and soft bounces.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_you_calculate_reply_rate\"><\/span>How do you calculate reply rate?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Reply Rate = replies \/ delivered emails. Use delivered as the denominator so bounces don\u2019t distort the result.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_should_we_log_to_make_these_metrics_auditable\"><\/span>What should we log to make these metrics auditable?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Log the raw events that create the numerators and denominators: dials, connected calls, human answers, sent, delivered, bounce type, replies, positive replies, wrong-person confirmations, and suppression reasons.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Next_steps\"><\/span>Next steps<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>Interpretation deep-dive: <a href=\"http:\/\/heartbeat.ai\/resources\/data-quality-verification\/connect-rate-vs-answer-rate\/\">Connect rate vs answer rate<\/a>.<\/li>\n<li>Operational tracking: <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/ats-field-schema-for-outreach-metrics\/\">ATS\/CRM field schema for outreach metrics<\/a>.<\/li>\n<li>Email measurement workflow: <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/\">Reply rate tracking for physician outreach<\/a>.<\/li>\n<li>Data freshness ops: <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/provider-data-refresh-cadence\/\">Provider data refresh cadence<\/a>.<\/li>\n<li>Instrument this in your workflow: <a href=\"https:\/\/heartbeat.ai\/signup\">Create a Heartbeat.ai account<\/a>.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"About_the_Author\"><\/span><b>About the Author<\/b><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\"><span style=\"font-weight: 400;\">Ben Argeband<\/span><\/a><span style=\"font-weight: 400;\"> is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben&#8217;s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on <\/span><a href=\"https:\/\/www.linkedin.com\/in\/ben-m-argeband-2427a8a3\/\"><span style=\"font-weight: 400;\">LinkedIn<\/span><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"author\":{\"@type\":\"Person\",\"jobTitle\":\"Founder & CEO of Heartbeat.ai\",\"name\":\"Ben Argeband\"},\"description\":\"Canonical recruiting outreach metric definitions with formulas and denominators: connect rate, answer rate, deliverability, bounce rate, reply rate, plus what to log, how to measure per 100, and how to prevent definition drift.\",\"headline\":\"Connect rate definition for recruiters\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Connect Rate = connected calls \/ total dials. Report it as connected calls per 100 dials, and keep the definition stable across teams and tools.\"},\"name\":\"What is the connect rate definition for recruiters?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Connect Rate is connected calls per 100 dials. Answer Rate is human answers per 100 connected calls. Use both so you can separate reachability from call timing and trust.\"},\"name\":\"What\u2019s the difference between connect rate and answer rate?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Deliverability Rate = delivered emails \/ sent emails (delivered per 100 sent). Bounce Rate = bounced emails \/ sent emails (bounces per 100 sent), split into hard and soft bounces.\"},\"name\":\"How do you define deliverability rate and bounce rate for recruiting email?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Reply Rate = replies \/ delivered emails. Use delivered as the denominator so bounces don\u2019t distort the result.\"},\"name\":\"How do you calculate reply rate?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Log the raw events that create the numerators and denominators: dials, connected calls, human answers, sent, delivered, bounce type, replies, positive replies, wrong-person confirmations, and suppression reasons.\"},\"name\":\"What should we log to make these metrics auditable?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>Canonical recruiting outreach metric definitions with formulas and denominators: connect rate, answer rate, deliverability, bounce rate, reply rate, plus what to log, how to measure per 100, and how to prevent definition drift.<\/p>","protected":false},"author":5,"featured_media":54134,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"connect rate definition for recruiters","_yoast_wpseo_title":"Connect rate definition for recruiters (formulas + how to measure)","_yoast_wpseo_metadesc":"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.","_custom_permalink":"trust-methodology\/accuracy-and-metrics-definitions","footnotes":""},"categories":[1],"tags":[],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\r\n<title>Connect rate definition for recruiters (formulas + how to measure)<\/title>\r\n<meta name=\"description\" content=\"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.\" \/>\r\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\r\n<link rel=\"canonical\" href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Connect rate definition for recruiters (formulas + how to measure)\" \/>\r\n<meta property=\"og:description\" content=\"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T18:21:22+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-02-27T19:31:07+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png\" \/>\r\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:height\" content=\"1024\" \/>\r\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\r\n<meta name=\"author\" content=\"Ben Argeband\" \/>\r\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\r\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ben Argeband\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#article\",\"isPartOf\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Connect rate definition for recruiters (canonical formulas + how to measure)\",\"datePublished\":\"2026-02-01T18:21:22+00:00\",\"dateModified\":\"2026-02-27T19:31:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\"},\"wordCount\":2782,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\",\"url\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\",\"name\":\"Connect rate definition for recruiters (formulas + how to measure)\",\"isPartOf\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png\",\"datePublished\":\"2026-02-01T18:21:22+00:00\",\"dateModified\":\"2026-02-27T19:31:07+00:00\",\"description\":\"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.\",\"breadcrumb\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage\",\"url\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png\",\"contentUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/heartbeat.ai\/healthcare\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Connect rate definition for recruiters (canonical formulas + how to measure)\"}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#website\",\"url\":\"http:\/\/heartbeat.ai\/resources\/\",\"name\":\"Heartbeat.ai\",\"description\":\"\",\"publisher\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/heartbeat.ai\/resources\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\",\"name\":\"Heartbeat.ai\",\"url\":\"http:\/\/heartbeat.ai\/resources\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png\",\"contentUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png\",\"width\":704,\"height\":126,\"caption\":\"Heartbeat.ai\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173\",\"name\":\"Ben Argeband\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/image\/\",\"url\":\"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g\",\"contentUrl\":\"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g\",\"caption\":\"Ben Argeband\"},\"url\":\"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/\"}]}<\/script>\r\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Connect rate definition for recruiters (formulas + how to measure)","description":"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/","og_locale":"en_US","og_type":"article","og_title":"Connect rate definition for recruiters (formulas + how to measure)","og_description":"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.","og_url":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T18:21:22+00:00","article_modified_time":"2026-02-27T19:31:07+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Connect rate definition for recruiters (canonical formulas + how to measure)","datePublished":"2026-02-01T18:21:22+00:00","dateModified":"2026-02-27T19:31:07+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/"},"wordCount":2782,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/","url":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/","name":"Connect rate definition for recruiters (formulas + how to measure)","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png","datePublished":"2026-02-01T18:21:22+00:00","dateModified":"2026-02-27T19:31:07+00:00","description":"Connect Rate = connected calls \/ total dials. Canonical definitions for answer rate, deliverability, bounce rate, reply rate, plus what to log and how to measure per 100.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#primaryimage","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/accuracy-and-metrics-definitions-906f72b4.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/trust-methodology\/accuracy-and-metrics-definitions\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/heartbeat.ai\/healthcare\/"},{"@type":"ListItem","position":2,"name":"Connect rate definition for recruiters (canonical formulas + how to measure)"}]},{"@type":"WebSite","@id":"http:\/\/heartbeat.ai\/resources\/#website","url":"http:\/\/heartbeat.ai\/resources\/","name":"Heartbeat.ai","description":"","publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/heartbeat.ai\/resources\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"http:\/\/heartbeat.ai\/resources\/#organization","name":"Heartbeat.ai","url":"http:\/\/heartbeat.ai\/resources\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2021\/04\/Heartbeat.ai-logo.png","width":704,"height":126,"caption":"Heartbeat.ai"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173","name":"Ben Argeband","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/image\/","url":"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g","contentUrl":"http:\/\/0.gravatar.com\/avatar\/6356f96884d5a313d758128b3d9aaef7?s=96&d=mm&r=g","caption":"Ben Argeband"},"url":"http:\/\/heartbeat.ai\/resources\/author\/ben-argeband\/"}]}},"_links":{"self":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54135"}],"collection":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/comments?post=54135"}],"version-history":[{"count":2,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54135\/revisions"}],"predecessor-version":[{"id":54444,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54135\/revisions\/54444"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54134"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54135"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54135"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}