<\/span><\/h2>\nThis is for recruiters and recruiting ops leaders who need clear boundaries for outreach that protect deliverability, brand, and candidate relationships while keeping workflow speed. If you need something you can hand to leadership, compliance, or procurement, this is written to be operational and auditable.<\/p>\n
One non-negotiable: you own compliance<\/strong>. Tools can help you execute, but they can\u2019t own your policies, training, or decisions.<\/p>\n<\/span>Quick Answer<\/span><\/h2>\n\n- Core Answer<\/dt>\n
- Use contact data only for relevant recruiting outreach, with clear identity context, limited retention, an easy opt-out<\/strong>, and strict opt-out enforcement via a suppression list<\/strong>.<\/dd>\n
- Key Insight<\/dt>\n
- Ethical outreach is operational: provenance, relevance, frequency caps, and opt-out enforcement matter more than the channel you use.<\/dd>\n
- Best For<\/dt>\n
- Recruiters + ops wanting clear boundaries<\/dd>\n<\/dl>\n
\nCompliance & Safety<\/strong><\/p>\nThis 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
<\/span>Acceptable use in 6 rules (copy\/paste)<\/span><\/h3>\n\n- Be relevant:<\/strong> Only contact people who plausibly match the role (specialty\/setting\/location\/seniority).<\/li>\n
- Be transparent:<\/strong> Say who you are, why you\u2019re reaching out, and what the next step is.<\/li>\n
- Be restrained:<\/strong> Use frequency caps and stop rules; don\u2019t pile on across channels.<\/li>\n
- Make it easy to stop:<\/strong> Every message includes an easy opt-out<\/strong>.<\/li>\n
- Honor opt-outs everywhere:<\/strong> Centralize and enforce via a suppression list<\/strong> across all tools and channels.<\/li>\n
- No patient data:<\/strong> Recruiting outreach never uses or implies access to patient information.<\/li>\n<\/ul>\n
<\/span>Framework: The \u201cDon\u2019t be a creep\u201d standard (practical examples)<\/span><\/h2>\nI\u2019ve watched teams lose weeks of productivity because they got flagged, blocked, or publicly called out. The \u201cDon\u2019t be a creep\u201d standard is a fast filter before any outreach goes out the door:<\/p>\n
\n- Respect:<\/strong> Treat the person like a professional, not a lead. No harassment, no pressure, no guilt trips.<\/li>\n
- Relevance:<\/strong> Your message should make sense for their specialty, licensure, geography, and career stage.<\/li>\n
- Transparency:<\/strong> Say who you are and why you\u2019re reaching out.<\/li>\n
- Control:<\/strong> Give a clear easy opt-out<\/strong> and honor it immediately across channels.<\/li>\n
- Restraint:<\/strong> Frequency caps and quiet hours. If you wouldn\u2019t want it done to you during personal time, don\u2019t do it to them.<\/li>\n
- Separation:<\/strong> Recruiting outreach is not patient outreach. No patient data, no clinical context, no insinuations.<\/li>\n<\/ul>\n
<\/span>What acceptable use is not<\/span><\/h3>\n\n- Not<\/strong> permission to spam: volume doesn\u2019t replace relevance.<\/li>\n
- Not<\/strong> a reason to ignore gatekeepers or keep pushing after a \u201cno.\u201d<\/li>\n
- Not<\/strong> patient outreach: don\u2019t reference care events, cases, or anything that implies clinical surveillance.<\/li>\n<\/ul>\n
Examples you can use in training:<\/p>\n
\n- Acceptable:<\/strong> \u201cDr. Patel \u2014 I recruit hospitalists in the Midwest. Are you open to hearing about a 7-on\/7-off role in Dayton? If not, reply \u2018no\u2019 and I\u2019ll stop.\u201d<\/li>\n
- Not acceptable:<\/strong> \u201cI saw you treated a patient at X hospital\u2026\u201d<\/li>\n
- Acceptable:<\/strong> One follow-up after no response, then stop or switch to a lower-friction channel with a single touch.<\/li>\n
- Not acceptable:<\/strong> Calling, texting, emailing, and messaging the same day with escalating language.<\/li>\n<\/ul>\n
<\/span>Do \/ Don\u2019t (fast reference)<\/span><\/h2>\n\n- Do<\/strong> lead with relevance: role + location + why them. Don\u2019t<\/strong> send generic blasts that force the candidate to guess why you contacted them.<\/li>\n
- Do<\/strong> identify yourself and your organization. Don\u2019t<\/strong> use deceptive subject lines or fake familiarity.<\/li>\n
- Do<\/strong> include an easy opt-out<\/strong> in every channel you use. Don\u2019t<\/strong> bury opt-out language or make people jump through hoops.<\/li>\n
- Do<\/strong> treat any \u201cstop\/remove\/unsubscribe\u201d as an opt-out and enforce it via a suppression list<\/strong>. Don\u2019t<\/strong> rely on individual recruiters to remember.<\/li>\n
- Do<\/strong> set frequency caps and stop rules per role. Don\u2019t<\/strong> multi-channel pile-on within 24\u201348 hours.<\/li>\n
- Do<\/strong> keep content strictly recruiting-related. Don\u2019t<\/strong> reference patient care, cases, or anything that implies you\u2019re tracking clinical activity.<\/li>\n<\/ul>\n
<\/span>Step-by-step method<\/span><\/h2>\n<\/span>Step 1: Write a one-page acceptable-use SOP your team will actually follow<\/span><\/h3>\nKeep it short and enforceable. Your SOP should answer:<\/p>\n
\n- Purpose:<\/strong> \u201cWe use contact data to communicate about employment opportunities and career conversations.\u201d<\/li>\n
- In-scope audience:<\/strong> Who you recruit and what \u201crelevant\u201d means for your org.<\/li>\n
- Channels allowed:<\/strong> Email, phone, SMS, voicemail, professional social (if used), and who can use each.<\/li>\n
- Frequency caps:<\/strong> Max attempts per person per role and quiet hours.<\/li>\n
- Stop rules:<\/strong> When to stop after no response, and when to stop immediately (any opt-out, any negative response).<\/li>\n
- Opt-out enforcement:<\/strong> How opt-outs are captured and applied via a suppression list<\/strong>.<\/li>\n<\/ul>\n
<\/span>Stop rules examples (use in training)<\/span><\/h3>\n\n- Immediate stop:<\/strong> Any opt-out language (\u201cstop,\u201d \u201cremove,\u201d \u201cunsubscribe,\u201d \u201cdon\u2019t contact\u201d).<\/li>\n
- Immediate stop:<\/strong> Any explicit negative response (\u201cnot interested,\u201d \u201cdo not call\/text\/email\u201d).<\/li>\n
- Stop and correct:<\/strong> Wrong person\/wrong specialty\/wrong location (fix targeting; don\u2019t keep trying).<\/li>\n
- Stop and route:<\/strong> Gatekeeper requests a different channel or contact point (follow that instruction once, then stop if declined).<\/li>\n
- Stop after cap:<\/strong> No response after your defined attempt cap for that role.<\/li>\n<\/ul>\n
<\/span>Step 2: Separate identity sources from contact channels (provenance)<\/span><\/h3>\nProcurement and compliance teams don\u2019t just want \u201cwhere did you get the data?\u201d They want structure: what establishes identity, what enables contact, and what transformations you apply.<\/p>\n
Procurement-friendly provenance one-pager (outline):<\/strong><\/p>\n\n- Identity sources:<\/strong> What you use to establish professional identity (name, specialty, license\/NPI context).<\/li>\n
- Contact channels:<\/strong> Email\/phone\/SMS endpoints used for outreach (acknowledge these decay).<\/li>\n
- Transformations you apply:<\/strong> verification, refresh, deduping, and suppression enforcement (describe at a high level).<\/li>\n
- Refresh reality:<\/strong> How often you re-check contactability and remove bad endpoints.<\/li>\n
- Suppression governance:<\/strong> Where the suppression list<\/strong> lives, who owns it, and how it propagates to tools.<\/li>\n
- Audit artifacts:<\/strong> What you can show (opt-out logs, campaign settings, template versions).<\/li>\n<\/ul>\n
This is the clean way to answer due diligence questions without exposing sensitive sourcing details.<\/p>\n
<\/span>What to say if asked \u201cWhere did you get my info?\u201d<\/span><\/h3>\nKeep it simple and factual. Don\u2019t argue. Don\u2019t overshare. Use your provenance structure:<\/p>\n
\n- Identity context:<\/strong> \u201cWe recruit in [specialty\/region] and use professional registries to confirm identity and credentials.\u201d<\/li>\n
- Contact channel:<\/strong> \u201cWe use business contact channels to reach out about roles.\u201d<\/li>\n
- Control:<\/strong> \u201cIf you\u2019d like, I can remove you from outreach. Just reply \u2018stop\u2019 and I\u2019ll add you to our suppression list.\u201d<\/li>\n<\/ul>\n
<\/span>Step 3: Build opt-out and suppression into the workflow (not as an afterthought)<\/span><\/h3>\nOpt-out is a system, not a promise. Your operating rules should include:<\/p>\n
\n- Every outbound email includes an easy opt-out<\/strong> instruction.<\/li>\n
- Every SMS includes a clear stop instruction (and you honor it).<\/li>\n
- Any opt-out request updates your
![\"54142\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/data-ethics-acceptable-use-5d49dc32.png.webp\")
<\/p>\n