Regulatory update · FCC & rulemaking

Voximplant Admits Noncompliant Robocall Mitigation Filing in FCC Consent Decree

The bottom line: on July 8, 2026, the Enforcement Bureau of the Federal Communications Commission (FCC) adopted a Consent Decree with Voximplant, Inc. (DA 26-644). Voximplant admitted that its Robocall Mitigation Database (RMD) certification was noncompliant with RMD requirements and agreed to implement a compliance plan. The order terminated the Bureau's investigation.

By Harrison GevirtzPublished 1 min read
On this page

The order and consent decree are attached: FCC Voximplant consent decree.

What happened

According to the order:

  1. The Wireline Competition Bureau reviewed RMD certifications and notified Voximplant that its certification and robocall mitigation plan were deficient.
  2. Voximplant failed to reply, and the matter was referred to the Enforcement Bureau.
  3. On August 6, 2025, the Bureau removed Voximplant's certification from the RMD.
  4. The parties then executed the Consent Decree.

What Voximplant agreed to

  • Admission. Respondent admitted, for purposes of this decree and the civil enforcement process of the FCC, that the statement of facts set forth in the decree is true and correct.
  • Compliance Officer. Respondent shall designate a senior manager with authority to act as Compliance Officer.
  • Compliance Plan. Respondent shall implement a compliance plan and set of policies and procedures.

The law

The FCC created the RMD to increase transparency and improve robocall mitigation. Voice service providers must file RMD certifications and mitigation plans. Among other things, a filing must provide assurance that the company will fully and timely respond, within 24 hours, to traceback requests from the FCC, law enforcement and the industry traceback consortium. Removal from the RMD requires other providers to stop accepting a company's calls directly.

The FCC’s first mitigation database removals

Why it matters

An RMD filing is not something you complete and forget. A deficient filing, followed by silence, cost this company its place in the database. Reinstatement required an admission and a formal compliance program.

What this means for you

  1. Review your RMD filing now. Confirm it contains every required element.
  2. Answer agency deficiency notices. Nonresponse led to removal here.
  3. Assign ownership. Appoint someone senior to be responsible for robocall compliance.
  4. Track traceback response times. The 24-hour commitment is part of the filing.

Not legal advice. TCPA.com provides general information, not legal advice, and is not a substitute for the advice of an attorney. Do not rely on it. Verify any action with your own licensed lawyer before you take it. See our Terms of Use.

Primary sources

  1. Order and Consent Decree, In the Matter of Voximplant, Inc., DA 26-644, File No. EB-TCD-26-00040372 (FCC Enforcement Bureau, July 8, 2026).
Harrison Gevirtz, Chief Strategy Officer of Ringba, Las Vegas, Nevada

About the Author: Harrison Gevirtz

Harrison Gevirtz serves as the Chief Strategy Officer (CSO) of Ringba, a call tracking and pay per call platform, and is based in Las Vegas, Nevada. Harrison Gevirtz is a serial operator in call tracking, call routing and telemarketing operations, and for the past several years he has focused on how federal regulations affect the daily operations of these industries. At TCPA.com, Harrison Gevirtz covers TCPA litigation, Telemarketing Sales Rule (TSR) enforcement, tech support fraud prosecutions and Federal Communications Commission (FCC) rulemaking in a way that's accessible to the non-lawyer executive or compliance manager.

More from Harrison Gevirtz

Topics