Provider certification record
ConnX Inc.
Listed- RMD number
- RMD0008963
- FRN
- 0031517642
- OCN
Identity
- Legal business name
- ConnX Inc.
- Doing-business-as
- Atlas ConnX
- Foreign Voice Service Provider
- No
- Business address
- 103 Morgan Lane, Suite 104, Plainsboro NJ 08536
- Filing contact
- Heather Palmucci
Product Development Manager · Product Development
heather.palmucci@connxai.com
(978) 501-2827
103 Morgan Lane Suite 104 Plainsboro NJ 08536
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Mark Beranek
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- § 64.6304 Extension of implementation deadline (a) Small voice service providers Voice service providers, gateway providers, and non-gateway intermediate providers that cannot obtain an SPC token. Voice service providers that are incapable of obtaining an SPC token due to Governance Authority policy are exempt from the requirements of § 64.6301 until they are capable of obtaining an SPC token. ConnX did not qualify for an SPC token when applying through iconectiv.com. ConnX is now engaging with NECA to meet qualifications for OCN code assignment. Once we obtain the OCN we are completing our application with iconectiv.com to finish the SPC token process. ConnX is also actively working with TransNexus on connectivity testing as part of our RMD plan implementation.
Prior investigations / actions
- Description
- 1) Law Enforcement or Regulatory Agencies Involved Federal Communications Commission Enforcement Bureau 2) Date Action or Investigation Commenced Robocall Mitigation Database Filers, Order (August 25, 2025) Robocall Mitigation Database Filers, Show Cause Order (March 24, 2026) 3) Current Status of the Action or Investigation Robocall Mitigation Database Filers, Order (August 25, 2025) Current Status: ConnX was provisionally reinstated in the Robocall Mitigation Database August 29, 2025 via email from RMDReinstatementRequest@fcc.gov. Downstream providers may resume accepting your traffic in accordance with FCC rules (47 CFR § 64.6305(g)). This provisional reinstatement is not a final determination regarding the compliance of the company’s filing with the Commission’s rules. Specifically, under the rules, any voice service provider, gateway provider, and non-gateway intermediate provider (as defined in 47 CFR § 64.6300) must submit a filing in the RMD that contains the information, certifications, and robocall mitigation plan described in 47 CFR § 64.6305 and on the RMD submission form, including a statement regarding whether the provider has been the subject of a formal Commission, law enforcement, or regulatory agency action in the prior two years, which includes the Enforcement Bureau’s August 6, 2025, and August 25, 2025, Removal Orders. Additional information regarding providers’ obligations can be found in the RMD Filing Deadlines and Instructions Public Notice, and in the entirety of Subpart HH in Title 47 of the Code of Federal Regulations. Deficiencies may still exist in your filing, which the company should promptly address. Robocall Mitigation Database Filers, Show Cause Order (March 24, 2026) Current Status: ConnX continues to be in a provisionally reinstated status. Below are the dates and description of correspondence regarding remediation actions to address Show Cause Order (March 24, 2026). May 18, 2026: ConnX updates our RMD filing and notified Enforcement Bureau that an update has been submitted. May 12, 2026 3:07pm ET Enforcement Bureau acknowledges our status update email: Thank you for this update, Heather. Please let us know when all other updates to the filing have been made so that Commission staff can review. Please also keep us updated about the STIR/SHAKEN implementation. As previously stated, the Company will continue to be provisionally reinstated while the STIR/SHAKEN implementation is underway. Tuesday, May 12, 2026 9:38 AM ConnX provides status update email: Good morning, I want to provide an update. We have applied for an OCN. We should be receiving that shortly. Our application at iconectiv/ STI – PA is submitted but pending receipt of OCN. We are focused on moving out of Provisional status and actively taking steps to meet Full RMD compliance. Thank you again for your assistance. Friday, May 1, 2026 8:57 AM ConnX sent thank you email (for informational conf call): Thank you for your assistance today. It was a very productive call. Thursday, April 30, 2026 4:15 PM Meeting summary and follow from Enforcement Bureau: Hello Heather and Masoud, It was good to speak with you and your team this afternoon. I hope that you found the call productive. As discussed, here is the August 29 email thread between the Bureau and the Company communicating the Company’s provisional reinstatement. Thu 4/30/2026 3:30 PM - 4:00 PM RMD Follow-Up Teams meeting: Attendees: Lauren Merck, Heather Palmucci, Masoud Majidi and Satya Prakash Tuesday, April 28, 2026 3:12:13 PM Enforcement Bureau sent calendar invite: We just sent a calendar invite for Thursday at 3:30pm ET. The calendar invite includes a Teams link. Tuesday, April 28, 2026 2:52 PM ConnX response to Enforcement Bureau: Thursday, April 30 between 3:30 PM and 4:40 PM Eastern time, please. Tuesday, April 28, 2026 2:32:21 PM ConnX accepted offer from Enforcement Bureau to host a call: Do you have any availability on Thursday, April 30 between 3:30pm and 4:40pm ET, or on Friday, May 1 after 1:30pm ET? Tuesday, April 28, 2026 1:15 PM Connx accepts Enforcement Bureau meeting offer: Thank you for offering a brief call to help clarify. I would like to set up a call to discuss the RMD filing requirements. Please let me know what times are available to discuss. Tuesday, April 28, 2026 11:45 AM Enforcement Bureau responds with additional required changes: Thank you for updating the Company’s filing. There still appears to be deficiencies in the description of the prior actions. Please ensure that the description includes the correct date of the August 2025 RMD order in which the Company was specifically named. Please also ensure the description includes a complete summary of the current status of the August 2025 action. If you would like to set up a call to discuss the RMD filing requirements, we can arrange a brief conversation. Please note, we will not be able to provide legal advice, but we can discuss the RMD and filing requirements generally. Monday, April 27, 2026 2:19 PM ConnX notifies Enforcement Bureau of updates to our RMD filing: I am emailing to notify you that the deficiencies described below have been corrected. The RMD Portal has been updated with revised responses. Thank you for providing the links. Please let us know if any additional information or clarification is needed to support your review. Tuesday, April 14, 2026 11:15 AM Enforcement Bureau notifies ConnX requires changes: Thank you for updating the Company’s filing. Commission staff have identified the following remaining deficiencies that must be corrected: 1. The Company does not sufficiently describe the actions or investigations that it was subject to. Note: this field asks for multiple pieces of information that the Company must provide a description for. Specifically, the field instructs: Provide a description of any such action or investigation, including (1) all law enforcement or regulatory agencies involved, (2) the date that any action or investigation was commenced, (3) the current status of the action or investigation, (4) a summary of the findings of wrongdoing made in connection with the action or investigation, and (5) whether any final determinations have been issued (if you require more space, please provide this information in your robocall mitigation program description). Please ensure that the description includes each element required by the instructions, including the specific dates of the actions, and accurate descriptions of the current status, findings, and whether any final determinations have been made. Please refer to the August RMD orders and the March 2026 Show Cause Order for additional information about the enforcement actions: In the Matter of Robocall Mitigation Database Filers, Order (August 6, 2025) https://docs.fcc.gov/public/attachments/DA-25-694A1.pdf In the Matter of Robocall Mitigation Database Filers, Order (August 25, 2025) https://docs.fcc.gov/public/attachments/DA-25-737A1.pdf In the Matter of Robocall Mitigation Database Filers, Show Cause Order (March 24, 2026) https://docs.fcc.gov/public/attachments/DA-26-282A1.pdf Please respond to this email once the revisions have been made. Moreover, here are links to some additional resources you may find useful: January 2026 Public Notice announcing the RMD changes: https://docs.fcc.gov/public/attachments/DA-26-72A1.pdf Robocall Mitigation Database Frequently Asked Questions For Filers: https://www.fcc.gov/sites/default/files/rmd-faq.pdf Monday, April 13, 2026 3:41 PM ConnX notifies Enforcement Bureau of updates to our RMD filing: Good afternoon Reinstatement Team, We have successfully submitted our revised Robocall Mitigation Database (RMD) plan in the RMD portal today, incorporating the updates and clarifications requested in your prior correspondence. We appreciate your guidance throughout this process and remain committed to full compliance with all Federal Communications Commission requirements. Please let us know if any additional information or clarification is needed to support your review. Thank you for your time and consideration. Wednesday, April 8, 2026 11:28 AM Enforcement Bureau notifies ConnX changes required: Thank you for updating the Company’s filing. Commission staff have identified the following remaining deficiencies that must be corrected: 1. A human principal is not identified in the “Principals, Affiliates, Subsidiaries, and Parent Companies” field. 2. The Company does not answer “yes” in the field that asks providers whether they have been subject to a “formal Commission, law enforcement, or regulatory agency action or investigation . . .” Note: The removal orders issued in August 2025, and the Show Cause Order issued in March 2026 fall under this category. Once “yes” is selected, the Company must provide a description of the action or investigation in the next field. This field asks for multiple pieces of information that the Company must provide a description for 3. The Company’s RMD plan does not include Know Your Customer (KYC) plan, such as failing to indicate whether the Company uses a third-party vendor for analytics and identifying that vendor, not including the Company’s specific reasonable steps to mitigate illegal traffic, or not addressing how the Company applies its KYC plan to existing customers. Note: The Bureau cannot advise your Company on what this plan should be. Please respond to this email once the revisions have been made. Moreover, here are links to some additional resources you may find useful: January 2026 Public Notice announcing the RMD changes: https://docs.fcc.gov/public/attachments/DA-26-72A1.pdf Robocall Mitigation Database Frequently Asked Questions For Filers: https://www.fcc.gov/sites/default/files/rmd-faq.pdf Thursday, April 2, 2026 1:19 PM: Enforcement Bureau confirms receipt of ConnX RMD database updates: Thank you. This response is received and Commission staff will review the updated filing. Thursday, April 2, 2026 12:02 PM ConnX notifies RMDReinstatementRequest@fcc.gov of updates to our RMD filing: Hello Reinstatement team, Please confirm that our database filing for RMD has been recognized by FCC. We believe we have addressed the filing requirement to satisfaction. We understand that the remediation/reinstatement completion date is April 6 2026. If there is any further action required, please let us know at your earliest convenience. Thank you for your help with this serious matter. Wednesday, April 1, 2026 10:02 AM ConnX notifies enforcementbureauTCD@fcc.gov our RMD filing has been updated: To Whom It May Concern, This letter is in response to the Federal Communications Commission (FCC) Cure Notice issued March 24, 2026 to ConnX Inc (RMD0008963) regarding deficiency in our filing within the Robocall Mitigation Database (RMD). Upon receipt of the Cure Notice, we conducted an immediate review of our compliance status and identified that our RMD filing was completed on March 24, 2026. The RMD web portal reflects this status. The required RMD filing was successfully completed and submitted on the same day the Cure Notice was issued. ConnX Inc takes its obligations under the FCC’s STIR/SHAKEN and robocall mitigation framework very seriously. We have implemented internal compliance controls to ensure ongoing adherence to all applicable requirements, including timely updates and verification of our RMD filings. We respectfully request confirmation that our corrective action satisfies the requirements outlined in the Cure Notice and that no further action is required at this time. Please do not hesitate to contact us should you require any additional information or documentation. 4) Summary of Findings of Wrongdoing Robocall Mitigation Database Filers, Order (August 25, 2025) EB-TCD-25-000385901 The FCC Enforcement Bureau removed ConnX’s RMD certification due to missing or incomplete required filings by February 26, 2024, and failure to cure deficiencies or respond to a December 10, 2024 Order. As a result, providers must stop accepting calls from ConnX, and reinstatement requires prior FCC WCB and Bureau approval. Robocall Mitigation Database Filers, Show Cause Order (March 24, 2026) EB-TCD-25-00038590 The FCC Enforcement Bureau ordered ConnX to cure deficiencies in its RMD certification—due to missing required information in its mitigation plan—or explain why it should not be removed. Failure would require providers to stop accepting ConnX calls (except emergency), with a 14-day deadline to respond. 5) Final Determinations ConnX has completed necessary remediation and implemented new controls to assure timely compliance with future FCC rulings and guidelines. This includes assigning a primary Compliance lead, calendar reminders, subscribed to FCC notifications and regular compliance meeting cadence to stay ahead of FCC compliance requirements.
Robocall mitigation plan
Declaration
- By
- Heather Palmucci
- Date
- 2026-05-18No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-05-18 | New | Initial certification filed and added to database. |