Provider certification record

Leadferno LLC

Listed
RMD number
RMD0009216
FRN
0031566300
OCN
417H

Identity

Legal business name
Leadferno LLC
Doing-business-as
 
Foreign Voice Service Provider
No
Business address
1299 6th St NW, Buffalo MN 55313
Filing contact
Joel Headley
Co-founder · Executive
joel@leadferno.com
(650) 440-1509
36319 Indian Wells Dr Newark CA 94560
United States of America
Principals, Affiliates, Subsidiaries, and Parent Companies
Principals (ownership and management): Aaron Weiche — Co-founder and Chief Executive Officer; owner/member of Leadferno LLC. Joel Headley — Co-founder and Head of Product & Engineering; owner/member of Leadferno LLC. Jeff Wagner — Head of Design; owner/member of Leadferno LLC. Michael Blumenthal — Advisor; owner/member of Leadferno LLC. Leadferno LLC has no parent company, no subsidiaries, and no affiliated entities. No person or entity other than those named above holds an ownership or control interest in Leadferno LLC.

Classification

Provider role(s)
  • Voice service provider
STIR/SHAKEN implementation
RoleImplementation
Voice service providerNone
OverallNone
Exemption rules
47 C.F.R. § 64.6305(d)(2)(i) — lack of control over the network infrastructure necessary to implement STIR/SHAKEN. Leadferno LLC is unable to implement the STIR/SHAKEN authentication framework because it does not control the network infrastructure necessary to do so. Leadferno is a software provider of two-way business text messaging, web-to-text conversion widgets, and lead-capture tools for small and medium-sized businesses. It owns and operates no switching equipment, softswitches, session border controllers, media gateways, or Internet Protocol networks over which voice traffic is carried. Leadferno has no network on which STIR/SHAKEN could be deployed and no point in any call path at which it could authenticate caller identification information. All voice transport, call routing, and interconnection with the Public Switched Telephone Network associated with Leadferno-hosted numbers is performed by Leadferno's underlying carrier, Bandwidth Inc., on Bandwidth's own network and under Bandwidth's own certificate. The only voice function in Leadferno's product is inbound call forwarding, which Bandwidth executes on its network pursuant to routing configuration data supplied by Leadferno's software. Leadferno has no outbound calling capability; neither Leadferno nor its customers can place a voice call through the platform. Consistent with the foregoing, Leadferno originates no voice calls and operates no Internet Protocol networks carrying voice traffic. Leadferno is also not an intermediate provider within the meaning of 47 C.F.R. § 64.6300(g), as it neither carries nor processes voice traffic. Leadferno holds Operating Company Number 417H, category IPES, assigned by the National Exchange Carrier Association on August 21, 2026. Leadferno has not registered with the STI Policy Administrator, holds no Service Provider Code token, and holds no STIR/SHAKEN certificate. Leadferno has not been granted numbering authorization under 47 C.F.R. § 52.15(g)(3) and obtains no numbering resources directly from the North American Numbering Plan Administrator or the Pooling Administrator. Leadferno maintains a robocall mitigation program consistent with 47 C.F.R. § 64.6305(a), described in the attached robocall mitigation program description, and commits to responding fully and within 24 hours to all traceback requests from the Commission, law enforcement, and the industry traceback consortium.

Prior investigations / actions

