Provider certification record

WooSender, Inc.

Listed
RMD number
RMD0030292
FRN
0036763399
OCN
 

Identity

Legal business name
WooSender, Inc.
Doing-business-as
WooFederal, WooStaffing, All In One Networking
Foreign Voice Service Provider
No
Business address
3409 Capri Court, Philadelphia PA 19145
Filing contact
Paul Lean
Chief Operation Officer · Operations
paul@woosender.com
(604) 354-7735
1323 SE 17th St. PMB 98286 Ft Lauderdale PA 33316
United States of America
Principals, Affiliates, Subsidiaries, and Parent Companies
WooFederal, WooStaffing, All In One Networking

Classification

Provider role(s)
  • Voice service provider
STIR/SHAKEN implementation
RoleImplementation
Voice service providerNone
OverallNone
Exemption rules
Rule Cited The exemption arises under 47 CFR § 64.6305(a). This rule provides that filers who have not implemented the STIR/SHAKEN authentication framework on their networks may instead certify that all calls they originate are subject to a robocall mitigation program. Explanation of Why It Applies WooSender does not qualify as a Voice Service Provider (VSP) with numbering resources or direct interconnection to the public switched telephone network (PSTN). Instead, WooSender operates solely as a software platform. All outbound calls are originated and authenticated through upstream VSP partners—Bandwidth, Twilio, and Plivo—who are registered providers of record responsible for STIR/SHAKEN implementation. Because WooSender: Does not control numbering resources – All telephone numbers used for calling are provisioned and managed by its upstream VSP partners. Does not directly originate calls on the PSTN – Call origination and authentication are performed at the carrier level (Bandwidth, Twilio, Plivo). Cannot implement STIR/SHAKEN independently – As a software-only provider without direct PSTN access, WooSender has no technical ability to deploy STIR/SHAKEN. Therefore, under § 64.6305(a), WooSender certifies compliance through a robocall mitigation program that includes: Taking reasonable steps to avoid originating illegal robocall traffic, Cooperating fully with the Industry Traceback Group and law enforcement, and Responding within 24 hours to all traceback requests. For these reasons, the filer is exempt from direct STIR/SHAKEN implementation and properly certifies under Option 3 in the Robocall Mitigation Database.

Prior investigations / actions

Description
 

Robocall mitigation plan

Declaration

By
Paul Lean
Date
2025-09-11No Recertification Date

Listing history

DateEventDetail / diff
2025-09-11NewInitial certification filed and added to database.