Provider certification record
Firstoutcomes, Inc
Listed- RMD number
- RMD0015295
- FRN
- 0034272153
- OCN
Identity
- Legal business name
- Firstoutcomes, Inc
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 800 3rd Ave, Suite A #614, New York NY 10022
- Filing contact
- Seetha Ganesan
CTO · Management
sganesan@firstoutcomes.com
(415) 308-6769
1070 Hedgecroft Pl Suite A #614 San Jose CA 95120
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- Dinesh Gambhir, CEO Seetha Ganesan, CTO
Classification
- Provider role(s)
- Gateway provider
- STIR/SHAKEN implementation
Role Implementation Gateway provider None Overall None - Exemption rules
- First Outcomes Inc. does not operate or control the voice network infrastructure necessary to implement STIR/SHAKEN directly and does not authenticate calls directly. All outbound calling traffic is originated through our upstream carrier, Bandwidth.com, which performs STIR/SHAKEN authentication/attestation for calls originated using its network. Accordingly, First Outcomes Inc. is unable to implement STIR/SHAKEN due to a lack of control over the network infrastructure necessary to implement STIR/SHAKEN.
Prior investigations / actions
- Description
- 5/21/2026 As requested by the FCC 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). Answers 1. All law enforcement or regulatory agencies involved: The Federal Communications Commission (FCC), specifically the Enforcement Bureau (EB) and the Wireline Competition Bureau (WCB). 2. The date that any action or investigation was commenced: The formal process that led to the removal began with the issuance of the Show Cause Order on December 10, 2024, under investigation File No. EB-TCD-24-00036891 (later assigned File No. EB-TCD-25-00038590). 3. The current status of the action or investigation: The company's RMD filing was provisionally reinstated on September 17, 2025, but deficiencies remain, and the company must correct the remaining deficiency concerning the insufficient description of the action/investigation itself. The provisional reinstatement is explicitly noted as "not a final determination regarding the compliance of the company’s filing with the Commission’s rules. 4. A summary of the findings of wrongdoing made in connection with the action or investigation: The FCC found the RMD certification was deficient because the company failed to update its certification and submit a robocall mitigation plan with newly required information by the February 26, 2024 deadline, and subsequently failed to cure the deficiencies or provide sufficient explanation as required by the December 10, 2024 Show Cause Order. 5. Whether any final determinations have been issued: Yes. A final determination was issued on August 25, 2025, in an Order (DA 25-737) by the Acting Chief, Enforcement Bureau. This Order formally removed the company’s certification from the RMD and required all intermediate providers and voice service providers (such as Bandwidth) to cease accepting all traffic directly from the company 12/10/2024 In August 2025, the Company was subject to a formal actions by the FCC’s Enforcement Bureau regarding deficiencies in its Robocall Mitigation Database (RMD) filing. • On August 25 , 2025, the Company’s filing was removed from the RMD. • On September 17, 2025, the Company’s filing was provisionally reinstated pending required corrections. • On November 21, 2025 the Company was asked to address deficiencies in its RMD filing The Company has now updated its RMD filing and robocall mitigation plan by: (1) describing the FCC actions it was subject to, (2) accurately reporting reliance on upstream STIR/SHAKEN signing by Bandwidth.com; and (3) updating and expanding our Robocall Mitigation Plan to align fully with FCC Option 3 (Mitigation Certification). No other enforcement actions, investigations, or formal proceedings have occurred.
Robocall mitigation plan
Declaration
- By
- Dinesh Gambhir
- Date
- 2026-05-21No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2026-05-21 | New | Initial certification filed and added to database. |