\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>Framework: \u201cPermission + brevity\u201d SMS pattern<\/span><\/h2>\nEvery effective physician recruiting text follows the same structure. Keep it consistent so your team can move quickly without sounding careless.<\/p>\n
\n- Identity<\/strong>: who you are (name + org) and that you recruit physicians.<\/li>\n
- Purpose<\/strong>: why you\u2019re texting (role type + location or schedule hint, not a full pitch).<\/li>\n
- Permission-based question<\/strong>: ask if it\u2019s okay to share details or schedule a quick call.<\/li>\n
- Easy out<\/strong>: include STOP to opt out<\/strong>.<\/li>\n
- Logging<\/strong>: record the outcome and update suppression<\/strong> immediately on any opt-out<\/strong>.<\/li>\n<\/ul>\n
Operational definition:<\/strong> \u201cconsent-aware\u201d means permission-first wording, immediate opt-out suppression, and no repeated nudges after silence.<\/p>\nThe trade-off is\u2026 the shorter you keep the message, the more you rely on a clean follow-up workflow (call\/email) to carry the details.<\/p>\n
<\/span>Step-by-step method<\/span><\/h2>\n<\/span>1) Decide if SMS is the right channel (when to use vs not)<\/span><\/h3>\nUse SMS when you\u2019re asking permission, confirming interest, or scheduling. Avoid SMS for long pitches, credentialing\/licensure questions, or compensation negotiation.<\/p>\n
If you can\u2019t justify legitimate recruiting relevance under your org policy, don\u2019t text\u2014start with email.<\/p>\n
\n- Use SMS<\/strong>: permission check, scheduling, \u201cis this still your number?\u201d, short follow-up after voicemail\/email.<\/li>\n
- Use call<\/strong>: time-sensitive coverage, objections, relationship building, nuanced schedule\/comp discussion.<\/li>\n
- Use email<\/strong>: full job details, links, documents, multi-step process, formal summaries.<\/li>\n<\/ul>\n
<\/span>2) Do a quick pre-send hygiene check<\/span><\/h3>\n\n- Confirm you\u2019re texting the right person (name\/specialty\/location match).<\/li>\n
- Check internal suppression before sending.<\/li>\n
- Send during reasonable local hours.<\/li>\n
- Keep the first text short so it reads cleanly on any device.<\/li>\n<\/ul>\n
<\/span>3) Send a first text that earns permission<\/span><\/h3>\nYour first message should be a permission request, not a pitch. Identify yourself, state the reason, and ask a simple yes\/no question.<\/p>\n
<\/span>4) Route replies into a tight follow-up workflow<\/span><\/h3>\n\n- Yes<\/strong> \u2192 ask preferred channel\/time; offer two time windows; confirm role type and location.<\/li>\n
- Maybe \/ later<\/strong> \u2192 ask when to follow up; set a reminder; don\u2019t keep nudging after silence.<\/li>\n
- No<\/strong> \u2192 thank them; close out; do not argue.<\/li>\n
- STOP \/ opt-out<\/strong> \u2192 acknowledge once, suppress immediately, and log.<\/li>\n<\/ul>\n
If there\u2019s no reply, stop texting and switch channels (email\/call) rather than sending repeated follow-ups.<\/p>\n
<\/span>5) Stop rules and logging workflow (do this the same day)<\/span><\/h3>\nOpt-outs are where teams get into trouble: one recruiter logs it, another doesn\u2019t see it, and the physician gets texted again. Treat stop handling as an ops workflow, not a personal habit.<\/p>\n
\n- Receive<\/strong> the opt-out (STOP or clear intent).<\/li>\n
- Send one confirmation<\/strong> (one message only).<\/li>\n
- Update suppression<\/strong> so it applies across your team and tools.<\/li>\n
- Log<\/strong> the required fields in your ATS\/CRM (see consolidated table below).<\/li>\n<\/ol>\n
Measure this by\u2026 running a weekly audit of recent opt-outs to confirm suppression was applied and no further texts were sent.<\/p>\n
<\/span>Diagnostic Table:<\/span><\/h2>\nUse this to pick the right message type and avoid texting when it\u2019s likely to backfire.<\/p>\n
![\"54153\"](\"http:\/\/hc.heartbeat.ai\/wp-content\/webp-express\/webp-images\/uploads\/2026\/02\/physician-recruiter-sms-templates-f37446f2.png.webp\")
<\/p>\n