Now that the June 30th deadline has passed, the industry is now in the execution phase of STIR/SHAKEN deployment and Robocall Mitigation Plan fulfillment.
Service providers have the responsibility to vet and validate the authenticity of the callers originating traffic on their networks, and attest to the authorized usage of the phone numbers to be displayed.
If you are a service provider who is currently signing enterprise calls at B or C-Level, looking for a solution to elevate these calls to A-Level, a KYC process has to be implemented to authenticate each intermediary along the call chain down to the calling party brand in order to fulfill the due diligence requirements as set forth by the FCC.
Implementation of a KYC-based local policy solution, such as the Aegis Mobile + Numeracle solution, supports service and platform provider’s ability to assess the level of attestation achievable based on the availability of information to vet and verify down to the enterprise or calling party brand, with confidence.
For a deeper dive on what STIR/SHAKEN is, where it came from, and how it affects Attestation levels, visit our STIR/SHAKEN Knowledge Center.
With your Verified Identity successfully associated with your phone numbers and RCD (rich call data), Numeracle then passes this information to your originating service provider or other authority for call signing, such as NetNumber’s Guaranteed Caller Enterprise STIR/SHAKEN solution.
To complete the process, the call is assigned a level of attestation relational to the level of validation completed. The call is passed to the terminating service provider. The result is a call delivered as STIR/SHAKEN authenticated, displayed with a verified caller display and optional RCD information available.