{"id":54110,"date":"2026-02-01T12:17:11","date_gmt":"2026-02-01T18:17:11","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/reply-rate-tracking-for-physician-outreach\/"},"modified":"2026-08-31T08:45:20","modified_gmt":"2026-08-31T13:45:20","slug":"reply-rate-tracking-for-physician-outreach","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/","title":{"rendered":"Reply Rate Tracking for Physician Outreach (ATS Field Map, Strict Campaign Windows, Weekly Report)"},"content":{"rendered":"<p class=\"article-last-updated\"><strong>Last updated:<\/strong> August 31, 2026<\/p>\n<p><strong>By Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 Extremely operational: tables, definitions, logging fields.<\/p>\n<p>Physician outreach fails in two ways that look identical in a pipeline meeting: your emails aren&#8217;t getting delivered, or they&#8217;re delivered but your targeting or message isn&#8217;t connecting. If you don&#8217;t measure those separately, you&#8217;ll waste time rewriting copy that never reached the inbox. This playbook gives you a measurement spine \u2014 definitions, an ATS field map, ownership, and a weekly report \u2014 so you can fix the right thing first.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 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\" style=\"cursor:inherit\">What\u2019s 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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#The_measure-then-fix_ladder_deliverability_reply_positive_reply\" >The measure-then-fix ladder: deliverability, reply, positive reply<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_1_Lock_definitions_and_denominators\" >Step 1: Lock definitions and denominators<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_2_Choose_your_unit_of_analysis\" >Step 2: Choose your unit of analysis<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_3_Instrument_the_funnel\" >Step 3: Instrument the funnel<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_4_Standardize_what_%E2%80%9Cpositive%E2%80%9D_means\" >Step 4: Standardize what &#8220;positive&#8221; means<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_5_Build_the_ATS_field_map_and_data_dictionary\" >Step 5: Build the ATS field map and data dictionary<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#ATS_data_dictionary\" >ATS data dictionary<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#If_your_ATS_cant_support_campaigns\" >If your ATS can&#8217;t support campaigns<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Ownership_and_cadence\" >Ownership and cadence<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_6_Deliverability_monitoring_and_spam_complaint_proxies\" >Step 6: Deliverability monitoring and spam complaint proxies<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Step_7_Build_the_weekly_report\" >Step 7: Build the weekly report<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-16\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-17\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-18\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Template_1_Email_first_touch_%E2%80%94_fast_yesno\" >Template 1: Email (first touch) \u2014 fast yes\/no<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Template_2_Email_follow-up_%E2%80%94_constraint-first\" >Template 2: Email (follow-up) \u2014 constraint-first<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Template_3_SMS_after_an_email_open_or_call_attempt\" >Template 3: SMS (after an email open or call attempt)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-21\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Template_4_Voicemail_measurable_next_step\" >Template 4: Voicemail (measurable 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-22\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-23\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Pitfall_1_Calculating_reply_rate_on_sent_not_delivered\" >Pitfall 1: Calculating reply rate on sent, not delivered<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Pitfall_2_Counting_auto-replies_as_replies\" >Pitfall 2: Counting auto-replies as replies<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-25\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Pitfall_3_Letting_each_recruiter_self-grade_%E2%80%9Cpositive%E2%80%9D\" >Pitfall 3: Letting each recruiter self-grade &#8220;positive&#8221;<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-26\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Pitfall_4_Suppression_failures\" >Pitfall 4: Suppression failures<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-27\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Pitfall_5_Double-counting_cross-channel_replies\" >Pitfall 5: Double-counting cross-channel replies<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-29\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#1_Fix_deliverability_before_you_touch_messaging\" >1) Fix deliverability before you touch messaging<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#2_Run_one-variable_tests_on_reply_rate_at_the_campaign_level\" >2) Run one-variable tests on reply rate at the campaign level<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#3_Improve_positive_replies_by_removing_basic_questions_from_the_thread\" >3) Improve positive replies by removing basic questions from the thread<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#4_Enforce_change-log_discipline\" >4) Enforce change-log discipline<\/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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-34\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-35\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-36\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#What_is_reply_rate_in_physician_outreach\" >What is reply rate in physician outreach?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-37\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Should_reply_rate_be_calculated_on_delivered_or_sent\" >Should reply rate be calculated on delivered or sent?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-38\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#What_counts_as_a_positive_reply\" >What counts as a positive reply?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-39\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Do_auto-replies_or_out-of-office_messages_count_as_replies\" >Do auto-replies or out-of-office messages count as replies?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-40\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#Do_unsubscribes_count_as_replies\" >Do unsubscribes count as replies?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-41\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#How_do_I_avoid_double-counting_replies_across_email_and_SMS\" >How do I avoid double-counting replies across email and SMS?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-42\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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-43\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#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 is for <strong>recruiters and ops teams who want consistent outreach reporting<\/strong> across email, SMS, and call sequences, without metric drift when tools or recruiters change.<\/p>\n<ul>\n<li>Recruiting ops building weekly reporting and coaching loops<\/li>\n<li>Agency owners who need predictable throughput and fewer wasted touches<\/li>\n<li>Recruiters who want to know whether to fix list quality, targeting, or copy<\/li>\n<\/ul>\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>Track reply rate using delivered emails as the denominator, dedupe to one reply per person per campaign, and label positive replies with a shared rubric.<\/dd>\n<dt>Key Insight<\/dt>\n<dd>Separate deliverability from replies so you don&#8217;t confuse list or domain problems with messaging problems.<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiters and ops teams who want consistent outreach reporting.<\/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=\"The_measure-then-fix_ladder_deliverability_reply_positive_reply\"><\/span>The measure-then-fix ladder: deliverability, reply, positive reply<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ol>\n<li><strong>Deliverability<\/strong>: did the email get delivered (not bounced)?<\/li>\n<li><strong>Reply<\/strong>: did a human reply at all?<\/li>\n<li><strong>Positive Reply<\/strong>: did the reply create a next step (call, details, timing)?<\/li>\n<\/ol>\n<p>Operational rule: don&#8217;t touch messaging until deliverability is stable, and don&#8217;t celebrate replies until you can separate positive replies from everything else.<\/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_Lock_definitions_and_denominators\"><\/span>Step 1: Lock definitions and denominators<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Deliverability Rate<\/strong> = delivered emails \/ sent emails<\/li>\n<li><strong>Bounce Rate<\/strong> = bounced emails \/ sent emails<\/li>\n<li><strong>Reply Rate<\/strong> = replies \/ delivered emails<\/li>\n<li><strong>Positive Reply Rate<\/strong> = positive replies \/ delivered emails<\/li>\n<\/ul>\n<p>Two rules that prevent bad math:<\/p>\n<ul>\n<li>Reply metrics use <strong>delivered<\/strong> as the denominator so bounces don&#8217;t hide inside a low reply number.<\/li>\n<li>Count <strong>a maximum of one reply per person per campaign<\/strong> unless you explicitly want a raw total.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Choose_your_unit_of_analysis\"><\/span>Step 2: Choose your unit of analysis<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Pick a primary rollup and keep it consistent:<\/p>\n<ul>\n<li><strong>Campaign<\/strong> (recommended): a defined list, sequence, and time window, e.g. &#8220;Cardiology-Hospital-2026W03&#8221;.<\/li>\n<li><strong>Recruiter-week<\/strong>: best for coaching and capacity planning.<\/li>\n<li><strong>Req<\/strong>: best for hiring manager updates, but can mask list quality issues when sourcing is shared across reqs.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Instrument_the_funnel\"><\/span>Step 3: Instrument the funnel<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Track these counts per campaign:<\/p>\n<ul>\n<li>Sent emails<\/li>\n<li>Delivered emails<\/li>\n<li>Bounced emails (hard vs. soft, if available)<\/li>\n<li>Replies (any)<\/li>\n<li>Positive replies<\/li>\n<li>Opt-outs \/ unsubscribes<\/li>\n<li>Spam complaint proxy signals (see Step 6)<\/li>\n<\/ul>\n<p><strong>This requires manual verification.<\/strong> Most sequencing tools capture replies automatically, but positive-versus-negative classification and dedup (one reply per person per campaign) still need a lightweight review step. Skip it and your &#8220;positive reply&#8221; metric becomes recruiter-dependent and unusable for ops comparisons.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Standardize_what_%E2%80%9Cpositive%E2%80%9D_means\"><\/span>Step 4: Standardize what &#8220;positive&#8221; means<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Positive<\/strong>: &#8220;Yes, send details,&#8221; &#8220;Call me after clinic,&#8221; &#8220;I&#8217;m open to locums in March,&#8221; &#8220;Can you share comp and call?&#8221;<\/li>\n<li><strong>Neutral<\/strong>: &#8220;Not now,&#8221; &#8220;Maybe later.&#8221;<\/li>\n<li><strong>Negative<\/strong>: &#8220;Not interested,&#8221; &#8220;Stop emailing me,&#8221; &#8220;Wrong specialty.&#8221;<\/li>\n<\/ul>\n<p>Rule: if it doesn&#8217;t move you toward a call or a defined next step, it isn&#8217;t positive.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_Build_the_ATS_field_map_and_data_dictionary\"><\/span>Step 5: Build the ATS field map and data dictionary<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>This is the measurement spine. Your sequencing tool can change; your ATS or CRM is where reporting should survive.<\/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 \/ Attribute<\/th>\n<th>Where it lives<\/th>\n<th>Field name (example)<\/th>\n<th>How it&#8217;s populated<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Campaign ID<\/td>\n<td>ATS\/CRM<\/td>\n<td>Outreach Campaign<\/td>\n<td>Manual picklist<\/td>\n<td>Naming convention: Specialty-Setting-YYYYW## (no free-text)<\/td>\n<\/tr>\n<tr>\n<td>Campaign Start Date<\/td>\n<td>ATS\/CRM<\/td>\n<td>Campaign Start<\/td>\n<td>Auto or manual<\/td>\n<td>Recommended: add Campaign End to enforce a strict campaign window for dedupe and audits<\/td>\n<\/tr>\n<tr>\n<td>Campaign End Date<\/td>\n<td>ATS\/CRM<\/td>\n<td>Campaign End<\/td>\n<td>Auto or manual<\/td>\n<td>Recommended for clean weekly rollups and cross-channel dedupe<\/td>\n<\/tr>\n<tr>\n<td>Channel<\/td>\n<td>ATS\/CRM<\/td>\n<td>Outreach Channel<\/td>\n<td>Manual picklist<\/td>\n<td>Email \/ SMS \/ Call \/ Mixed<\/td>\n<\/tr>\n<tr>\n<td>Sent count<\/td>\n<td>Sequencer export<\/td>\n<td>Emails Sent<\/td>\n<td>Weekly import<\/td>\n<td>Integer per campaign<\/td>\n<\/tr>\n<tr>\n<td>Delivered count<\/td>\n<td>Sequencer export<\/td>\n<td>Emails Delivered<\/td>\n<td>Weekly import<\/td>\n<td>Integer per campaign; denominator for reply metrics<\/td>\n<\/tr>\n<tr>\n<td>Bounced count<\/td>\n<td>Sequencer export<\/td>\n<td>Emails Bounced<\/td>\n<td>Weekly import<\/td>\n<td>Split hard\/soft if possible<\/td>\n<\/tr>\n<tr>\n<td>Reply count<\/td>\n<td>Sequencer + ops review<\/td>\n<td>Email Replies<\/td>\n<td>Weekly import + audit<\/td>\n<td>Deduplicate to 1 reply\/person\/campaign<\/td>\n<\/tr>\n<tr>\n<td>Positive reply count<\/td>\n<td>ATS\/CRM<\/td>\n<td>Positive Replies<\/td>\n<td>Manual tagging<\/td>\n<td>Use the rubric from Step 4<\/td>\n<\/tr>\n<tr>\n<td>Opt-out<\/td>\n<td>ATS\/CRM<\/td>\n<td>Do Not Contact<\/td>\n<td>Immediate manual update<\/td>\n<td>Must suppress across all tools<\/td>\n<\/tr>\n<tr>\n<td>Source<\/td>\n<td>ATS\/CRM<\/td>\n<td>Source Detail<\/td>\n<td>Auto or manual<\/td>\n<td>Include Heartbeat.ai when applicable<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><span class=\"ez-toc-section\" id=\"ATS_data_dictionary\"><\/span>ATS data dictionary<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Outreach Campaign<\/strong> (picklist): format Specialty-Setting-YYYYW##. No free-text values.<\/li>\n<li><strong>Campaign Window<\/strong>: defined by Campaign Start and Campaign End. If you can&#8217;t store an end date, define a fixed window rule in ops (for example, Monday through Sunday of the campaign week).<\/li>\n<li><strong>Outreach Channel<\/strong> (picklist): Email, SMS, Call, Mixed.<\/li>\n<li><strong>Reply (boolean)<\/strong>: true if any non-auto reply is received from the person within the campaign window.<\/li>\n<li><strong>Positive Reply (boolean)<\/strong>: true if the reply meets the Step 4 rubric.<\/li>\n<li><strong>Reply Dedupe Rule<\/strong>: count a maximum of one reply per person per campaign regardless of channel.<\/li>\n<li><strong>Reply Timestamp<\/strong> (datetime): first reply time in the campaign window.<\/li>\n<li><strong>Do Not Contact<\/strong> (boolean): true if an opt-out was requested; must sync to all tools.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"If_your_ATS_cant_support_campaigns\"><\/span>If your ATS can&#8217;t support campaigns<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>Keep a <strong>campaign ledger<\/strong> spreadsheet with Campaign ID, start\/end dates, and weekly counts (sent, delivered, bounced, replies, positive, opt-outs).<\/li>\n<li>On each candidate record, store only Outreach Campaign ID, Reply, Positive Reply, and Do Not Contact.<\/li>\n<li>Do weekly rollups from the ledger, not from ad-hoc recruiter notes.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Ownership_and_cadence\"><\/span>Ownership and cadence<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Recruiter (daily)<\/strong>: tag Reply and Positive Reply; apply Do Not Contact immediately when requested.<\/li>\n<li><strong>Ops (weekly)<\/strong>: import sent\/delivered\/bounced\/reply counts; audit a sample of reply labels for consistency.<\/li>\n<li><strong>Ops (weekly)<\/strong>: review Postmaster Tools and proxy signals; log any deliverability incidents.<\/li>\n<li><strong>Recruiting lead (weekly)<\/strong>: review the one-page report and approve one-variable tests for the next week.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_6_Deliverability_monitoring_and_spam_complaint_proxies\"><\/span>Step 6: Deliverability monitoring and spam complaint proxies<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Deliverability is more than bounces. You need domain-level monitoring plus internal proxy signals to catch reputation issues early. For Google Workspace domains, <strong>Postmaster Tools<\/strong> reports domain-level reputation and delivery trends, not per-recipient inbox placement.<\/p>\n<p><strong>Spam complaint proxy signals<\/strong><\/p>\n<ul>\n<li>A sudden drop in Deliverability Rate without a list-source change<\/li>\n<li>A sudden rise in Bounce Rate, especially hard bounces<\/li>\n<li>A spike in opt-outs for a campaign compared to the prior 2\u20134 weeks for the same sending domain and specialty slice<\/li>\n<li>An increase in replies like &#8220;stop,&#8221; &#8220;spam,&#8221; or &#8220;remove me&#8221; (tag as negative plus compliance)<\/li>\n<li>Postmaster Tools trend deterioration coinciding with reply-rate drops<\/li>\n<\/ul>\n<p>Action rule: if proxy signals spike, pause scaling volume, audit suppression, and fix list quality before testing new copy.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_7_Build_the_weekly_report\"><\/span>Step 7: Build the weekly report<span class=\"ez-toc-section-end\"><\/span><\/h3>\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>Week<\/th>\n<th>Campaign<\/th>\n<th>Sent<\/th>\n<th>Delivered<\/th>\n<th>Bounced<\/th>\n<th>Replies<\/th>\n<th>Positive Replies<\/th>\n<th>Deliverability Rate<\/th>\n<th>Bounce Rate<\/th>\n<th>Reply Rate<\/th>\n<th>Positive Reply Rate<\/th>\n<th>Notes \/ Changes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>YYYY-WW<\/td>\n<td>Specialty-Setting-YYYYW##<\/td>\n<td>#<\/td>\n<td>#<\/td>\n<td>#<\/td>\n<td>#<\/td>\n<td>#<\/td>\n<td>Delivered\/Sent<\/td>\n<td>Bounced\/Sent<\/td>\n<td>Replies\/Delivered<\/td>\n<td>PosReplies\/Delivered<\/td>\n<td>List source, domain, sequence version, send window, suppression update<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Diagnostic_table\"><\/span>Diagnostic table<span class=\"ez-toc-section-end\"><\/span><\/h2>\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>What you see<\/th>\n<th>Most likely cause<\/th>\n<th>What to check next<\/th>\n<th>Fix (fastest first)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>High bounce rate, low delivered<\/td>\n<td>Bad emails \/ stale data<\/td>\n<td>Bounce type (hard vs. soft), list source, recent imports<\/td>\n<td>Verify\/suppress risky addresses; tighten sourcing inputs; re-run verification before next send<\/td>\n<\/tr>\n<tr>\n<td>Stable deliverability, low reply rate<\/td>\n<td>Targeting or message mismatch<\/td>\n<td>Specialty fit, geography, clarity of schedule\/call\/comp, subject line relevance<\/td>\n<td>Adjust targeting slice; rewrite the first two lines for relevance; test one variable per week<\/td>\n<\/tr>\n<tr>\n<td>Replies exist, but low positive reply<\/td>\n<td>Offer friction or unclear next step<\/td>\n<td>Do replies ask basic questions you didn&#8217;t answer?<\/td>\n<td>Add minimum viable clarity; tighten the CTA to a specific scheduling ask<\/td>\n<\/tr>\n<tr>\n<td>Reply rate drops suddenly across campaigns<\/td>\n<td>Deliverability incident or suppression failure<\/td>\n<td>Postmaster Tools trend change, opt-out spike, recent tool\/domain\/list change<\/td>\n<td>Pause scaling volume; audit suppression; fix list quality before copy tests<\/td>\n<\/tr>\n<tr>\n<td>Reply counts look inflated<\/td>\n<td>Double-counting across channels or threads<\/td>\n<td>Are email and SMS replies both being counted for the same person\/campaign?<\/td>\n<td>Enforce one reply per person per campaign regardless of channel; store Reply Timestamp for audit<\/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<ul>\n<li><strong>(5) Definitions locked<\/strong>: deliverability rate, bounce rate, reply rate, and positive reply rate documented and shared.<\/li>\n<li><strong>(5) Denominators enforced<\/strong>: reply metrics use delivered emails; bounce uses sent emails.<\/li>\n<li><strong>(4) Campaign naming convention<\/strong>: strict IDs across ATS\/CRM and sequencing exports.<\/li>\n<li><strong>(4) Suppression workflow<\/strong>: opt-outs update a single source of truth and sync to all tools within 24 hours.<\/li>\n<li><strong>(4) Positive reply rubric<\/strong>: binary rubric with examples, plus a weekly calibration sample.<\/li>\n<li><strong>(3) Weekly report cadence<\/strong>: same day and time, one table, notes required.<\/li>\n<li><strong>(3) Deliverability monitoring<\/strong>: Postmaster Tools checked weekly; incidents logged.<\/li>\n<li><strong>(2) Audit trail<\/strong>: random sample of replies reviewed weekly for misclassification.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_templates\"><\/span>Outreach templates<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Template_1_Email_first_touch_%E2%80%94_fast_yesno\"><\/span>Template 1: Email (first touch) \u2014 fast yes\/no<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Quick question \u2014 {Specialty} role near {City}<\/p>\n<p>Dr. {LastName} \u2014 recruiting for a {Specialty} opening with {EmployerType} near {City}. Is it worth sending details, or should I close the loop?<\/p>\n<p>If yes, what&#8217;s the best number or time to reach you after clinic this week?<\/p>\n<p>\u2014 {YourName}<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_2_Email_follow-up_%E2%80%94_constraint-first\"><\/span>Template 2: Email (follow-up) \u2014 constraint-first<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Re: {Specialty} \u2014 schedule \/ call \/ comp<\/p>\n<p>Keeping this tight: what matters most for you right now \u2014 schedule, call, comp, or location?<\/p>\n<p>If you reply with one word (schedule\/call\/comp\/location), I&#8217;ll send only the relevant details.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_SMS_after_an_email_open_or_call_attempt\"><\/span>Template 3: SMS (after an email open or call attempt)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Dr. {LastName}, this is {YourName} re: a {Specialty} role near {City}. OK to text you details here, or prefer email?<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_4_Voicemail_measurable_next_step\"><\/span>Template 4: Voicemail (measurable next step)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi Dr. {LastName}, {YourName} calling about a {Specialty} opportunity near {City}. If you&#8217;re open to details, text me &#8220;yes&#8221; at {Number} and I&#8217;ll send a one-page summary. If not, text &#8220;no&#8221; and I&#8217;ll stop.<\/p>\n<p>If you&#8217;re sourcing physicians with Heartbeat.ai, you can operationalize this faster by using ranked mobile numbers by answer probability and keeping campaign IDs consistent from day one.<\/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=\"Pitfall_1_Calculating_reply_rate_on_sent_not_delivered\"><\/span>Pitfall 1: Calculating reply rate on sent, not delivered<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If you calculate replies divided by sent, you hide deliverability issues inside a low reply number. Use replies divided by delivered so you can see whether the message is failing or the email never arrived.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_2_Counting_auto-replies_as_replies\"><\/span>Pitfall 2: Counting auto-replies as replies<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Exclude auto-replies and out-of-office messages from reply rate. Track them separately if you need an operational reminder to follow up later.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_3_Letting_each_recruiter_self-grade_%E2%80%9Cpositive%E2%80%9D\"><\/span>Pitfall 3: Letting each recruiter self-grade &#8220;positive&#8221;<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Without a rubric and calibration, your positive reply metric becomes inconsistent across recruiters. Use the Step 4 rubric and audit a small sample weekly.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_4_Suppression_failures\"><\/span>Pitfall 4: Suppression failures<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If opt-outs aren&#8217;t centralized and synced, you&#8217;ll keep contacting people who asked you to stop. That&#8217;s a compliance risk, and it can damage deliverability over time.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_5_Double-counting_cross-channel_replies\"><\/span>Pitfall 5: Double-counting cross-channel replies<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>For clean ops reporting, count one reply per person per campaign regardless of channel, and store the first Reply Timestamp for audit.<\/p>\n<p>Once measurement is clean, if you need the behavioral side, read <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/why-physicians-dont-reply\/\">why physicians don&#8217;t reply (and what to do about it)<\/a>.<\/p>\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<h3><span class=\"ez-toc-section\" id=\"1_Fix_deliverability_before_you_touch_messaging\"><\/span>1) Fix deliverability before you touch messaging<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>Verify and suppress risky emails before sending, especially on older lists.<\/li>\n<li>Segment reporting by list source and sending domain so you can isolate the problem.<\/li>\n<li>Use Postmaster Tools trends plus your proxy signals from Step 6 to catch issues early.<\/li>\n<\/ul>\n<p>For a concrete list-hygiene workflow, see <a href=\"http:\/\/heartbeat.ai\/resources\/data-quality-verification\/email-verification-for-healthcare-recruiting\/\">email verification for healthcare recruiting<\/a>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Run_one-variable_tests_on_reply_rate_at_the_campaign_level\"><\/span>2) Run one-variable tests on reply rate at the campaign level<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Pick one variable per week per campaign; don&#8217;t stack changes:<\/p>\n<ul>\n<li>Subject line<\/li>\n<li>First two lines (relevance)<\/li>\n<li>CTA (specific scheduling ask vs. vague ask)<\/li>\n<li>Targeting slice (setting, geography, seniority)<\/li>\n<\/ul>\n<p><strong>Measure this by<\/strong> holding the list slice and send window constant, then comparing replies per 100 delivered emails week over week for the same campaign ID.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Improve_positive_replies_by_removing_basic_questions_from_the_thread\"><\/span>3) Improve positive replies by removing basic questions from the thread<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>State setting (hospital-employed vs. private group) and schedule shape<\/li>\n<li>Be explicit about call expectations when known<\/li>\n<li>Offer two concrete call windows<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"4_Enforce_change-log_discipline\"><\/span>4) Enforce change-log discipline<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>List source, and whether it was refreshed or verified<\/li>\n<li>Sending domain and mailbox used<\/li>\n<li>Sequence version (v1, v2, etc.)<\/li>\n<li>Send window (day\/time range)<\/li>\n<li>Suppression update: what changed, and when<\/li>\n<\/ul>\n<p>For a multi-channel workflow that&#8217;s easy to log, see <a href=\"http:\/\/heartbeat.ai\/resources\/physician-recruiting\/physician-recruiting-sequence-email-sms-call\/\">a physician recruiting sequence across email, SMS, and calls<\/a>.<\/p>\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<ul>\n<li>Honor opt-outs immediately and suppress across all tools.<\/li>\n<li>Only contact physicians for legitimate recruiting opportunities; avoid deceptive subject lines.<\/li>\n<li>Minimize data: store what you need to recruit and report, nothing more.<\/li>\n<li>Coordinate with your compliance or legal team on the privacy and communications rules that apply in your jurisdictions.<\/li>\n<\/ul>\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<ul>\n<li><a href=\"https:\/\/postmaster.google.com\/\">Google Postmaster Tools<\/a> \u2014 domain-level deliverability and reputation signals, not per-recipient inbox placement<\/li>\n<li><a href=\"https:\/\/support.google.com\/a\/answer\/81126?hl=en\">Google Workspace deliverability basics<\/a> \u2014 baseline practices and common causes of delivery issues<\/li>\n<\/ul>\n<p>How we approach accuracy and sourcing in Heartbeat resources: <a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/\">Heartbeat trust methodology<\/a>.<\/p>\n<p>Reminder: this page does not provide any guarantee of inbox placement or outcomes.<\/p>\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_reply_rate_in_physician_outreach\"><\/span>What is reply rate in physician outreach?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Reply Rate<\/strong> equals replies divided by delivered emails, expressed per 100 delivered emails.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Should_reply_rate_be_calculated_on_delivered_or_sent\"><\/span>Should reply rate be calculated on delivered or sent?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Delivered. Using sent mixes deliverability failures into your reply metric and leads you to diagnose the wrong problem.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_counts_as_a_positive_reply\"><\/span>What counts as a positive reply?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A <strong>Positive Reply<\/strong> is a response that indicates interest or creates a next step, such as sending details, scheduling a call, or sharing timing. Track it separately from any reply.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Do_auto-replies_or_out-of-office_messages_count_as_replies\"><\/span>Do auto-replies or out-of-office messages count as replies?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. Exclude auto-replies and out-of-office messages from reply rate. If you track them, track them separately so they don&#8217;t inflate performance.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Do_unsubscribes_count_as_replies\"><\/span>Do unsubscribes count as replies?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>No. Track opt-outs and unsubscribes separately as a compliance and deliverability signal. A reply is a message response; an unsubscribe is a suppression event.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_avoid_double-counting_replies_across_email_and_SMS\"><\/span>How do I avoid double-counting replies across email and SMS?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use a single rule: count one reply per person per campaign regardless of channel. Store the first Reply Timestamp in the campaign window so ops can audit edge cases.<\/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>Static lists decay fast. Standard ops practice is access, refresh, verification, and suppression before you scale sends.<\/li>\n<li>Implement the ATS field map and data dictionary above, and run the weekly report for three consecutive weeks without changing definitions.<\/li>\n<li>Then run one-variable tests on targeting and messaging using the same campaign IDs.<\/li>\n<li>If you want to operationalize sourcing and outreach faster, <a href=\"https:\/\/heartbeat.ai\/signup\">start free search &amp; preview data<\/a> in Heartbeat.ai and build campaigns that are measurable from day one.<\/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><br \/>\n<script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"Article\",\"articleSection\":\"Recruiting Ops\",\"author\":{\"@type\":\"Person\",\"name\":\"Ben Argeband\"},\"headline\":\"Reply Rate Tracking for Physician Outreach (ATS Field Map, Strict Campaign Windows, Weekly Report)\",\"inLanguage\":\"en\",\"keywords\":[\"reply rate tracking for physician outreach\",\"reply rate\",\"positive reply\",\"deliverability\",\"bounce rate\",\"Postmaster Tools\"],\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/\",\"@type\":\"WebPage\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"Heartbeat.ai\"}}<\/script><\/p>\n<p><script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Reply Rate = replies \/ delivered emails (per 100 delivered emails).\"},\"name\":\"What is reply rate in physician outreach?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Delivered. If you use sent, you\u2019ll mix deliverability failures into your reply metric and diagnose the wrong problem.\"},\"name\":\"Should reply rate be calculated on delivered or sent?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Positive Reply is a response that indicates interest or creates a next step (send details, schedule a call, share timing). Track it separately from any reply.\"},\"name\":\"What counts as a positive reply?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Exclude auto-replies\/OOO from reply rate. If you track them, track them separately so they don\u2019t inflate performance.\"},\"name\":\"Do auto-replies or out-of-office messages count as replies?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. Track opt-outs\/unsubscribes separately as a compliance and deliverability signal. A reply is a message response; an unsubscribe is a suppression event.\"},\"name\":\"Do unsubscribes count as replies?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use a single rule: count one reply per person per campaign regardless of channel. Store the first Reply Timestamp in the campaign window so ops can audit edge cases.\"},\"name\":\"How do I avoid double-counting replies across email and SMS?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>A practical playbook for tracking reply rates in physician outreach: definitions, ATS field map, deliverability monitoring, and weekly reporting.<\/p>","protected":false},"author":5,"featured_media":54109,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_custom_permalink":"recruiting-ops\/reply-rate-tracking-for-physician-outreach","footnotes":""},"categories":[1],"tags":[],"class_list":["post-54110","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\r\n<title>Reply Rate Tracking for Physician Outreach (ATS Field Map + Weekly Report)<\/title>\r\n<meta name=\"description\" content=\"Operational playbook for reply rate tracking for physician outreach: definitions (reply, positive reply, bounce), ATS field map + data dictionary, strict campaign windows, ownership\/cadence, and weekly reporting.\" \/>\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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Reply Rate Tracking for Physician Outreach (ATS Field Map + Weekly Report)\" \/>\r\n<meta property=\"og:description\" content=\"Operational playbook for reply rate tracking for physician outreach: definitions (reply, positive reply, bounce), ATS field map + data dictionary, strict campaign windows, ownership\/cadence, and weekly reporting.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T18:17:11+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-08-31T13:45:20+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.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=\"12 minutes\" \/>\r\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Reply Rate Tracking for Physician Outreach (ATS Field Map, Strict Campaign Windows, Weekly Report)\",\"datePublished\":\"2026-02-01T18:17:11+00:00\",\"dateModified\":\"2026-08-31T13:45:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/\"},\"wordCount\":2466,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/\",\"url\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/\",\"name\":\"Reply Rate Tracking for Physician Outreach (ATS Field Map + Weekly Report)\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png\",\"datePublished\":\"2026-02-01T18:17:11+00:00\",\"dateModified\":\"2026-08-31T13:45:20+00:00\",\"description\":\"Operational playbook for reply rate tracking for physician outreach: definitions (reply, positive reply, bounce), ATS field map + data dictionary, strict campaign windows, ownership\\\/cadence, and weekly reporting.\",\"breadcrumb\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#primaryimage\",\"url\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png\",\"contentUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/recruiting-ops\\\/reply-rate-tracking-for-physician-outreach\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Reply Rate Tracking for Physician Outreach (ATS Field Map, Strict Campaign Windows, Weekly Report)\"}]},{\"@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\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"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\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?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":"Reply Rate Tracking for Physician Outreach (ATS Field Map + Weekly Report)","description":"Operational playbook for reply rate tracking for physician outreach: definitions (reply, positive reply, bounce), ATS field map + data dictionary, strict campaign windows, ownership\/cadence, and weekly reporting.","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\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/","og_locale":"en_US","og_type":"article","og_title":"Reply Rate Tracking for Physician Outreach (ATS Field Map + Weekly Report)","og_description":"Operational playbook for reply rate tracking for physician outreach: definitions (reply, positive reply, bounce), ATS field map + data dictionary, strict campaign windows, ownership\/cadence, and weekly reporting.","og_url":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T18:17:11+00:00","article_modified_time":"2026-08-31T13:45:20+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png","type":"image\/png"}],"author":"Ben Argeband","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Ben Argeband","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Reply Rate Tracking for Physician Outreach (ATS Field Map, Strict Campaign Windows, Weekly Report)","datePublished":"2026-02-01T18:17:11+00:00","dateModified":"2026-08-31T13:45:20+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/"},"wordCount":2466,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/","url":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/","name":"Reply Rate Tracking for Physician Outreach (ATS Field Map + Weekly Report)","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png","datePublished":"2026-02-01T18:17:11+00:00","dateModified":"2026-08-31T13:45:20+00:00","description":"Operational playbook for reply rate tracking for physician outreach: definitions (reply, positive reply, bounce), ATS field map + data dictionary, strict campaign windows, ownership\/cadence, and weekly reporting.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#primaryimage","url":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png","contentUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/reply-rate-tracking-for-physician-outreach-7ee6fcb8.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/reply-rate-tracking-for-physician-outreach\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/heartbeat.ai\/resources\/"},{"@type":"ListItem","position":2,"name":"Reply Rate Tracking for Physician Outreach (ATS Field Map, Strict Campaign Windows, Weekly Report)"}]},{"@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":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"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":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9cdd6acf262740ced0b6a1c76378e93640df32a98d2f4d29507f31fbce6817e7?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\/54110","targetHints":{"allow":["GET"]}}],"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=54110"}],"version-history":[{"count":2,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54110\/revisions"}],"predecessor-version":[{"id":66173,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54110\/revisions\/66173"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54109"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54110"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54110"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54110"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}