Provider certification record

ProMedia Inc.

Listed
RMD number
RMD0006978
FRN
0031420797
OCN
 

Identity

Legal business name
ProMedia Inc.
Doing-business-as
 
Foreign Voice Service Provider
No
Business address
13499 BISCAYNE BLVD., TS6, Miami FL 33181
Filing contact
Will Sabol
VP of Technology · Technology
technology@promedia.com
(800) 814-6037
13499 BISCAYNE BLVD. TS6 Miami FL 33181
United States of America
Principals, Affiliates, Subsidiaries, and Parent Companies
Will Sabol

Classification

Provider role(s)
  • Voice service provider
STIR/SHAKEN implementation
RoleImplementation
Voice service providerNone
OverallNone
Exemption rules
ProMedia Inc. does not own or operate telecommunications network infrastructure and lacks control over the network infrastructure necessary to implement STIR/SHAKEN, pursuant to 47 CFR § 64.6305(d). All calls originated by ProMedia are transmitted exclusively through the IP-based networks of its upstream carriers, Twilio Inc. and Bandwidth Inc., both of which have fully implemented STIR/SHAKEN on the IP portions of their networks and authenticate calls under their own STIR/SHAKEN credentials.

Prior investigations / actions

Description
ProMedia Inc. (RMD ID: RMD0006978) was subject to removal from the Robocall Mitigation Database by Commission action pursuant to Enforcement Bureau Order DA 25-737, released August 25, 2025. (1) Law enforcement or regulatory agencies involved: Federal Communications Commission, Enforcement Bureau and Wireline Competition Bureau. (2) Date action or investigation commenced: The compliance review began following the February 26, 2024 deadline for updated RMD certifications. ProMedia was notified via email on March 29, 2024 that its certification was noncompliant. A Show Cause Order was issued on December 10, 2024, and the removal order (DA 25-737) was released on August 25, 2025. (3) Current status: The Enforcement Bureau provisionally reinstated ProMedia Inc.'s RMD filing on August 29, 2025, following ProMedia's submission of a revised Robocall Mitigation Plan and updated certification through the RMD portal on August 27, 2025. (4) Summary of findings: ProMedia Inc. was found to have a deficient RMD certification because (a) the robocall mitigation plan lacked information required to be submitted by February 26, 2024, and (b) the certification lacked information required by that same date. No findings of illegal robocalling, spoofing, or other substantive wrongdoing were made. (5) Final determinations: The removal order (DA 25-737) was issued on August 25, 2025. ProMedia's filing was provisionally reinstated on August 29, 2025, pending completion of its updated certification. Explanation for failure to respond to FCC notices: ProMedia takes full responsibility for failing to receive critical FCC communications due to an administrative oversight. The FCC properly sent notifications to allen@promedia.com, which was the designated RMD contact email on file. However, the employee associated with that email address, left ProMedia in June 2023. Due to inadequate transition procedures, ProMedia failed to: (a) update the RMD contact information after his departure, (b) establish email monitoring or forwarding for RMD-related communications, and (c) maintain proper oversight of FCC compliance obligations. As a result, ProMedia did not receive the March 29, 2024 email notification, the April 29, 2024 deadline notice, or the December 10, 2024 Show Cause Order. ProMedia had no actual knowledge of these requirements until August 26, 2025. Explanation for failure to update by February 26, 2024 deadline: For the same reasons stated above, ProMedia was unaware of the amended RMD requirements that took effect on February 26, 2024. The company's designated contact had departed, and no internal process existed to monitor FCC regulatory updates or ensure compliance with new filing requirements. Upon learning of the situation on August 26, 2025, ProMedia immediately took steps to cure all deficiencies and submitted its revised filing on August 27, 2025. ProMedia has since updated its contact information and implemented procedures to prevent similar failures in the future.

Robocall mitigation plan

PDF Robocall_Mitigation_Plan_2026_3.pdfFiled 2026-02-18 · 1.1 MB

Declaration

By
Will Sabol
Date
2026-02-18No Recertification Date

Listing history

DateEventDetail / diff
2026-02-18NewInitial certification filed and added to database.