<?xml version="1.0" encoding="utf-8"?>
<oembed>
  <version>1</version>
  <type>rich</type>
  <provider_name>Libsyn</provider_name>
  <provider_url>https://www.libsyn.com</provider_url>
  <height>90</height>
  <width>600</width>
  <title>CBP 305: The Post-Discharge Follow System that Reactivates Patients and Earns Google Reviews</title>
  <description>If you don’t have at least a 6-12 month follow-up system for patients after discharge, you’re leaving a lot of money on the table. Most practices either don’t follow up at all, or they send one message a few weeks later that says something like, “Just checking in to see how you’re doing.” The intention is good, but the message is too easy to ignore. It doesn’t remind the patient what they accomplished, it doesn’t ask a specific question that commands a response, and it doesn’t create a clear path back onto the schedule if they need help again. That’s what this episode is about. I’m walking through the exact post-discharge follow-up system we use in my own clinic to stay in front of patients for more than a year after they finish care. It’s simple, repeatable, handled by staff, and it helps us reactivate patients almost every week. What You’ll Learn in This Episode   The 13-month follow-up structure we use after discharge   How to write follow-up texts that actually get responses   What to say when patients reply that they are still doing great   What to say when patients have lost progress and need to come back in   How to avoid follow-up automation mistakes when patients return to the schedule   USEFUL INFORMATION:  Check out our course: CASH-BASED PRACTICE MASTERMIND </description>
  <author_name>The Cash-Based Practice Podcast</author_name>
  <author_url>https://drjarodcarter.com</author_url>
  <html>&lt;iframe title="Libsyn Player" style="border: none" src="//html5-player.libsyn.com/embed/episode/id/41012785/height/90/theme/custom/thumbnail/yes/direction/forward/render-playlist/no/custom-color/88AA3C/" height="90" width="600" scrolling="no"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen&gt;&lt;/iframe&gt;</html>
  <thumbnail_url>https://assets.libsyn.com/secure/content/201179300</thumbnail_url>
</oembed>
