Provider certification record
Kenect, LLC
Listed- RMD number
- RMD0009152
- FRN
- 0031550593
- OCN
Identity
- Legal business name
- Kenect, LLC
- Doing-business-as
- Foreign Voice Service Provider
- No
- Business address
- 1064 S N County Blvd, Suite 300, Pleasant Grove UT 84062
- Filing contact
- Jeff Jones
Chief Operating Officer · Operations
jjones@kenect.com
(888) 972-7422
1221 Valley Grove Way Suite 400 Pleasant Grove UT 84062
United States of America - Principals, Affiliates, Subsidiaries, and Parent Companies
- PSG Equity
Classification
- Provider role(s)
- Voice service provider
- STIR/SHAKEN implementation
Role Implementation Voice service provider None Overall None - Exemption rules
- Kenect, LLC (“Kenect”) (https://www.kenect.com/) offers a text messaging platform to business customers. Kenect offers no voice services to customers. Kenect permits a business customer to send and receive text messages to the business customer’s customers. The Commission considers text messaging information services. However, Kenect’s platform will forward voice calls from the text message recipient to each customer’s main business line upon receiving calls to the text message originating telephone number. Kenect submits this RMP in accordance with the Commission’s rules applicable to voice service providers to the extent the Commission deems Kenect’s call forwarding feature a “voice service” as set forth in Section 64.6300(l) of the Commission’s rules, 47 C.F.R. §64.6300(l). For all voice traffic, Kenect lacks control of the network infrastructure necessary to implement the STIR/SHAKEN authentication framework. All voice traffic originating on Kenect’s network is authenticated under the STIR/SHAKEN authentication framework pursuant to 47 CFR § 64.6301(a) by either Twilio or Bandwidth as set forth below. Accordingly, Kenect performs Robocall Mitigation as set forth below in this RMP. Pursuant to Section 64.6305 of the Commission’s rules, 47 C.F.R. § 64.6305, Kenect commits to taking all such reasonable steps to avoid originating illegal robocall traffic and to respond fully and in a timely manner to all traceback requests from the Commission, law enforcement, and the industry traceback consortium, and to cooperate with such entities in investigating and stopping any illegal robocallers from using Kenect service to originate calls. Importantly, Kenect exercises no control over the relevant network infrastructure to implement the technical requirements of STIR/SHAKEN described under 47 C.F.R. §64.6301. As such, under the Commission’s robocall mitigation orders, Kenect is not required to implement STIR/SHAKEN.2 In fact, Kenect contracts with Twilio and Bandwidth (third-party providers) to facilitate termination of calls forwarding as a result of the customer returning calls to the originating text number as well as to obtain telephone numbers used by customers if necessary to provide text messaging services. Kenect understands that Twilio and Bandwidth obtain the necessary Service Provider Code (“SPC”) Tokens and implement the various STIR/SHAKEN attestation levels and technical requirements for any voice communications resulting from call forwarding that originate on either Twilio or Bandwidth’s network. Kenect’s information service requires no Operating Company Number (“OCN”) nor has the National Exchange Carriers Association assigned Kenect an OCN. Kenect does not meet the requirements to receive, and has not received, an SPC Token under the Secure Telephone Identity Governance Authority’s Token Access Policy. Kenect’s current operations remain subject to the indefinite STIR/SHAKEN implementation extension under 47 C.F.R. §64.6304(b). Kenect maintains no control over the relevant network infrastructure to implement the technical requirements of STIR/SHAKEN and is without the ability to obtain an SPC Token.
Prior investigations / actions
- Description
Robocall mitigation plan
Declaration
- By
- Jeff Jones
- Date
- 2024-12-31No Recertification Date
Listing history
| Date | Event | Detail / diff |
|---|---|---|
| 2024-12-31 | New | Initial certification filed and added to database. |