Advanced Methods To Target and Eliminate Robocalls
In this document, the Federal Communications Commission (Commission) proposes steps to improve the availability and accuracy of caller identification information transmitted to consumers to enable them to better understand who is calling and decide whether to answer calls. Specifically, the Commission proposes to enhance the effectiveness of STIR/SHAKEN by requiring terminating providers to transmit verified caller name or other caller identity information for presentation on a consumer's handset whenever they transmit an indication that a call has received an A-level attestation. It also seeks comment on requiring providers to use Rich Call Data (RCD) to transmit verified caller name on IP networks, whether to permit or require use of other solutions, and an alternative option to require that providers implement RCD in their IP networks for all calls. The Commission further proposes to require voice service providers to implement measures to ensure that consumers know which calls originate from outside of the United States and to prohibit spoofing of United States telephone numbers for calls that originate from outside of the United States. Finally, the Commission seeks comment on whether some of its calling-related rules can be simplified, streamlined, or eliminated, perhaps because they are outdated or have not been enforced for a substantial amount of time.
What this rule actually says
The FCC wants to make phone calls clearer so people know who's really calling them. Right now, robocalls and spoofed numbers (fake caller IDs) are rampant. This rule proposes requiring phone carriers to show verified caller information on your phone's screen and block calls pretending to be from US numbers when they're actually coming from overseas. It's still in the "we're asking for comments" phase, not yet final.
Who it applies to
- If you make outbound phone calls to end users (medical scribes calling patients, hiring assistants calling candidates, support bots calling customers): This likely applies to you, at least eventually.
- If you only send text or email, never voice calls: You're probably fine. This is specifically about phone calls.
- If you're in the US and your service makes calls into the US: This applies. The rule covers calls originating from or terminating in the US.
- If you use a third-party calling platform or API (Twilio, Amazon Connect, etc.): Your vendor may handle compliance for you—check their documentation.
- If you operate outside the US and don't call US numbers: Still doesn't apply to you right now.
What founders need to do
- Figure out your calling footprint (1-2 days): Document whether your product makes outbound calls, who you're calling, and through what service. If the answer is "we don't make calls," stop here.
- Check your vendor's roadmap (1 day): If you use Twilio, Amazon Connect, or similar, email support asking if they're implementing STIR/SHAKEN and caller name verification. Most major vendors are already compliant or have plans.
- Monitor FCC updates (ongoing, ~5 min/quarter): This is proposed, not final. Subscribe to FCC telecom alerts or check back in 6 months. The actual requirements might change during the public comment period.
- Verify your caller ID (1-2 days, one-time): Once rules solidify, you'll need to register your phone numbers with your carrier and ensure your outbound caller ID matches your actual business identity. Most carriers now require this anyway.
- Test before rollout (1-2 days): When the rule becomes final, test a few calls to verify your caller name appears correctly on recipients' phones.
Bottom line
Monitor this—it's not final yet—but if you make outbound calls to customers, budget for compliance within 12 months once the rule finalizes.