{"id":54426,"date":"2026-02-01T13:18:10","date_gmt":"2026-02-01T19:18:10","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/recruiter-capacity-planning-for-physician-roles\/"},"modified":"2026-02-27T13:37:59","modified_gmt":"2026-02-27T19:37:59","slug":"recruiter-capacity-planning-for-physician-roles","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/","title":{"rendered":"Recruiter capacity planning physician recruiting: req load math + calculator"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png.webp\" alt=\"54425\" \/><\/p>\n<h1>Recruiter capacity planning physician recruiting<\/h1>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 Make it spreadsheet math + real recruiting language.<\/p>\n<p>Physician recruiting capacity breaks in two places: <strong>reach<\/strong> (gatekeepers, clinic hours, private practice owners, wrong numbers) and <strong>admin drag<\/strong> (ATS updates, scheduling, duplicate cleanup, contact refresh). If you plan headcount off \u201creqs per recruiter,\u201d you\u2019ll overload the team the moment connectability dips or admin spikes.<\/p>\n<p>This playbook gives you a math-first staffing model that outputs <strong>safe active reqs per recruiter<\/strong> and a staffing estimate using your own inputs: outreach attempts per placement, connect rate, time per attempt, and admin hours. It\u2019s built for speed-to-submittal and workflow fit, not generic HR theory.<\/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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Framework_The_%E2%80%9CStop_Overloading_Recruiters%E2%80%9D_Model_inputs_%E2%86%92_throughput_%E2%86%92_staffing\" title=\"Framework: The \u201cStop Overloading Recruiters\u201d Model: inputs \u2192 throughput \u2192 staffing\">Framework: The \u201cStop Overloading Recruiters\u201d Model: inputs \u2192 throughput \u2192 staffing<\/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\/recruiter-capacity-planning-for-physician-roles\/#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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Step_1_Define_an_outreach_attempt_so_your_math_isnt_fiction\" title=\"Step 1) Define an outreach attempt (so your math isn\u2019t fiction)\">Step 1) Define an outreach attempt (so your math isn\u2019t fiction)<\/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\/recruiter-capacity-planning-for-physician-roles\/#Step_2_Define_capacity_in_weekly_attempt_capacity_not_req_count\" title=\"Step 2) Define capacity in weekly attempt capacity (not req count)\">Step 2) Define capacity in weekly attempt capacity (not req count)<\/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\/recruiter-capacity-planning-for-physician-roles\/#Step_3_Use_your_attempts-per-placement_first-party_and_update_monthly\" title=\"Step 3) Use your attempts-per-placement (first-party) and update monthly\">Step 3) Use your attempts-per-placement (first-party) and update monthly<\/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\/recruiter-capacity-planning-for-physician-roles\/#Step_4_Track_connect_rate_because_attempts_arent_equal\" title=\"Step 4) Track connect rate (because attempts aren\u2019t equal)\">Step 4) Track connect rate (because attempts aren\u2019t equal)<\/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\/recruiter-capacity-planning-for-physician-roles\/#Step_5_Convert_attempt_capacity_into_placement_capacity\" title=\"Step 5) Convert attempt capacity into placement capacity\">Step 5) Convert attempt capacity into placement capacity<\/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\/recruiter-capacity-planning-for-physician-roles\/#Step_6_Convert_placement_capacity_into_a_safe_active_req_cap\" title=\"Step 6) Convert placement capacity into a safe active req cap\">Step 6) Convert placement capacity into a safe active req cap<\/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\/recruiter-capacity-planning-for-physician-roles\/#Step_7_Physician-specific_workflow_call_windows_gatekeeper_routing\" title=\"Step 7) Physician-specific workflow: call windows + gatekeeper routing\">Step 7) Physician-specific workflow: call windows + gatekeeper routing<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-13\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-14\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-15\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Standard_dispositions_use_these_for_clean_measurement\" title=\"Standard dispositions (use these for clean measurement)\">Standard dispositions (use these for clean measurement)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Template_1_Call_opener_direct_physician_line\" title=\"Template 1: Call opener (direct physician line)\">Template 1: Call opener (direct physician line)<\/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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Template_2_Gatekeeper-friendly_ask_clinic_front_desk\" title=\"Template 2: Gatekeeper-friendly ask (clinic front desk)\">Template 2: Gatekeeper-friendly ask (clinic front desk)<\/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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Template_3_Email_first_touch\" title=\"Template 3: Email (first touch)\">Template 3: Email (first touch)<\/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\/recruiter-capacity-planning-for-physician-roles\/#Template_4_Text_after_permission_or_warm_context\" title=\"Template 4: Text (after permission or warm context)\">Template 4: Text (after permission or warm context)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-20\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-21\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Pitfall_1_Planning_off_req_count_instead_of_attempt_capacity\" title=\"Pitfall 1: Planning off req count instead of attempt capacity\">Pitfall 1: Planning off req count instead of attempt capacity<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-22\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Pitfall_2_Treating_all_attempts_as_equal\" title=\"Pitfall 2: Treating all attempts as equal\">Pitfall 2: Treating all attempts as equal<\/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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#Pitfall_3_Ignoring_admin_time_then_blaming_recruiters\" title=\"Pitfall 3: Ignoring admin time (then blaming recruiters)\">Pitfall 3: Ignoring admin time (then blaming recruiters)<\/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\/recruiter-capacity-planning-for-physician-roles\/#Pitfall_4_Using_stale_contact_data_without_suppression\" title=\"Pitfall 4: Using stale contact data without suppression\">Pitfall 4: Using stale contact data without suppression<\/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\/recruiter-capacity-planning-for-physician-roles\/#Pitfall_5_Not_separating_active_reqs_from_owned_reqs\" title=\"Pitfall 5: Not separating active reqs from owned reqs\">Pitfall 5: Not separating active reqs from owned reqs<\/a><\/li><\/ul><\/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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-27\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#1_Capacity_Calculator_worksheet_uniqueness_hook\" title=\"1) Capacity Calculator worksheet (uniqueness hook)\">1) Capacity Calculator worksheet (uniqueness hook)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-28\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#2_Add_a_sensitivity_table_attempts_100_vs_200_connect_5_vs_10_vs_15\" title=\"2) Add a sensitivity table (attempts 100 vs 200; connect 5 vs 10 vs 15%)\">2) Add a sensitivity table (attempts 100 vs 200; connect 5 vs 10 vs 15%)<\/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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#3_Measurement_instructions_weekly_ops_cadence\" title=\"3) Measurement instructions (weekly ops cadence)\">3) Measurement instructions (weekly ops cadence)<\/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\/recruiter-capacity-planning-for-physician-roles\/#4_Increase_capacity_without_hiring_reduce_waste_first\" title=\"4) Increase capacity without hiring (reduce waste first)\">4) Increase capacity without hiring (reduce waste first)<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-31\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-32\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-33\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-34\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#How_do_I_estimate_outreach_attempts_per_placement_if_my_ATS_data_is_messy\" title=\"How do I estimate outreach attempts per placement if my ATS data is messy?\">How do I estimate outreach attempts per placement if my ATS data is messy?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-35\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#What_connect_rate_should_I_plan_around_for_physician_calls\" title=\"What connect rate should I plan around for physician calls?\">What connect rate should I plan around for physician calls?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-36\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#How_do_I_turn_attempt_capacity_into_a_req_cap\" title=\"How do I turn attempt capacity into a req cap?\">How do I turn attempt capacity into a req cap?<\/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\/recruiter-capacity-planning-for-physician-roles\/#Should_I_hire_more_recruiters_or_invest_in_automation_first\" title=\"Should I hire more recruiters or invest in automation first?\">Should I hire more recruiters or invest in automation first?<\/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\/recruiter-capacity-planning-for-physician-roles\/#Where_does_Heartbeatai_fit_in_this_capacity_planning_workflow\" title=\"Where does Heartbeat.ai fit in this capacity planning workflow?\">Where does Heartbeat.ai fit in this capacity planning workflow?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-39\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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-40\" href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#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><strong>Recruiting leaders planning headcount and setting realistic req loads<\/strong> for physician roles (in-house, agency, or hybrid) who need a defensible answer to:<\/p>\n<ul>\n<li>How many active reqs can one recruiter carry without missing follow-ups?<\/li>\n<li>How many recruiters do we need for next month\u2019s req load?<\/li>\n<li>Should we hire, automate, or fix contact data first?<\/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>Calculate weekly attempt capacity, divide by outreach attempts per placement, then cap active reqs by required attempts per req per week to protect speed-to-submittal.<\/dd>\n<dt>Key Statistic<\/dt>\n<dd><strong>Heartbeat observed typicals (Q1 2026):<\/strong> 100\u2013200 outreach attempts per placement; connect rate ~10% (about 10 connected calls per 100 dials).<\/dd>\n<dt>Best For<\/dt>\n<dd>Recruiting leaders planning headcount and setting realistic req loads.<\/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<p><strong>TL;DR lookup:<\/strong><\/p>\n<ul>\n<li><strong>Inputs:<\/strong> admin hours, time per attempt, connect rate, attempts per placement, attempts per active req per week.<\/li>\n<li><strong>Outputs:<\/strong> placements per recruiter per week, and a safe cap for active reqs per recruiter.<\/li>\n<li><strong>Fast diagnosis:<\/strong> if connect rate drops, your \u201creq capacity\u201d drops even if recruiters work the same hours.<\/li>\n<li><strong>Fix order:<\/strong> reachability + suppression \u2192 automation\/ATS enrichment \u2192 then headcount.<\/li>\n<li><strong>CTA:<\/strong> <a href=\"https:\/\/heartbeat.ai\/signup\">start free search &amp; preview data<\/a> to see how much wasted dialing you can remove before hiring.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Framework_The_%E2%80%9CStop_Overloading_Recruiters%E2%80%9D_Model_inputs_%E2%86%92_throughput_%E2%86%92_staffing\"><\/span>Framework: The \u201cStop Overloading Recruiters\u201d Model: inputs \u2192 throughput \u2192 staffing<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Capacity planning in physician recruiting is a throughput model with constraints. Use three layers:<\/p>\n<ul>\n<li><strong>Inputs<\/strong>: time, admin load, reachability, and conversion assumptions.<\/li>\n<li><strong>Throughput<\/strong>: how many <em>quality outreach attempts<\/em> a recruiter can execute per week while keeping the ATS usable.<\/li>\n<li><strong>Staffing<\/strong>: recruiters needed (or req load per recruiter) to hit submittals and placements.<\/li>\n<\/ul>\n<p>Capacity is constrained by reach and admin time. Automations increase capacity. Better contact data increases the share of attempts that turn into real conversations.<\/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_Define_an_outreach_attempt_so_your_math_isnt_fiction\"><\/span>Step 1) Define an outreach attempt (so your math isn\u2019t fiction)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Outreach attempt definition:<\/strong> one discrete outbound touch to a specific physician (or decision-maker) through a single channel (call, email, text), with a logged outcome (connected, left voicemail, bounced, replied, wrong number, etc.).<\/p>\n<p>Rule: if it isn\u2019t logged with an outcome, it doesn\u2019t count for capacity planning.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Define_capacity_in_weekly_attempt_capacity_not_req_count\"><\/span>Step 2) Define capacity in weekly attempt capacity (not req count)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Capacity definition:<\/strong> the number of quality outreach attempts a recruiter can execute per week at an acceptable admin burden, while maintaining pipeline hygiene (notes, stages, next steps).<\/p>\n<p>Start with time budgeting:<\/p>\n<ul>\n<li><strong>Total weekly hours<\/strong> (e.g., 40)<\/li>\n<li><strong>Admin hours<\/strong> (intakes, scheduling, ATS updates, reporting)<\/li>\n<li><strong>Net outreach hours<\/strong> = total weekly hours \u2212 admin hours<\/li>\n<\/ul>\n<p>Convert time to attempts:<\/p>\n<ul>\n<li><strong>Time per attempt (minutes)<\/strong>: dialing + voicemail + logging + immediate follow-up (if your process requires it).<\/li>\n<li><strong>Weekly attempt capacity<\/strong> = (net outreach hours \u00d7 60) \u00f7 time per attempt<\/li>\n<\/ul>\n<p>The trade-off is\u2026 if you force time per attempt down without improving data quality and workflow, you\u2019ll inflate \u201cattempts\u201d while reducing meaningful conversations and submittals.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Use_your_attempts-per-placement_first-party_and_update_monthly\"><\/span>Step 3) Use your attempts-per-placement (first-party) and update monthly<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>You need one conversion anchor: <strong>outreach attempts per placement<\/strong>. Use your own historical data if you have it. If you don\u2019t, start with a planning range and tighten it after 30\u201360 days of clean logging.<\/p>\n<p>Define \u201cplacement\u201d for your team and keep it consistent (for example: accepted offer for perm; start date for locums).<\/p>\n<ul>\n<li><strong>Heartbeat observed typicals (Q1 2026):<\/strong> 100\u2013200 outreach attempts per placement.<\/li>\n<\/ul>\n<p>Keep it segmented by specialty and setting. A hospital-employed role and a private practice owner role can behave differently.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Track_connect_rate_because_attempts_arent_equal\"><\/span>Step 4) Track connect rate (because attempts aren\u2019t equal)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Two recruiters can do the same number of dials and get different outcomes if one is dialing better numbers at better times.<\/p>\n<ul>\n<li><strong>Connect Rate<\/strong> = connected calls \/ total dials (report as connected calls per 100 dials).<\/li>\n<\/ul>\n<p>Use connect rate as your reachability signal for call-heavy workflows. If connect rate drops, your effective capacity drops. If you want to quantify how better contact data changes throughput, pair this with <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/measure-contact-data-roi\/\">how to measure contact data ROI in recruiting ops<\/a>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_Convert_attempt_capacity_into_placement_capacity\"><\/span>Step 5) Convert attempt capacity into placement capacity<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Once you have weekly attempt capacity and attempts per placement:<\/p>\n<ul>\n<li><strong>Weekly placements per recruiter<\/strong> = weekly attempt capacity \u00f7 outreach attempts per placement<\/li>\n<\/ul>\n<p>This is the cleanest way to talk about \u201ccapacity\u201d without arguing about req counts.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_6_Convert_placement_capacity_into_a_safe_active_req_cap\"><\/span>Step 6) Convert placement capacity into a safe active req cap<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Req load should be based on <strong>active reqs<\/strong> (reqs that require weekly outbound activity), not \u201cowned reqs.\u201d<\/p>\n<p>Set a minimum activity standard per active req:<\/p>\n<ul>\n<li><strong>Attempts per active req per week<\/strong>: the minimum outreach attempts you expect to keep a req moving (calls + emails + texts + follow-ups).<\/li>\n<\/ul>\n<p>Qualitative intensity tiers (so you can standardize without arguing about exact counts):<\/p>\n<ul>\n<li><strong>Low intensity:<\/strong> maintenance mode (pipeline exists; you\u2019re keeping warm outreach and follow-ups moving).<\/li>\n<li><strong>Medium intensity:<\/strong> steady build (you need new candidates weekly and consistent follow-up windows).<\/li>\n<li><strong>High intensity:<\/strong> urgent fill (tight follow-up SLAs; more same-week touches; more scheduling coordination).<\/li>\n<\/ul>\n<p>Then cap active reqs by attempt capacity:<\/p>\n<ul>\n<li><strong>Safe active req cap per recruiter<\/strong> = weekly attempt capacity \u00f7 attempts per active req per week<\/li>\n<\/ul>\n<p>This is the number most leaders actually need for staffing and req assignment.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_7_Physician-specific_workflow_call_windows_gatekeeper_routing\"><\/span>Step 7) Physician-specific workflow: call windows + gatekeeper routing<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Physician outreach is not a 9-to-5 desk job. If you don\u2019t plan around call windows, you\u2019ll burn attempts on gatekeepers and voicemail loops.<\/p>\n<ul>\n<li><strong>Call blocks:<\/strong> protect two outbound blocks aligned to clinic gaps (often early morning and late afternoon). Keep them meeting-free.<\/li>\n<li><strong>Gatekeeper routing:<\/strong> log the best callback window and the best path (direct line vs provider office vs email review).<\/li>\n<li><strong>Disposition discipline:<\/strong> every attempt gets an outcome so your attempts-per-placement becomes real.<\/li>\n<\/ul>\n<p>For a deeper call-block design, use: <a href=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/call-block-math-for-physician-recruiting\/\">call block math for physician recruiting<\/a>.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Diagnostic_Table\"><\/span>Diagnostic Table:<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><strong>Use this in weekly ops review<\/strong> to decide whether you have a staffing problem, a reach problem, or an admin\/workflow problem.<\/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>What it usually means<\/th>\n<th>What to measure<\/th>\n<th>Fix that increases capacity<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>High dials, low conversations<\/td>\n<td>Reach problem (wrong numbers, bad timing, gatekeepers)<\/td>\n<td><strong>Connect Rate<\/strong> = connected calls \/ total dials (per 100 dials)<\/td>\n<td>Refresh contact data, suppress wrong numbers, protect call blocks, reduce wasted dials with ATS enrichment<\/td>\n<\/tr>\n<tr>\n<td>Good conversations, slow submittals<\/td>\n<td>Admin drag or scheduling friction<\/td>\n<td>Minutes from \u201cinterested\u201d to \u201csubmitted\u201d (median)<\/td>\n<td>Automation for follow-ups + scheduling; tighter intake notes; coordinator support<\/td>\n<\/tr>\n<tr>\n<td>Lots of outreach, few qualified candidates<\/td>\n<td>Targeting problem<\/td>\n<td>Qualification pass rate after first live conversation<\/td>\n<td>Sharper intake, better search filters, suppression of out-of-scope profiles<\/td>\n<\/tr>\n<tr>\n<td>Recruiters are busy but ATS is messy<\/td>\n<td>Workflow mismatch<\/td>\n<td>Admin hours\/week vs planned; rework rate (duplicate cleanup time)<\/td>\n<td>ATS enrichment, standardized dispositions, fewer required fields<\/td>\n<\/tr>\n<tr>\n<td>Capacity swings week to week<\/td>\n<td>Interruptions and unplanned meetings<\/td>\n<td>Outbound block adherence (% of planned blocks completed)<\/td>\n<td>Protected outbound blocks + triage rules for \u201cfires\u201d<\/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><strong>Goal:<\/strong> decide whether to add headcount, improve reachability, or automate. Score each item 0\u20132 (0 = no, 1 = partial, 2 = yes). Multiply by weight.<\/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>Decision area<\/th>\n<th>Question<\/th>\n<th>Weight<\/th>\n<th>Score (0\u20132)<\/th>\n<th>Weighted score<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Reachability<\/td>\n<td>Do we have reliable direct dials and deliverable emails for our target physicians?<\/td>\n<td>3<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Reachability<\/td>\n<td>Is connect rate stable week-to-week (connected calls \/ total dials per 100 dials)?<\/td>\n<td>3<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Process<\/td>\n<td>Do recruiters have protected outbound blocks at the right call windows?<\/td>\n<td>2<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Admin load<\/td>\n<td>Is ATS enrichment automated (contact + specialty + location + suppression) instead of manual?<\/td>\n<td>3<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Conversion<\/td>\n<td>Do we know our outreach attempts per placement from first-party logs?<\/td>\n<td>3<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Staffing<\/td>\n<td>Are follow-ups slipping because recruiters are carrying too many active reqs?<\/td>\n<td>2<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><strong>Interpretation:<\/strong><\/p>\n<ul>\n<li>If reachability scores low, fix contact data + suppression before hiring.<\/li>\n<li>If admin load scores low, automate and add ATS enrichment before hiring.<\/li>\n<li>If everything scores high and targets still miss, add recruiter capacity or reduce req load.<\/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<p>Short templates that fit physician reality (clinic hours, gatekeepers, short attention windows). Keep them tight and log outcomes.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Standard_dispositions_use_these_for_clean_measurement\"><\/span>Standard dispositions (use these for clean measurement)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>Connected<\/li>\n<li>Left voicemail<\/li>\n<li>Gatekeeper (no transfer)<\/li>\n<li>Wrong number<\/li>\n<li>Do not contact (opt-out)<\/li>\n<li>Email bounced<\/li>\n<li>Replied (email\/text)<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Template_1_Call_opener_direct_physician_line\"><\/span>Template 1: Call opener (direct physician line)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Opener:<\/strong> \u201cDr. [Last], this is [Name]. I\u2019m calling about a [specialty] role in [region]. Do you have 20 seconds for the headline?\u201d<\/li>\n<li><strong>Headline:<\/strong> \u201cIt\u2019s [setting], [schedule\/call], comp range [range]. If I send a 3-bullet summary, what\u2019s the best email?\u201d<\/li>\n<li><strong>Close:<\/strong> \u201cIf it\u2019s not you, who\u2019s the right person in your group to talk to?\u201d<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Template_2_Gatekeeper-friendly_ask_clinic_front_desk\"><\/span>Template 2: Gatekeeper-friendly ask (clinic front desk)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>\u201cI\u2019m trying to reach Dr. [Last] about a physician opportunity. What\u2019s the best time to call when they\u2019re between patients?\u201d<\/li>\n<li>\u201cIs there a direct line for the provider office, or should I email a one-page summary for review?\u201d<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_Email_first_touch\"><\/span>Template 3: Email (first touch)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Subject:<\/strong> \u201c[Specialty] role \u2014 [city] schedule + comp\u201d<\/li>\n<li><strong>Body:<\/strong> \u201cDr. [Last] \u2014 recruiting for a [specialty] opening in [region]. 3 bullets: (1) [setting], (2) [schedule\/call], (3) [comp range]. If you\u2019re open, I\u2019ll send details and a 10-minute time slot. If not, who should I speak with?\u201d<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Template_4_Text_after_permission_or_warm_context\"><\/span>Template 4: Text (after permission or warm context)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li>\u201cDr. [Last], [Name] here. Sent a 3-bullet summary to [email]. Want me to hold a 10-min slot this week or should I close the loop?\u201d<\/li>\n<\/ul>\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_Planning_off_req_count_instead_of_attempt_capacity\"><\/span>Pitfall 1: Planning off req count instead of attempt capacity<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If you start with \u201ceach recruiter can handle X reqs,\u201d you\u2019ll miss the real constraint: how many quality attempts they can execute while keeping follow-up tight.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_2_Treating_all_attempts_as_equal\"><\/span>Pitfall 2: Treating all attempts as equal<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A dial to a verified mobile is not the same as a dial to a hospital main line. If you don\u2019t separate \u201cattempts\u201d from \u201ceffective attempts,\u201d your model will overestimate capacity.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_3_Ignoring_admin_time_then_blaming_recruiters\"><\/span>Pitfall 3: Ignoring admin time (then blaming recruiters)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Credentialing coordination, scheduling, and ATS hygiene are real work. If you don\u2019t budget admin hours, you\u2019ll steal them from outbound time and the pipeline stalls.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_4_Using_stale_contact_data_without_suppression\"><\/span>Pitfall 4: Using stale contact data without suppression<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Buying static lists is risky because of decay. The modern standard is Access + Refresh + Verification + Suppression. If you don\u2019t suppress wrong numbers, bounced emails, and opt-outs, your reachability drops and your capacity plan quietly fails.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_5_Not_separating_active_reqs_from_owned_reqs\"><\/span>Pitfall 5: Not separating active reqs from owned reqs<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Recruiters can \u201cown\u201d 40 reqs, but only 12 might be truly active. Capacity planning should be based on active reqs that require weekly outbound activity.<\/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_Capacity_Calculator_worksheet_uniqueness_hook\"><\/span>1) Capacity Calculator worksheet (uniqueness hook)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Calculator block note:<\/strong> Create a spreadsheet tab called <strong>Capacity<\/strong>. Use the table below as your exact layout so leaders can audit assumptions quickly.<\/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>Cell<\/th>\n<th>Input \/ Output<\/th>\n<th>Definition<\/th>\n<th>Value<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>B2<\/td>\n<td>Total weekly hours<\/td>\n<td>Hours per recruiter per week<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B3<\/td>\n<td>Admin hours<\/td>\n<td>Intakes, scheduling, ATS updates, reporting<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B4<\/td>\n<td>Net outreach hours<\/td>\n<td>=B2-B3<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B5<\/td>\n<td>Time per attempt (minutes)<\/td>\n<td>Dial\/email\/text + logging + immediate follow-up<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B6<\/td>\n<td>Weekly attempt capacity<\/td>\n<td>= (B4*60)\/B5<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B7<\/td>\n<td>Outreach attempts per placement<\/td>\n<td>Your first-party observed typical (segment by specialty)<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B8<\/td>\n<td>Placements per recruiter per week<\/td>\n<td>=B6\/B7<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B9<\/td>\n<td>Attempts per active req per week<\/td>\n<td>Minimum activity standard to keep a req moving<\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>B10<\/td>\n<td>Safe active req cap per recruiter<\/td>\n<td>=B6\/B9<\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><strong>Symbolic example (no numbers):<\/strong> if admin hours (B3) increase, net outreach hours (B4) decrease, so weekly attempt capacity (B6) decreases. That lowers placements per recruiter (B8) and lowers your safe active req cap (B10). If leadership adds reqs anyway, follow-ups slip first.<\/p>\n<p><strong>How to use it:<\/strong> B10 is your \u201creqs per recruiter\u201d cap for active reqs. If leadership wants to add reqs, they must either increase B6 (capacity) or reduce B9 (required weekly activity) without harming outcomes.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"2_Add_a_sensitivity_table_attempts_100_vs_200_connect_5_vs_10_vs_15\"><\/span>2) Add a sensitivity table (attempts 100 vs 200; connect 5 vs 10 vs 15%)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Put this next to the calculator so everyone sees how reachability changes the plan. Use connect rate as your early warning signal.<\/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>Scenario<\/th>\n<th>Outreach attempts per placement<\/th>\n<th>Connect Rate (connected calls \/ total dials per 100 dials)<\/th>\n<th>Operational implication<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Best-case reach<\/td>\n<td>100<\/td>\n<td>15%<\/td>\n<td>More live conversations per dial block; faster qualification; less follow-up waste<\/td>\n<\/tr>\n<tr>\n<td>Planning typical<\/td>\n<td>100<\/td>\n<td>10%<\/td>\n<td>Balanced; requires consistent call blocks and clean dispositions<\/td>\n<\/tr>\n<tr>\n<td>Low reach<\/td>\n<td>100<\/td>\n<td>5%<\/td>\n<td>More time burned on wrong numbers\/gatekeepers; prioritize refresh + suppression<\/td>\n<\/tr>\n<tr>\n<td>Hard search<\/td>\n<td>200<\/td>\n<td>15%<\/td>\n<td>More attempts needed; protect outbound time and tighten targeting<\/td>\n<\/tr>\n<tr>\n<td>Hard search (planning typical)<\/td>\n<td>200<\/td>\n<td>10%<\/td>\n<td>Expect slower fills unless you add capacity or reduce active req cap<\/td>\n<\/tr>\n<tr>\n<td>Hard search + low reach<\/td>\n<td>200<\/td>\n<td>5%<\/td>\n<td>Plan breaks; fix reachability before adding reqs or headcount<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><span class=\"ez-toc-section\" id=\"3_Measurement_instructions_weekly_ops_cadence\"><\/span>3) Measurement instructions (weekly ops cadence)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Measure this by\u2026 running a weekly funnel review per recruiter and per specialty line: attempts \u2192 connects \u2192 qualified \u2192 submitted \u2192 placed.<\/p>\n<ul>\n<li><strong>Connect Rate<\/strong> = connected calls \/ total dials (report per 100 dials).<\/li>\n<li><strong>Outreach attempts per placement<\/strong> = total logged outreach attempts \/ placements (report per placement, segmented by specialty).<\/li>\n<li><strong>Capacity utilization<\/strong> = logged outreach attempts \/ weekly attempt capacity (report per recruiter per week).<\/li>\n<\/ul>\n<p>Operating rule: if connect rate drops for two consecutive weeks, treat it as a reachability\/workflow issue (refresh, suppression, call windows) before treating it as a recruiter performance issue.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"4_Increase_capacity_without_hiring_reduce_waste_first\"><\/span>4) Increase capacity without hiring (reduce waste first)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>ATS enrichment:<\/strong> auto-fill contact fields, specialty, location, and suppress duplicates so recruiters aren\u2019t doing data entry mid-flow.<\/li>\n<li><strong>Automation:<\/strong> templated follow-ups, sequences, and standardized dispositions.<\/li>\n<li><strong>Reachability:<\/strong> fewer wrong numbers and bounces means fewer wasted attempts and better connect rate.<\/li>\n<\/ul>\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>Physician outreach is high-trust and high-scrutiny. Keep your process clean:<\/p>\n<ul>\n<li>Only contact for legitimate recruiting purposes and document your process where required.<\/li>\n<li>Honor opt-out requests immediately and suppress future outreach.<\/li>\n<li>Don\u2019t misrepresent the role, compensation, or urgency.<\/li>\n<li>Keep sensitive information out of free-text notes when it\u2019s not required for recruiting decisions.<\/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<p>We build these playbooks from operational recruiting workflows and what we see in real outreach systems. For how Heartbeat.ai evaluates data quality, refresh, and suppression, read our <a href=\"http:\/\/heartbeat.ai\/resources\/trust-methodology\/\">trust methodology<\/a>.<\/p>\n<p>Reference (context only; not a benchmark): <a href=\"https:\/\/www.bls.gov\/ooh\/management\/human-resources-managers.htm\">U.S. Bureau of Labor Statistics: Human Resources Managers<\/a>.<\/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=\"How_do_I_estimate_outreach_attempts_per_placement_if_my_ATS_data_is_messy\"><\/span>How do I estimate outreach attempts per placement if my ATS data is messy?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Run a 2-week logging sprint: require every call\/email\/text to be logged with an outcome. Then compute total attempts divided by placements, segmented by specialty. Replace planning assumptions with your observed typical.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_connect_rate_should_I_plan_around_for_physician_calls\"><\/span>What connect rate should I plan around for physician calls?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Plan around your own dial logs. <strong>Connect Rate<\/strong> = connected calls \/ total dials (per 100 dials). Use the median week, not the best week.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_turn_attempt_capacity_into_a_req_cap\"><\/span>How do I turn attempt capacity into a req cap?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Set a minimum attempts-per-active-req-per-week standard (B9 in the calculator). Then cap active reqs using: weekly attempt capacity \u00f7 attempts per active req per week.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Should_I_hire_more_recruiters_or_invest_in_automation_first\"><\/span>Should I hire more recruiters or invest in automation first?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If admin hours are eating outbound blocks, automation and ATS enrichment usually increase capacity faster than hiring. If reachability is poor (low connect rate, wrong numbers), fix contact data and suppression first or you\u2019ll scale wasted attempts.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Where_does_Heartbeatai_fit_in_this_capacity_planning_workflow\"><\/span>Where does Heartbeat.ai fit in this capacity planning workflow?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Heartbeat.ai supports reachability and admin reduction: contact discovery, suppression, and ATS enrichment so recruiters spend more time on real conversations and less on rework. If you need fast contact discovery for a target list, see <a href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/bulk-physician-lookup\/\">bulk physician lookup for recruiting outreach<\/a>.<\/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>Build the Capacity worksheet (cells B2\u2013B10) and fill it with your current assumptions.<\/li>\n<li>Run the sensitivity table and decide what breaks first: reachability, admin time, or attempts per placement.<\/li>\n<li>Protect outbound blocks and standardize dispositions so your data stays clean.<\/li>\n<li><a href=\"https:\/\/heartbeat.ai\/signup\">start free search &amp; preview data<\/a> and pressure-test how much wasted dialing you can remove before adding headcount.<\/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\",\"articleSection\":\"Recruiting Ops\",\"author\":{\"@type\":\"Person\",\"jobTitle\":\"Founder & CEO of Heartbeat.ai\",\"name\":\"Ben Argeband\"},\"headline\":\"Recruiter capacity planning physician recruiting: req load math + calculator\",\"inLanguage\":\"en\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\",\"@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\":\"Run a 2-week logging sprint: require every call\/email\/text to be logged with an outcome. Then compute total attempts divided by placements, segmented by specialty. Replace planning assumptions with your observed typical.\"},\"name\":\"How do I estimate outreach attempts per placement if my ATS data is messy?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Plan around your own dial logs. Connect Rate = connected calls \/ total dials (per 100 dials). Use the median week, not the best week.\"},\"name\":\"What connect rate should I plan around for physician calls?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Set a minimum attempts-per-active-req-per-week standard (B9 in the calculator). Then cap active reqs using: weekly attempt capacity \u00f7 attempts per active req per week.\"},\"name\":\"How do I turn attempt capacity into a req cap?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"If admin hours are eating outbound blocks, automation and ATS enrichment usually increase capacity faster than hiring. If reachability is poor (low connect rate, wrong numbers), fix contact data and suppression first or you\u2019ll scale wasted attempts.\"},\"name\":\"Should I hire more recruiters or invest in automation first?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Heartbeat.ai supports reachability and admin reduction: contact discovery, suppression, and ATS enrichment so recruiters spend more time on real conversations and less on rework. If you need fast contact discovery for a target list, see bulk physician lookup for recruiting outreach.\"},\"name\":\"Where does Heartbeat.ai fit in this capacity planning workflow?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>A math-first playbook for recruiter capacity planning in physician recruiting. Use a spreadsheet calculator to set safe active req caps per recruiter based on attempt capacity, connect rate, and attempts per placement.<\/p>","protected":false},"author":5,"featured_media":54425,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_yoast_wpseo_focuskw":"recruiter capacity planning physician recruiting","_yoast_wpseo_title":"Recruiter capacity planning physician recruiting (req load calculator)","_yoast_wpseo_metadesc":"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.","_custom_permalink":"recruiting-ops\/recruiter-capacity-planning-for-physician-roles","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>Recruiter capacity planning physician recruiting (req load calculator)<\/title>\r\n<meta name=\"description\" content=\"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.\" \/>\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\/recruiter-capacity-planning-for-physician-roles\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Recruiter capacity planning physician recruiting (req load calculator)\" \/>\r\n<meta property=\"og:description\" content=\"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-02-01T19:18:10+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-02-27T19:37:59+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#article\",\"isPartOf\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Recruiter capacity planning physician recruiting: req load math + calculator\",\"datePublished\":\"2026-02-01T19:18:10+00:00\",\"dateModified\":\"2026-02-27T19:37:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\"},\"wordCount\":2682,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#organization\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\",\"url\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\",\"name\":\"Recruiter capacity planning physician recruiting (req load calculator)\",\"isPartOf\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage\"},\"image\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png\",\"datePublished\":\"2026-02-01T19:18:10+00:00\",\"dateModified\":\"2026-02-27T19:37:59+00:00\",\"description\":\"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.\",\"breadcrumb\":{\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage\",\"url\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png\",\"contentUrl\":\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/heartbeat.ai\/healthcare\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Recruiter capacity planning physician recruiting: req load math + calculator\"}]},{\"@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":"Recruiter capacity planning physician recruiting (req load calculator)","description":"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.","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\/recruiter-capacity-planning-for-physician-roles\/","og_locale":"en_US","og_type":"article","og_title":"Recruiter capacity planning physician recruiting (req load calculator)","og_description":"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.","og_url":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-02-01T19:18:10+00:00","article_modified_time":"2026-02-27T19:37:59+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.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\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Recruiter capacity planning physician recruiting: req load math + calculator","datePublished":"2026-02-01T19:18:10+00:00","dateModified":"2026-02-27T19:37:59+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/"},"wordCount":2682,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/","url":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/","name":"Recruiter capacity planning physician recruiting (req load calculator)","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage"},"thumbnailUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png","datePublished":"2026-02-01T19:18:10+00:00","dateModified":"2026-02-27T19:37:59+00:00","description":"Set realistic req loads in physician recruiting with a spreadsheet capacity calculator: attempt capacity, connect rate, attempts per placement, and a safe active req cap per recruiter.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#primaryimage","url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png","contentUrl":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/02\/recruiter-capacity-planning-for-physician-roles-4adb278e.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/recruiting-ops\/recruiter-capacity-planning-for-physician-roles\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/heartbeat.ai\/healthcare\/"},{"@type":"ListItem","position":2,"name":"Recruiter capacity planning physician recruiting: req load math + calculator"}]},{"@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\/54426"}],"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=54426"}],"version-history":[{"count":1,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54426\/revisions"}],"predecessor-version":[{"id":54566,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54426\/revisions\/54566"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54425"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54426"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54426"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54426"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}