Close this search box.
Resources > Blog

Navigating New TCPA Regulations: A Guide for Healthcare Communications

In the ever-evolving landscape of healthcare communications, staying compliant with regulatory changes is paramount. One such significant transformation occurred on July 20, 2023, when new requirements under the Telephone Consumer Protection Act (TCPA) came into effect. These changes directly impact how healthcare organizations engage with their patients and members, including significant implications for HIPAA-related calls. Understanding the intricacies of these regulations is essential to avoid hefty fines and legal complications.

At mPulse, we recognize the challenges and complexities that healthcare organizations face, which were previously mostly exempted. With our expertise and innovative solutions, we are well-positioned to help healthcare organizations navigate these changes seamlessly and ensure they remain compliant, safeguarding both their reputation and financial well-being. 

In this blog post, we’ll explore the key aspects of the TCPA changes that took effect on July 20, 2023, and shed light on how mPulse can assist healthcare organizations meet these regulatory demands through our digital health solutions, especially as they relate to HIPAA-related communications.

Three notable impacts of the Telephone Consumer Protection Act on healthcare pre-recorded voice calls

  1. The TCPA now sets a call limitation on healthcare-related calls without prior express consent, allowing for one artificial or pre-recorded call per day and up to three artificial or pre-recorded calls per week. This is a significant change, as there was previously no limit on calls without prior consent. However, even with these TCPA changes in effect, if recipients have willingly provided their prior express consent—often obtained through providing a telephone number or completing a registration process—there is still no limit to the number of calls that can be made.

mPulse solutions are thoughtfully designed to make an impact with the fewest touch points possible, well within the call limits, to comply with the TCPA changes when there is no prior express consent. With consent, we can also offer configurations involving multiple solutions that may need more touchpoints, enabling healthcare organizations to achieve their communication goals. 

2. The callers* must provide the following to help recipients opt out of the artificial or pre-recorded healthcare-related call:

  • State the identity of the entity*
  • State the entity’s phone number* that allows the recipient to make a do-not-call request during regular business hours. 
  • The message must include an automated, interactive voice and/or key press-activated opt-out mechanism within two seconds of the identification message. 
  • Brief instructions on how to use the mechanism.
  • If the recipient elects to opt-out, the mechanism must record the recipient’s number to the do-not-call list and immediately terminate the call. 
  • If the call is left on an answering machine or a voice mail service, the automated message must leave a toll-free number that leads the recipient to the opt-out mechanism above. 

mPulse diligently adheres to these requirements in our IVR scripting, ensuring that all information is provided, including contact information and instructions for opting out using our key-press-activated mechanism. Moreover, our technology enables the management of do-not-call information at an account level for do-not-call requests made directly to mPulse.**

3. Ensure that the entity* making the healthcare-related calls has a do-not-call policy. The do-not-call policy must be in writing, and the personnel must be trained on do-not-call practices. As for the specifics, consumer do-not-call requests must be honored within 30 days of receipt. The party seeking to be placed on the do-not-call list must provide their name (or their entity’s name) and number(s) for inclusion on the do-not-call list. Furthermore, companies must maintain records of do-not-call requests for five years.

It’s important to note that while mPulse offers a robust platform for managing these communications, the responsibility for creating a written policy and training personnel on the do-not-call list primarily lies with the healthcare organization. We understand our partners’ needs and procedures may vary, and we aim to provide the necessary tools and support to facilitate compliance. With mPulse software, we ensure that do-not-call requests are promptly recorded and retained for five years, which is vital to regulatory adherence. However, it remains our partners’ duty to maintain a holistic list that captures all do-not-call requests – especially ones made directly to their call center.

Navigating the complexities of TCPA regulations can be daunting, but with mPulse, healthcare organizations can find a reliable partner to help them navigate these intricacies seamlessly. We understand the nuances of TCPA and are well-equipped to guide healthcare organizations toward compliance while ensuring that their digital engagement remains robust and effective. Moreover, mPulse offers diverse health communication solutions, including text messaging, email, and mobile web, providing healthcare organizations with a comprehensive toolkit to engage consumers and achieve the best possible outcomes. With our expertise and multifaceted approach, we are here to support healthcare organizations in delivering top-notch services while adhering to regulatory standards.

Please visit the Code of Federal Regulations website to learn more about TCPA changes.

*Refers to healthcare organizations mPulse partners with

**mPulse is not liable for a complete do-not-call list as the healthcare organizations we partner with may have multiple lists from historical vendors, direct requests from members, or other various do-not-call requests in the healthcare organization’s database. To comply with TCPA, it’s imperative that the healthcare organization manages and owns the holistic do-not-call list with or without mPulse technology and that the correct list is sent to mPulse prior to the launch of the solution.


Stay up to Date on the Latest News & Resources