{"id":54039,"date":"2026-01-27T06:34:24","date_gmt":"2026-01-27T12:34:24","guid":{"rendered":"https:\/\/heartbeat.ai\/healthcare\/?p=54039"},"modified":"2026-08-28T05:41:39","modified_gmt":"2026-08-28T10:41:39","slug":"physician-contact-database","status":"publish","type":"post","link":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/","title":{"rendered":"Physician Contact Database: How Recruiters Evaluate, Verify, and Measure It"},"content":{"rendered":"<p class=\"article-last-updated\"><strong>Last updated:<\/strong> August 28, 2026<\/p>\n<p><img decoding=\"async\" loading=\"false\" class=\"aligncenter\" src=\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/01\/physician-contact-database-b96a8d32.png.webp\" alt=\"54043\" \/><\/p>\n<p><strong>Ben Argeband, Founder &amp; CEO of Heartbeat.ai<\/strong> \u2014 a practical look at what belongs in a physician contact database, how to test it, and how to measure whether it&#8217;s actually working for your recruiting team.<\/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\/provider-contact-data\/physician-contact-database\/#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\/provider-contact-data\/physician-contact-database\/#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\/provider-contact-data\/physician-contact-database\/#The_%E2%80%9Cuseful_database%E2%80%9D_test_coverage_%C3%97_connectability_%C3%97_refresh\" >The &#8220;useful database&#8221; test: coverage \u00d7 connectability \u00d7 refresh<\/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\/provider-contact-data\/physician-contact-database\/#Diagnostic_table\" >Diagnostic table<\/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\/provider-contact-data\/physician-contact-database\/#Healthcare-specific_vs_general_B2B_side-by-side_buyer_table\" >Healthcare-specific vs general B2B: side-by-side buyer table<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-7\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#Step_1_build_your_target_cohort_using_stable_identity_first\" >Step 1: build your target cohort using stable identity first<\/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\/provider-contact-data\/physician-contact-database\/#Step_2_treat_phone_and_email_as_volatile_fields\" >Step 2: treat phone and email as volatile fields<\/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\/provider-contact-data\/physician-contact-database\/#Step_3_run_a_pilot_that_mirrors_your_real_recruiting_workflow\" >Step 3: run a pilot that mirrors your real recruiting workflow<\/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\/provider-contact-data\/physician-contact-database\/#Step_4_use_canonical_metric_definitions\" >Step 4: use canonical metric definitions<\/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\/provider-contact-data\/physician-contact-database\/#Step_5_operationalize_suppression_and_opt-out_as_a_system\" >Step 5: operationalize suppression and opt-out as a system<\/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\/provider-contact-data\/physician-contact-database\/#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-13\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-14\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#Template_1_first_email\" >Template 1: first email<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#Template_2_voicemail_15%E2%80%9320_seconds\" >Template 2: voicemail (15\u201320 seconds)<\/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\/provider-contact-data\/physician-contact-database\/#Template_3_SMS_only_where_appropriate\" >Template 3: SMS (only where appropriate)<\/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\/provider-contact-data\/physician-contact-database\/#Template_4_gatekeeper-friendly_opener\" >Template 4: gatekeeper-friendly opener<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-18\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-19\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#Pitfall_1_optimizing_for_record_count_instead_of_outcomes\" >Pitfall 1: optimizing for record count instead of outcomes<\/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\/provider-contact-data\/physician-contact-database\/#Pitfall_2_confusing_%E2%80%9Cdelivered%E2%80%9D_with_%E2%80%9Cinbox%E2%80%9D\" >Pitfall 2: confusing &#8220;delivered&#8221; with &#8220;inbox&#8221;<\/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\/provider-contact-data\/physician-contact-database\/#Pitfall_3_identity_drift_%E2%80%94_wrong_person_wrong_location\" >Pitfall 3: identity drift \u2014 wrong person, wrong location<\/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\/provider-contact-data\/physician-contact-database\/#Pitfall_4_treating_opt-out_as_optional\" >Pitfall 4: treating opt-out as optional<\/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\/provider-contact-data\/physician-contact-database\/#Pitfall_5_accepting_%E2%80%9Caccuracy%E2%80%9D_claims_without_definitions\" >Pitfall 5: accepting &#8220;accuracy&#8221; claims without definitions<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-24\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-25\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#1_What_you_get_vs_what_you_dont\" >1) What you get vs what you don&#8217;t<\/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\/provider-contact-data\/physician-contact-database\/#2_Sequence_channels_to_reduce_attempts_per_conversation\" >2) Sequence channels to reduce attempts per conversation<\/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\/provider-contact-data\/physician-contact-database\/#3_Use_a_benchmark_worksheet_for_weekly_cohort_comparisons\" >3) Use a benchmark worksheet for weekly cohort comparisons<\/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\/provider-contact-data\/physician-contact-database\/#4_Measurement_instructions\" >4) Measurement instructions<\/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\/provider-contact-data\/physician-contact-database\/#5_Pilot_acceptance_criteria\" >5) Pilot acceptance criteria<\/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\/provider-contact-data\/physician-contact-database\/#6_First-party_benchmarks_only_if_timestamped\" >6) First-party benchmarks, only if timestamped<\/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\/provider-contact-data\/physician-contact-database\/#7_Tighten_deliverability_operations\" >7) Tighten deliverability operations<\/a><\/li><\/ul><\/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\/provider-contact-data\/physician-contact-database\/#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-33\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-34\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-35\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#What_should_a_physician_contact_database_include_for_recruiting\" >What should a physician contact database include for recruiting?<\/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\/provider-contact-data\/physician-contact-database\/#How_do_I_compare_two_databases_without_getting_fooled_by_record_count\" >How do I compare two databases without getting fooled by record count?<\/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\/provider-contact-data\/physician-contact-database\/#What_metrics_should_my_team_track_weekly\" >What metrics should my team track weekly?<\/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\/provider-contact-data\/physician-contact-database\/#How_should_opt-out_and_suppression_work_across_a_recruiting_team\" >How should opt-out and suppression work across a recruiting team?<\/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\/provider-contact-data\/physician-contact-database\/#How_do_I_reduce_false_positives_in_outreach\" >How do I reduce false positives in outreach?<\/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\/provider-contact-data\/physician-contact-database\/#How_do_I_start_testing_Heartbeatai\" >How do I start testing Heartbeat.ai?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-41\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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-42\" href=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#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 written for physician recruiters and locums teams building outreach lists who need faster connectability without wasting time on wrong numbers, dead inboxes, or duplicate physician identities.<\/p>\n<p>Static lists have an obvious appeal \u2014 buy once, dial forever. The problem is decay. Physicians change groups, rotate coverage, and switch inboxes constantly, so a list that isn&#8217;t refreshed starts losing value the day you buy it. The more durable approach combines access, refresh, verification, and suppression rather than a one-time export.<\/p>\n<p><strong>Myth to drop:<\/strong> more records rarely means more conversations. A smaller, fresher, verified cohort usually outperforms a giant stale export.<\/p>\n<p><strong>Scope note:<\/strong> this page focuses on evaluating and measuring a physician contact database. If you need channel-specific execution, see the phone workflow or email workflow pages linked under Next steps.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Quick_answer\"><\/span>Quick answer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<dl>\n<dt>Core answer<\/dt>\n<dd>A physician contact database earns its keep when it&#8217;s NPI-anchored, contact fields are verified (line tested for phone, validated for email, suppressed after opt-out or bounce), and performance is tracked by connect rate and deliverability \u2014 not record count.<\/dd>\n<dt>Key insight<\/dt>\n<dd>NPI is stable identity; phone and email are volatile fields. Refresh cadence and suppression discipline usually matter more than how many records you can export.<\/dd>\n<dt>Best for<\/dt>\n<dd>Physician recruiters and locums teams building outreach lists.<\/dd>\n<\/dl>\n<blockquote>\n<p><strong>Compliance &amp; safety<\/strong><\/p>\n<p>This is intended for legitimate recruiting outreach only. 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_%E2%80%9Cuseful_database%E2%80%9D_test_coverage_%C3%97_connectability_%C3%97_refresh\"><\/span>The &#8220;useful database&#8221; test: coverage \u00d7 connectability \u00d7 refresh<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Recruiting teams rarely lose searches because they lacked data. They lose because the data doesn&#8217;t connect, doesn&#8217;t refresh, or doesn&#8217;t map to the right person.<\/p>\n<ul>\n<li><strong>Coverage:<\/strong> can you reliably find the physicians you recruit \u2014 by specialty, geography, setting \u2014 with a stable identity anchor?<\/li>\n<li><strong>Connectability:<\/strong> when you dial or email, do you reach a real physician (or at least a valid inbox) at a rate that supports your workflow?<\/li>\n<li><strong>Refresh:<\/strong> how quickly does the dataset correct itself when physicians change groups, rotate numbers, or switch inboxes?<\/li>\n<\/ul>\n<p><strong>A practical mental model:<\/strong> start with <strong>NPI<\/strong> as identity, apply <strong>license matching<\/strong> to keep state credentials aligned, attach practice context (specialty, location), then layer in volatile contact fields (phone\/email), and close the loop with refresh plus suppression so bad outcomes don&#8217;t repeat.<\/p>\n<p>A National Provider Identifier is a unique 10-digit identification number issued to health care providers in the United States by CMS, mandated as part of the Administrative Simplification portion of HIPAA. Once assigned, an NPI remains the same even if the provider changes name, address, or other information, and it does not carry information like geographic location or specialty. That&#8217;s exactly why it works as an anchor: it&#8217;s stable, while phone and email are not.<\/p>\n<p>Healthcare-specific datasets tend to produce fewer false positives because they&#8217;re built around this kind of provider identity plus practice context. General B2B datasets can look large on paper but often break down when you need the right clinician at the right location.<\/p>\n<p>For the product-level view of what&#8217;s included, see <a href=\"https:\/\/heartbeat.ai\/our-data\">what&#8217;s inside Heartbeat.ai data coverage<\/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>Use this to evaluate any physician contact database, including whatever you&#8217;re using today. It&#8217;s built around recruiting operations: speed-to-submittal, connectability, and workflow fit.<\/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>What you&#8217;re evaluating<\/th>\n<th>What &#8220;good&#8221; looks like<\/th>\n<th>How to test it fast<\/th>\n<th>Why it matters<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Identity anchor<\/td>\n<td>Every record ties to <strong>NPI<\/strong> and supports <strong>license matching<\/strong><\/td>\n<td>Pick 25 known physicians; confirm NPI alignment and license state<\/td>\n<td>NPI prevents wrong-person outreach and duplicate identities<\/td>\n<\/tr>\n<tr>\n<td>Phone quality<\/td>\n<td>Numbers are <strong>line tested<\/strong> and tagged by <strong>recency<\/strong><\/td>\n<td>Run a 100-dial pilot; track connected calls and wrong-party outcomes<\/td>\n<td>Bad numbers waste call blocks and slow submittals<\/td>\n<\/tr>\n<tr>\n<td>Email quality<\/td>\n<td>Emails are validated (format\/domain checks and bounce suppression); opt-outs persist<\/td>\n<td>Send a small pilot; track delivered vs bounced; confirm suppression<\/td>\n<td>Protects domain reputation and keeps outreach scalable<\/td>\n<\/tr>\n<tr>\n<td>Refresh cadence<\/td>\n<td>Refresh cadence is explicit and prioritized over record count<\/td>\n<td>Ask: &#8220;How often do you re-verify phone\/email and update practice moves?&#8221;<\/td>\n<td>Decay is the hidden cost; refresh beats &#8220;big export&#8221; marketing<\/td>\n<\/tr>\n<tr>\n<td>Workflow fit<\/td>\n<td>Exports\/CRM sync; recruiter notes; suppression writeback<\/td>\n<td>Export a 50-record cohort; confirm you can write back outcomes and opt-outs<\/td>\n<td>Prevents rework and keeps suppression consistent across the team<\/td>\n<\/tr>\n<tr>\n<td>Compliance controls<\/td>\n<td>Clear <strong>consent<\/strong> posture, <strong>opt-out<\/strong> workflow, and suppression lists<\/td>\n<td>Request documentation of opt-out + suppression handling<\/td>\n<td>Prevents repeat-contact mistakes and reduces risk<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><strong>Definitions for evaluation:<\/strong> <strong>Line tested<\/strong> means the number has been checked as a working line, not just present in a record. <strong>Recency<\/strong> means you can see when a contact field was last verified or observed active.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Healthcare-specific_vs_general_B2B_side-by-side_buyer_table\"><\/span>Healthcare-specific vs general B2B: side-by-side buyer table<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>Buyer question<\/th>\n<th>Healthcare-specific dataset (what to expect)<\/th>\n<th>General B2B dataset (common failure mode)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>How do you prevent wrong-person matches?<\/td>\n<td>NPI-anchored identity; better de-duplication across locations<\/td>\n<td>Name\/company matching creates false positives and merged identities<\/td>\n<\/tr>\n<tr>\n<td>Can I segment by clinical reality?<\/td>\n<td>Specialty + practice context is usually more consistent<\/td>\n<td>Titles\/roles often misclassify clinicians or mix admin roles<\/td>\n<\/tr>\n<tr>\n<td>How do you handle practice moves?<\/td>\n<td>Updates tied to provider identity and practice signals<\/td>\n<td>Company-based updates can lag or attach to the wrong record<\/td>\n<\/tr>\n<tr>\n<td>What reduces wasted outreach?<\/td>\n<td>Line testing + recency + suppression reduces dead attempts<\/td>\n<td>Large exports with stale fields increase wrong numbers and bounces<\/td>\n<\/tr>\n<tr>\n<td>What should I optimize for?<\/td>\n<td>Refresh cadence and connectability metrics<\/td>\n<td>Record count and &#8220;coverage&#8221; claims that don&#8217;t translate to connects<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p><strong>Buyer scorecard note:<\/strong> require reporting on <strong>connect rate per 100 dials<\/strong> and <strong>deliverability per 100 sends<\/strong> for your pilot cohort. Don&#8217;t accept a generic &#8220;accuracy&#8221; claim without definitions.<\/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_build_your_target_cohort_using_stable_identity_first\"><\/span>Step 1: build your target cohort using stable identity first<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Start with identity, not contact fields. In healthcare, the stable anchor is <strong>NPI<\/strong>. Use it to de-duplicate and keep outreach tied to the correct physician across locations.<\/p>\n<ul>\n<li>Define the cohort: specialty, geography, setting, and must-have constraints.<\/li>\n<li>Attach NPI and run <strong>license matching<\/strong> where state alignment matters.<\/li>\n<li>Only then evaluate phone\/email fields for outreach.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_treat_phone_and_email_as_volatile_fields\"><\/span>Step 2: treat phone and email as volatile fields<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>NPI is stable; phone and email are not. Physicians change groups, rotate coverage, and switch inboxes regularly. Build your workflow assuming decay and lean on verification plus refresh to keep pace.<\/p>\n<ul>\n<li>Prefer phone data that is <strong>line tested<\/strong> and tagged by <strong>recency<\/strong>.<\/li>\n<li>Prefer email data with validation, bounce handling, and suppression.<\/li>\n<li>Ensure opt-outs persist across recruiters and campaigns.<\/li>\n<\/ul>\n<p>Heartbeat.ai includes ranked mobile numbers by answer probability so recruiters can start with the option most likely to connect when time is tight.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_run_a_pilot_that_mirrors_your_real_recruiting_workflow\"><\/span>Step 3: run a pilot that mirrors your real recruiting workflow<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Don&#8217;t pilot on easy segments. Pilot on the cohort you actually struggle to reach.<\/p>\n<ol>\n<li>Pull 100 physicians you would genuinely recruit this month.<\/li>\n<li>Have one recruiter run a consistent call\/email sequence for 3\u20135 business days.<\/li>\n<li>Track outcomes using the metric definitions below so comparisons are apples-to-apples.<\/li>\n<\/ol>\n<p>The trade-off is straightforward: a smaller, fresher cohort with verified fields usually beats a massive stale export because it reduces wasted attempts and speeds up first conversations.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_use_canonical_metric_definitions\"><\/span>Step 4: use canonical metric definitions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use these definitions consistently across vendors, tools, and recruiters:<\/p>\n<ul>\n<li><strong>Connect rate<\/strong> = connected calls \/ total dials (report per 100 dials).<\/li>\n<li><strong>Answer rate<\/strong> = human answers \/ connected calls (report per 100 connected calls).<\/li>\n<li><strong>Deliverability rate<\/strong> = delivered emails \/ sent emails (report per 100 sent emails).<\/li>\n<li><strong>Bounce rate<\/strong> = bounced emails \/ sent emails (report per 100 sent emails).<\/li>\n<li><strong>Reply rate<\/strong> = replies \/ delivered emails (report per 100 delivered emails).<\/li>\n<\/ul>\n<p><strong>Mobile accuracy (definition):<\/strong> the share of first-listed mobile numbers that are valid and reach the intended physician when dialed, measured on a defined sample and time window.<\/p>\n<p><strong>Email accuracy (definition):<\/strong> the share of emails that are valid for the intended physician and result in delivery, not bounce, when sent under normal sending practices, measured on a defined sample and time window.<\/p>\n<p><strong>Deliverability (definition):<\/strong> the share of sent emails that are delivered, not bounced. Delivered doesn&#8217;t guarantee inbox placement.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_operationalize_suppression_and_opt-out_as_a_system\"><\/span>Step 5: operationalize suppression and opt-out as a system<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Opt-out can&#8217;t be a per-campaign setting. It has to be enforced across your entire team and toolchain.<\/p>\n<p><strong>Operational requirement:<\/strong> your CRM or ATS should store opt-out and suppression outcomes at the physician identity level, linked to NPI where possible, so a new recruiter doesn&#8217;t accidentally restart outreach on a previously suppressed record.<\/p>\n<ul>\n<li>Centralize <strong>opt-out<\/strong> and suppression lists.<\/li>\n<li>Write back outcomes \u2014 wrong number, best call window, gatekeeper notes \u2014 to improve future attempts.<\/li>\n<li>Segment by setting so the same cadence isn&#8217;t applied to every physician regardless of context.<\/li>\n<\/ul>\n<h2><span class=\"ez-toc-section\" id=\"Weighted_checklist\"><\/span>Weighted checklist<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Score each item 0\u20135, multiply by weight, and compare totals across options, including &#8220;do nothing.&#8221; This is built for recruiting ops decisions.<\/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>Category<\/th>\n<th>What to look for<\/th>\n<th>Weight<\/th>\n<th>Score (0\u20135)<\/th>\n<th>Weighted score<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Identity integrity<\/td>\n<td>NPI anchored; supports license matching; clear de-duplication rules<\/td>\n<td>5<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Phone connectability<\/td>\n<td>Line tested; recency visible; wrong-party outcomes tracked<\/td>\n<td>5<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Email hygiene<\/td>\n<td>Validation + suppression; bounce handling; sending guidance exists<\/td>\n<td>4<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Refresh cadence<\/td>\n<td>Explicit refresh cadence; updates frequent enough for recruiting cycles<\/td>\n<td>5<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Workflow fit<\/td>\n<td>Exports\/CRM sync; recruiter notes; team-level opt-out enforcement<\/td>\n<td>4<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Compliance posture<\/td>\n<td>Consent posture documented; opt-out honored; audit trail available<\/td>\n<td>4<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>Healthcare specificity<\/td>\n<td>Built around physician identity + practice context, not generic B2B<\/td>\n<td>4<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h2><span class=\"ez-toc-section\" id=\"Outreach_templates\"><\/span>Outreach templates<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Keep it short, respectful, and easy to opt out of. Personalize with specialty, location, and role specifics, and honor opt-out immediately.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_1_first_email\"><\/span>Template 1: first email<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p><strong>Subject:<\/strong> Quick question about [Specialty] coverage in [Region]<\/p>\n<p>Hi Dr. [Last Name] \u2014 I&#8217;m [Your Name]. I recruit physicians for [Facility\/Group Type] in [Region]. Are you open to a brief conversation about a [role type] need?<\/p>\n<p>If you&#8217;re not interested, reply &#8220;opt out&#8221; and I&#8217;ll stop.<\/p>\n<p>\u2014 [Your Name]<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_2_voicemail_15%E2%80%9320_seconds\"><\/span>Template 2: voicemail (15\u201320 seconds)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi Dr. [Last Name], this is [Name]. I&#8217;m recruiting for a [Specialty] role in [Region]. If you&#8217;re open to a quick call, my number is [Callback]. If not, tell me and I&#8217;ll close the loop. Thanks.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_3_SMS_only_where_appropriate\"><\/span>Template 3: SMS (only where appropriate)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Dr. [Last Name] \u2014 [Name] recruiting [Specialty] in [Region]. Open to a 5-min call this week? Reply STOP to opt out.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Template_4_gatekeeper-friendly_opener\"><\/span>Template 4: gatekeeper-friendly opener<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Hi, I&#8217;m trying to reach Dr. [Last Name] regarding a [Specialty] opportunity in [Region]. What&#8217;s the best way or time to connect, or is there a preferred contact route?<\/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_optimizing_for_record_count_instead_of_outcomes\"><\/span>Pitfall 1: optimizing for record count instead of outcomes<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Record count isn&#8217;t an operating metric. If your team can&#8217;t show connect rate per 100 dials and deliverability per 100 sends for the last cohort, you can&#8217;t actually manage performance.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_2_confusing_%E2%80%9Cdelivered%E2%80%9D_with_%E2%80%9Cinbox%E2%80%9D\"><\/span>Pitfall 2: confusing &#8220;delivered&#8221; with &#8220;inbox&#8221;<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Deliverability rate is delivered emails per 100 sends. Inbox placement is separate and depends on sender reputation and sending practices. Monitor bounces and complaints so future campaigns don&#8217;t get harder.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_3_identity_drift_%E2%80%94_wrong_person_wrong_location\"><\/span>Pitfall 3: identity drift \u2014 wrong person, wrong location<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Without an NPI anchor, you&#8217;ll merge the wrong people, duplicate the same physician across locations, or mis-assign specialties. That creates false positives and damages trust quickly.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_4_treating_opt-out_as_optional\"><\/span>Pitfall 4: treating opt-out as optional<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Opt-out has to persist across recruiters and tools. If a physician opts out and gets contacted again, that&#8217;s a preventable compliance and brand problem.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Pitfall_5_accepting_%E2%80%9Caccuracy%E2%80%9D_claims_without_definitions\"><\/span>Pitfall 5: accepting &#8220;accuracy&#8221; claims without definitions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Require definitions \u2014 mobile accuracy, email accuracy, deliverability \u2014 and run your own pilot with your own denominators. If a vendor won&#8217;t define terms, you can&#8217;t compare vendors.<\/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_What_you_get_vs_what_you_dont\"><\/span>1) What you get vs what you don&#8217;t<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>You get:<\/strong> a way to find the right physician identity (NPI), attach contact fields, and run measurable outreach.<\/li>\n<li><strong>You don&#8217;t get:<\/strong> guaranteed reachability, guaranteed inbox placement, or a permanent list that stays accurate without refresh.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"2_Sequence_channels_to_reduce_attempts_per_conversation\"><\/span>2) Sequence channels to reduce attempts per conversation<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Prioritize the contact path most likely to connect quickly \u2014 often mobile first when appropriate, then email, then office line. The goal is fewer attempts per booked conversation.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"3_Use_a_benchmark_worksheet_for_weekly_cohort_comparisons\"><\/span>3) Use a benchmark worksheet for weekly cohort comparisons<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>This worksheet is built for weekly comparisons so you can see whether refresh and verification are actually improving outcomes in your real segment.<\/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>Cohort (specialty + region)<\/th>\n<th>Time window<\/th>\n<th>Total dials<\/th>\n<th>Connected calls<\/th>\n<th>Connect rate (per 100 dials)<\/th>\n<th>Human answers<\/th>\n<th>Answer rate (per 100 connected calls)<\/th>\n<th>Sent emails<\/th>\n<th>Delivered emails<\/th>\n<th>Deliverability (per 100 sends)<\/th>\n<th>Bounced emails<\/th>\n<th>Bounce rate (per 100 sends)<\/th>\n<th>Replies<\/th>\n<th>Reply rate (per 100 delivered emails)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>[e.g., Hospitalist, Midwest]<\/td>\n<td>[Week of ____]<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td>[Same cohort]<\/td>\n<td>[Week of ____]<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<h3><span class=\"ez-toc-section\" id=\"4_Measurement_instructions\"><\/span>4) Measurement instructions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Run a weekly report on the last 100 dials and last 200 emails for the same cohort (same specialty + region), using the canonical denominators:<\/p>\n<ul>\n<li>Connect rate = connected calls \/ total dials (per 100 dials)<\/li>\n<li>Answer rate = human answers \/ connected calls (per 100 connected calls)<\/li>\n<li>Deliverability rate = delivered emails \/ sent emails (per 100 sent emails)<\/li>\n<li>Bounce rate = bounced emails \/ sent emails (per 100 sent emails)<\/li>\n<li>Reply rate = replies \/ delivered emails (per 100 delivered emails)<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"5_Pilot_acceptance_criteria\"><\/span>5) Pilot acceptance criteria<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Keep:<\/strong> wrong-party outcomes trend down week-over-week, suppression is enforced, and recruiters report fewer wasted attempts per conversation.<\/li>\n<li><strong>Investigate:<\/strong> connect rate is flat but answer rate drops \u2014 often a call-timing, gatekeeper, or sequencing issue.<\/li>\n<li><strong>Fix operations:<\/strong> deliverability is unstable or bounce rate spikes \u2014 often a sending-setup or suppression-hygiene issue.<\/li>\n<li><strong>Switch:<\/strong> identity drift persists (wrong person or location) even after NPI anchoring and de-duplication checks.<\/li>\n<\/ul>\n<p>Tie these to recruiter outcomes you already track: conversations booked, CVs received, submittals, and starts. If connect rate improves but starts don&#8217;t, the issue is likely targeting, offer, or follow-up \u2014 not the database itself.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"6_First-party_benchmarks_only_if_timestamped\"><\/span>6) First-party benchmarks, only if timestamped<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If you maintain internal benchmarks, label them clearly with a specific time period and cohort definition, and never treat them as guarantees.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"7_Tighten_deliverability_operations\"><\/span>7) Tighten deliverability operations<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Even valid emails won&#8217;t perform if sending setup is sloppy. Monitor bounces, complaints, and domain reputation, and keep suppression lists clean.<\/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<p>Recruiting outreach should be legitimate, respectful, and auditable:<\/p>\n<ul>\n<li>Use contact data for legitimate recruiting outreach only.<\/li>\n<li>Honor <strong>opt-out<\/strong> requests immediately and permanently via suppression.<\/li>\n<li>Minimize access to the recruiters who need it; log usage where possible.<\/li>\n<li>Be transparent in messaging: who you are, why you&#8217;re reaching out, and how to stop.<\/li>\n<li>Follow applicable local data laws and your organization&#8217;s policies. Heartbeat.ai does not provide legal counsel.<\/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>Provider identity is anchored to NPI because it&#8217;s a unique identification number for covered health care providers, and covered health care providers and all health plans and health care clearinghouses must use NPIs in administrative and financial transactions adopted under HIPAA. Once assigned, an NPI remains the same, even if the provider has a change of name, address, or other information, which is what makes it a durable anchor for de-duplication compared with volatile contact fields.<\/p>\n<ul>\n<li><a href=\"https:\/\/nppes.cms.hhs.gov\/\" target=\"_blank\" rel=\"noopener\">NPPES (NPI registry)<\/a><\/li>\n<li><a href=\"https:\/\/www.cms.gov\/medicare\/regulations-guidance\/administrative-simplification\/national-provider-identifier-npi\" target=\"_blank\" rel=\"noopener\">CMS: National Provider Identifier (NPI) overview<\/a><\/li>\n<\/ul>\n<p>For deliverability fundamentals and monitoring references:<\/p>\n<ul>\n<li><a href=\"https:\/\/support.google.com\/a\/answer\/81126?hl=en\" target=\"_blank\" rel=\"noopener\">Google: bulk sender &amp; deliverability basics<\/a><\/li>\n<li><a href=\"https:\/\/postmaster.google.com\/\" target=\"_blank\" rel=\"noopener\">Google Postmaster Tools<\/a><\/li>\n<\/ul>\n<p>For how Heartbeat.ai evaluates data quality and communicates trust, see our <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/trust-methodology\/\">trust methodology for sourcing and verification<\/a>.<\/p>\n<p>For definitions and practical implications, see <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/data-quality-verification\/what-is-contact-data-accuracy\/\">what contact data accuracy means in recruiting operations<\/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=\"What_should_a_physician_contact_database_include_for_recruiting\"><\/span>What should a physician contact database include for recruiting?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>At minimum: NPI-anchored identity, specialty and location context, phone and email fields with verification and recency signals, and compliance controls like opt-out and suppression.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_compare_two_databases_without_getting_fooled_by_record_count\"><\/span>How do I compare two databases without getting fooled by record count?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Run the same pilot cohort through both and compare connect rate per 100 dials and deliverability per 100 sends using the canonical definitions. Refresh cadence and suppression discipline usually explain the difference.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_metrics_should_my_team_track_weekly\"><\/span>What metrics should my team track weekly?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Connect rate (connected calls \/ total dials), answer rate (human answers \/ connected calls), deliverability rate (delivered \/ sent), bounce rate (bounced \/ sent), and reply rate (replies \/ delivered). Report each per 100 using the denominators.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_should_opt-out_and_suppression_work_across_a_recruiting_team\"><\/span>How should opt-out and suppression work across a recruiting team?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Opt-out should be stored centrally and enforced across recruiters, campaigns, and tools. Suppression should include opt-outs and known bad outcomes, like repeated bounces, so the team doesn&#8217;t re-contact the same physician after a stop request.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_reduce_false_positives_in_outreach\"><\/span>How do I reduce false positives in outreach?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Anchor identity to NPI, de-duplicate across locations, and require practice context fields that match clinical reality. Then validate contact fields and enforce suppression so mistakes don&#8217;t repeat.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"How_do_I_start_testing_Heartbeatai\"><\/span>How do I start testing Heartbeat.ai?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Use a real cohort you&#8217;d recruit this month, run a small pilot, and track connect and deliverability outcomes with the worksheet above.<\/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>Phone-first workflow: <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/provider-contact-data\/physician-phone-number-lookup\/\">physician phone number lookup for recruiters<\/a>.<\/li>\n<li>Email workflow: <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/provider-contact-data\/physician-email-list\/\">how to use physician email responsibly for recruiting<\/a>.<\/li>\n<li>Identity cleanup: <a href=\"http:\/\/heartbeat.ai\/resources\/resources\/provider-contact-data\/npi-license-matching\/\">NPI and license matching<\/a>.<\/li>\n<li>Product coverage: <a href=\"https:\/\/heartbeat.ai\/our-data\">what&#8217;s inside Heartbeat.ai data<\/a>.<\/li>\n<\/ul>\n<p>If you want to validate connectability in your market, <a href=\"https:\/\/heartbeat.ai\/signup\">start free search &amp; preview data<\/a> and run the pilot with the benchmark worksheet.<\/p>\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\",\"about\":[{\"@type\":\"Thing\",\"name\":\"Physician recruiting\"},{\"@type\":\"Thing\",\"name\":\"National Provider Identifier\"},{\"@type\":\"Thing\",\"name\":\"Contact data verification\"}],\"articleSection\":\"Resources\",\"author\":{\"@type\":\"Person\",\"name\":\"Ben Argeband\"},\"dateModified\":\"2026-01-06\",\"datePublished\":\"2026-01-06\",\"headline\":\"Physician Contact Database: How Recruiters Evaluate, Verify, and Measure It\",\"keywords\":[\"physician contact database\"],\"mainEntityOfPage\":{\"@id\":\"https:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/\",\"@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\":\"At minimum: NPI-anchored identity, specialty and location context, phone and email fields with verification\/recency signals, and compliance controls like opt-out and suppression.\"},\"name\":\"What should a physician contact database include for recruiting?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Run the same pilot cohort through both and compare connect rate per 100 dials and deliverability per 100 sends using the canonical definitions. Refresh cadence and suppression discipline usually explain the difference.\"},\"name\":\"How do I compare two databases without getting fooled by record count?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Connect rate (connected calls \/ total dials), answer rate (human answers \/ connected calls), deliverability rate (delivered \/ sent), bounce rate (bounced \/ sent), and reply rate (replies \/ delivered). Report each per 100 using the denominators.\"},\"name\":\"What metrics should my team track weekly?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Opt-out should be stored centrally and enforced across recruiters, campaigns, and tools. Suppression should include opt-outs and known bad outcomes (like repeated bounces) so the team doesn't re-contact the same physician after a stop request.\"},\"name\":\"How should opt-out and suppression work across a recruiting team?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Anchor identity to NPI, de-duplicate across locations, and require practice context fields that match clinical reality. Then validate contact fields and enforce suppression so you don't repeat mistakes.\"},\"name\":\"How do I reduce false positives in outreach?\"},{\"@type\":\"Question\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Use a real cohort you'd recruit this month, run a small pilot, and track connect and deliverability outcomes with the worksheet above.\"},\"name\":\"How do I start testing Heartbeat.ai?\"}]}<\/script><\/p>","protected":false},"excerpt":{"rendered":"<p>A physician contact database works when it&#8217;s NPI-anchored, verified, and measured by connect rate and deliverability\u2014not record count.<\/p>","protected":false},"author":5,"featured_media":54043,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_custom_permalink":"provider-contact-data\/physician-contact-database","footnotes":""},"categories":[1],"tags":[],"class_list":["post-54039","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>Physician Contact Database: Evaluation Checklist + Connect\/Deliverability Metrics<\/title>\r\n<meta name=\"description\" content=\"Recruiter guide to evaluating a physician contact database: NPI identity, license matching, line testing, recency, refresh cadence, opt-out suppression, and how to measure connect rate and deliverability.\" \/>\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\/provider-contact-data\/physician-contact-database\/\" \/>\r\n<meta property=\"og:locale\" content=\"en_US\" \/>\r\n<meta property=\"og:type\" content=\"article\" \/>\r\n<meta property=\"og:title\" content=\"Physician Contact Database: Evaluation Checklist + Connect\/Deliverability Metrics\" \/>\r\n<meta property=\"og:description\" content=\"Recruiter guide to evaluating a physician contact database: NPI identity, license matching, line testing, recency, refresh cadence, opt-out suppression, and how to measure connect rate and deliverability.\" \/>\r\n<meta property=\"og:url\" content=\"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/\" \/>\r\n<meta property=\"og:site_name\" content=\"Heartbeat.ai\" \/>\r\n<meta property=\"article:published_time\" content=\"2026-01-27T12:34:24+00:00\" \/>\r\n<meta property=\"article:modified_time\" content=\"2026-08-28T10:41:39+00:00\" \/>\r\n<meta property=\"og:image\" content=\"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/01\/physician-contact-database-b96a8d32.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\\\/provider-contact-data\\\/physician-contact-database\\\/#article\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/\"},\"author\":{\"name\":\"Ben Argeband\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#\\\/schema\\\/person\\\/7b323ddce9b211907423482e2f9db173\"},\"headline\":\"Physician Contact Database: How Recruiters Evaluate, Verify, and Measure It\",\"datePublished\":\"2026-01-27T12:34:24+00:00\",\"dateModified\":\"2026-08-28T10:41:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/\"},\"wordCount\":2847,\"commentCount\":0,\"publisher\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#organization\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/physician-contact-database-b96a8d32.png\",\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/\",\"url\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/\",\"name\":\"Physician Contact Database: Evaluation Checklist + Connect\\\/Deliverability Metrics\",\"isPartOf\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#primaryimage\"},\"image\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#primaryimage\"},\"thumbnailUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/physician-contact-database-b96a8d32.png\",\"datePublished\":\"2026-01-27T12:34:24+00:00\",\"dateModified\":\"2026-08-28T10:41:39+00:00\",\"description\":\"Recruiter guide to evaluating a physician contact database: NPI identity, license matching, line testing, recency, refresh cadence, opt-out suppression, and how to measure connect rate and deliverability.\",\"breadcrumb\":{\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#primaryimage\",\"url\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/physician-contact-database-b96a8d32.png\",\"contentUrl\":\"http:\\\/\\\/hc.heartbeat.ai\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/physician-contact-database-b96a8d32.png\",\"width\":1024,\"height\":1024},{\"@type\":\"BreadcrumbList\",\"@id\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/provider-contact-data\\\/physician-contact-database\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"http:\\\/\\\/heartbeat.ai\\\/resources\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Physician Contact Database: How Recruiters Evaluate, Verify, and Measure It\"}]},{\"@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":"Physician Contact Database: Evaluation Checklist + Connect\/Deliverability Metrics","description":"Recruiter guide to evaluating a physician contact database: NPI identity, license matching, line testing, recency, refresh cadence, opt-out suppression, and how to measure connect rate and deliverability.","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\/provider-contact-data\/physician-contact-database\/","og_locale":"en_US","og_type":"article","og_title":"Physician Contact Database: Evaluation Checklist + Connect\/Deliverability Metrics","og_description":"Recruiter guide to evaluating a physician contact database: NPI identity, license matching, line testing, recency, refresh cadence, opt-out suppression, and how to measure connect rate and deliverability.","og_url":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/","og_site_name":"Heartbeat.ai","article_published_time":"2026-01-27T12:34:24+00:00","article_modified_time":"2026-08-28T10:41:39+00:00","og_image":[{"width":1024,"height":1024,"url":"https:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/01\/physician-contact-database-b96a8d32.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\/provider-contact-data\/physician-contact-database\/#article","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/"},"author":{"name":"Ben Argeband","@id":"http:\/\/heartbeat.ai\/resources\/#\/schema\/person\/7b323ddce9b211907423482e2f9db173"},"headline":"Physician Contact Database: How Recruiters Evaluate, Verify, and Measure It","datePublished":"2026-01-27T12:34:24+00:00","dateModified":"2026-08-28T10:41:39+00:00","mainEntityOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/"},"wordCount":2847,"commentCount":0,"publisher":{"@id":"http:\/\/heartbeat.ai\/resources\/#organization"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/01\/physician-contact-database-b96a8d32.png","articleSection":["News"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#respond"]}]},{"@type":"WebPage","@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/","url":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/","name":"Physician Contact Database: Evaluation Checklist + Connect\/Deliverability Metrics","isPartOf":{"@id":"http:\/\/heartbeat.ai\/resources\/#website"},"primaryImageOfPage":{"@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#primaryimage"},"image":{"@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#primaryimage"},"thumbnailUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/01\/physician-contact-database-b96a8d32.png","datePublished":"2026-01-27T12:34:24+00:00","dateModified":"2026-08-28T10:41:39+00:00","description":"Recruiter guide to evaluating a physician contact database: NPI identity, license matching, line testing, recency, refresh cadence, opt-out suppression, and how to measure connect rate and deliverability.","breadcrumb":{"@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#primaryimage","url":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/01\/physician-contact-database-b96a8d32.png","contentUrl":"http:\/\/hc.heartbeat.ai\/wp-content\/uploads\/2026\/01\/physician-contact-database-b96a8d32.png","width":1024,"height":1024},{"@type":"BreadcrumbList","@id":"http:\/\/heartbeat.ai\/resources\/provider-contact-data\/physician-contact-database\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"http:\/\/heartbeat.ai\/resources\/"},{"@type":"ListItem","position":2,"name":"Physician Contact Database: How Recruiters Evaluate, Verify, and Measure It"}]},{"@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\/54039","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=54039"}],"version-history":[{"count":7,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54039\/revisions"}],"predecessor-version":[{"id":65474,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/posts\/54039\/revisions\/65474"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media\/54043"}],"wp:attachment":[{"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/media?parent=54039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/categories?post=54039"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/heartbeat.ai\/resources\/wp-json\/wp\/v2\/tags?post=54039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}