Description
(1) Agencies involved. The Federal Communications Commission — the Enforcement Bureau and the Wireline Competition Bureau. No other law enforcement or regulatory agency has been involved in any action or investigation concerning Leadferno LLC. (2) Date commenced. March 29, 2024. On that date the Robocall Mitigation Database Team of the Wireline Competition Bureau's Competition Policy Division emailed Leadferno, at the address listed as Leadferno's responsible point of contact, stating that Leadferno had not submitted an updated Robocall Mitigation Database filing by the February 26, 2024 deadline, that this constituted a violation of the Commission's rules, and that an updated certification and robocall mitigation plan were required by April 29, 2024. Leadferno received that email and did not submit an updated filing. On December 10, 2024, the Enforcement Bureau adopted an Order to Show Cause, DA-24-1235, naming Leadferno LLC in Appendix A under RMD file number RMD0009216 and requiring each named company either to cure its deficiencies and notify the Bureau, or to file a response, by December 31, 2024. The Bureau's Telecommunications Consumers Division emailed Leadferno the Order on December 10, 2024, and emailed Public Notice DA-24-1267, announcing the Order's publication in the Federal Register, on December 17, 2024. Leadferno received both. Leadferno read them and concluded they did not apply, because Leadferno's product places no voice calls and Leadferno did not understand itself to be a voice service provider. That conclusion was incorrect. Leadferno filed no response and took no corrective action by the December 31, 2024 deadline. The Bureau removed Leadferno's certification from the Robocall Mitigation Database by Order DA-25-737, released August 25, 2025. Leadferno is not named in the Bureau's August 6, 2025 order, DA-25-694. A prior version of this field stated that Leadferno received no letter of inquiry, notice of inquiry, or show cause order preceding DA-25-737. That statement was incorrect and is corrected here. (3) Current status. DA-25-737 is effective and final as to Leadferno's removal from the Robocall Mitigation Database. Leadferno is in active correspondence with the Wireline Competition Bureau and the Enforcement Bureau. Leadferno contacted both Bureaus by email on August 19, 2026, requesting consent to refile. The Bureau has identified deficiencies in Leadferno's filing on several occasions between August 20, 2026 and September 24, 2026, and Leadferno has corrected each deficiency identified. Leadferno's request for the Bureaus' consent to refile remains pending. No proceeding, investigation, or enforcement matter concerning Leadferno remains open other than this correspondence. (4) Summary of the findings of wrongdoing. The Bureau found that each company listed in Appendix A of DA-25-737, including Leadferno, had a deficient certification because a robocall mitigation plan was not provided or lacked information required to be submitted by February 26, 2024, and the certification lacked information required by that same date. Leadferno does not contest that finding. Leadferno's record in the Robocall Mitigation Database, RMD0009216, predates the requirements effective February 26, 2024 and shows no robocall mitigation plan attachment. Leadferno did not submit a robocall mitigation plan, and did not submit the updated certification and robocall mitigation plan required by February 26, 2024. Leadferno did not respond to the Wireline Competition Bureau's March 29, 2024 notice or to the December 2024 Order to Show Cause, as described above. No order, notice, or finding in this matter has alleged or determined that Leadferno transmitted, encouraged, assisted, or otherwise facilitated illegal robocalls or spoofing. Leadferno has never received a traceback request from the Commission, law enforcement, or the Industry Traceback Group. (5) Final determinations issued. Yes. DA-25-737 is a final Bureau-level order, effective upon release. It removed Leadferno's certification from the Robocall Mitigation Database and provided that Leadferno shall not refile absent the consent of both the Wireline Competition Bureau and the Enforcement Bureau. The March 29, 2024 notice and the December 2024 Order to Show Cause were interim steps preceding that order and were not themselves final determinations. No notice of apparent liability, forfeiture order, monetary penalty, consent decree, cease-and-desist order, civil action, or criminal proceeding has been issued or commenced against Leadferno by any agency. Additional disclosure. On August 19, 2026, not understanding that DA-25-737 barred refiling absent the Bureaus' consent, Leadferno completed and e-signed a Robocall Mitigation Database filing. Leadferno disclosed that filing to both Bureaus by email the same day, on its own initiative and before any inquiry. That filing also answered "No" to this question. The Bureau identified that answer as a deficiency on August 20, 2026, and Leadferno acknowledged the error and provided the correct answer by email the same day. This field has since been corrected further, as described in item (2) above.

Robocall mitigation plan

Declaration

By
Joel Headley
Date
2026-09-29No Recertification Date

Listing history

DateEventDetail / diff
2026-10-01NewInitial certification filed and added to database.