Provider certification record

TeleWise, LLC

Listed

Identity

Legal business name: TeleWise, LLC
Doing-business-as
Foreign Voice Service Provider: No
Business address: 14241 NE Woodinville Duvall Rd. #134, Woodinville Washington 98072
Filing contact: Charles Power
President · Executive
charles@telewise.com
(206) 245-9012
14241 NE Woodinville Duvall Rd. #134 Woodinville Washington 98072
United States of America
Principals, Affiliates, Subsidiaries, and Parent Companies: Charles Power, Principal

Provider role(s): Voice service provider
Intermediate provider
STIR/SHAKEN implementation: Role Implementation
Voice service provider None
Intermediate provider None
Overall None
Exemption rules: See 47 C.F.R. § 64.6304(d). The Company provides service on a TDM network and therefore cannot initiate, maintain, carry, process, or terminate SIP calls. TeleWise is participating through a third-party representative in an industry-led group that is working to develop a non-IP caller identification authentication solution as follows: TeleWise is a client of Inteserra. Inteserra is part of the Alliance for Telecommunications Industry Solutions (ATIS) that has a Non-IP Call Authentication Task Force developing a call authentication solution for non-IP communications providers with which Inteserra is actively engaged. Inteserra has informed TeleWise that it will work with its non-IP clients (like TeleWise) to communicate and implement industry solutions for non-IP providers developed in the ATIS Task Force.

Description: The filing entity has never been the subject of a formal Commission, law enforcement, or regulatory agency action or investigation with accompanying findings of actual or suspected wrongdoing due to the filing entity transmitting, encouraging, assisting, or otherwise facilitating illegal robocalls or spoofing. However, the filer was named in an FCC Enforcement Bureau Order issued on December 10, 2024 (DA 24-1235; Docket No. EB-TCD-24-00036891) directing 2,411 companies to cure alleged deficiencies in their Robocall Mitigation Database certifications or, in the alternative, provide a sufficient explanation for why a company should otherwise retain its certification in the RMD. Without admitting any violation of the Commission’s rules and regulations, by this submission on December 31, 2024, the filer herein seeks to update the information in the RMD to address any perceived deficiencies with its previous RMD certification filing.

Date	Event	Detail / diff
2025-11-25	New	Initial certification filed and added to database.