Internet-Based Telecommunications Relay Service Modernization
The Federal Communications Commission (Commission) proposes to modernize its telecommunications relay services (TRS) rules and seeks comment on the use of automatic speech recognition (ASR) for speech-to- text conversion and advanced text-to-speech technologies for Internet Protocol (IP) Relay Service; the need for metrics for IP Relay quality; the compatibility of IP Relay with Real-Time Text (RTT) technology; adding captioning functionality to Video Relay Service (VRS) platforms; amending VRS calling rules for calls to U.S. embassies and consulates by U.S. residents while traveling abroad; adjusting VRS call center requirements; streamlining TRS provider certification and user registration processes; updating or eliminating obsolete rules; and closing outdated dockets. With these proposals, the Commission presents targeted reforms that align internet-based TRS with twenty-first century technological advancements in relay services that can better serve the needs of persons with disabilities while securing the viability and enhancing the effectiveness and functional equivalency of internet-based TRS.
What this rule actually says
The FCC is proposing new rules for telecommunications relay services (TRS)—services that help deaf and hard-of-hearing people make phone calls. The proposal focuses on modernizing how these services work, particularly by allowing AI speech-recognition and text-to-speech technology instead of human operators in some cases, and adding captions to video relay services. It's still a proposal being debated, not final law yet.
Who it applies to
- If you're building a medical scribe, hiring assistant, or support chatbot that doesn't touch phone calls or relay services: This almost certainly doesn't apply to you.
- If you're building IP-based phone relay software or a video calling service specifically marketed to deaf/hard-of-hearing users: This applies to you.
- If you're using ASR (speech-to-text) or TTS (text-to-speech) technology in a general consumer app: This doesn't apply unless you're explicitly operating a relay service under FCC jurisdiction.
- Jurisdiction: U.S. only (FCC authority).
- Data scope: The proposal discusses how relay services handle conversation data between callers and relay operators/AI systems—not general user data collection.
What founders need to do
- Check if you operate a relay service (1 day): Ask yourself: Am I providing a service specifically designed to enable phone communication for people with hearing or speech disabilities? If no, stop here.
- Monitor the rulemaking process (ongoing, minimal effort): This is still "proposed"—it's not final. Subscribe to FCC updates on this docket or set a calendar reminder to check back in 6 months. The rules could change substantially during the comment period.
- If you do operate relay services, review the proposal details (3-5 days): Once the proposal is final, you'll need to understand specific quality metrics for AI-generated captions, ASR accuracy standards, and any new registration/certification requirements for TRS providers. This likely requires legal input.
- Budget for compliance if rules finalize (timeline unknown): If you offer relay services, expect to audit or upgrade your AI systems to meet whatever standards the FCC settles on, and possibly update your certification.
Bottom line
Monitor but don't act yet—this is a proposed rule that won't affect most indie AI founders, and it's still in comment phase.