Branded Calling ID • Ecosystem explorer

Who does what in BCID?

An interactive, non-exhaustive map of providers and their reported roles. Explore how enterprises enter the ecosystem, get vetted, and deliver signed branded calls.

17 organizations4 rolesProvider snapshot: late 2025 / early 2026 · Wisp update: Oct 23, 2026
A working matrix, not an official directory. The official pages reviewed on October 23, 2026 describe roles but do not publish a named partner roster. Company assignments below reproduce the supplied compilation, with Wisp’s application-in-process update added October 23, 2026; individual company announcements were not independently verified for this page. An unconfirmed cell does not mean the company lacks that role.

Provider role matrix

Select a role card or use the controls. Expand a row’s notes for context and evidence limitations.

Yes Claim in supplied compilation   Reported Explicitly qualified claim   Yes* * In process — Wisp OSP / Signing applications; not confirmed authorization   — Not confirmed. Existing provider claims are not independently verified here.

BCID providers and supplied role claims
CompanyOnboardingVettingSigningOSPNotes / evidence context
Wisp / Local Splash · Application & pilot scope

Wisp’s role in the BCID ecosystem

OSP: Yes* Signing: Yes* * In process. Both roles have been applied for, per the October 23, 2026 update. This is not a statement of current BCID authorization. Wisp is the proposed OSP; Local Splash is the first enterprise brand.

Recommended use-case statement

Suggested wording for the BCID OSP application, TransNexus onboarding forms, or partner discussions.

Wisp.net is an FCC 499-filing Originating Service Provider that delivers VoIP application services to businesses, offices, and mobile-connected service contractors, including plumbing, HVAC, electrical, and similar trades.

We want to originate BCID-signed calls for these contractor customers so that their vetted business name, logo, and call reason appear on supported handsets. Our planning scope currently references T-Mobile and Verizon; actual display availability depends on carrier support, handset compatibility, and enabled BCID features. Local Splash is our first enterprise; we expect approximately 80 calling numbers under that brand initially, with additional contractor brands to follow.

We already perform our own A-level STIR/SHAKEN signing and will continue to do so for non-BCID traffic. For BCID, we will selectively route specific calls or telephone numbers through an authorized Signing Agent so that the PASSporT carries the vetted Rich Call Data (RCD) claims. We retain the ability to bypass BCID signing on a per-call or per-number basis.

We are not seeking to act as a general Onboarding or Vetting Agent for third-party enterprises outside our own customer base. Our role is that of the OSP for our contractor customers, using existing authorized Onboarding and Vetting Agents for the KYC and brand-validation steps.

Proposed operating model: Wisp originates selected contractor calls; existing authorized agents onboard, vet, and provide BCID signing. Wisp’s Signing application is separately marked in process above; it does not imply Wisp is already authorized to sign BCID calls.

Short version for an application form

Wisp.net is an FCC 499-filing OSP providing VoIP services to businesses and trade contractors. We seek selective BCID/RCD signing through an authorized Signing Agent, beginning with Local Splash and approximately 80 calling numbers. We retain A-level STIR/SHAKEN signing for non-BCID traffic and per-call/per-number BCID bypass. Existing authorized Onboarding and Vetting Agents will handle KYC and brand validation.

Why this framing works
  • Matches Wisp’s role as the OSP for a defined set of small-business VoIP customers.
  • Separates existing A-level attestation from the BCID/RCD layer needed on selected traffic.
  • Sets an expectation of selective, togglable use rather than all traffic indefinitely.
  • Avoids implying a marketplace Onboarding or Vetting Agent role, reducing scope and conflict-of-interest questions.
  • Gives TransNexus or another Signing Agent a concrete pilot: Local Splash, approximately 80 numbers, with room for additional contractor brands.
Example call-reason context

A plumber calls a customer to confirm an appointment. The selected call is routed through the BCID signing path so the vetted contractor brand and approved call reason can be conveyed to a supported handset.

Wisp company, application, and pilot details are supplied statements, not independently verified regulatory filings, carrier coverage guarantees, or authorization confirmations.

How the roles fit together

1 · Onboard the enterprise2 · Validate identity & brand assets3 · Cryptographically sign call data4 · Originate & deliver branded calls

Conceptual responsibilities, not a mandatory network sequence. Roles can overlap within one company. Terminating Service Providers (TSPs) handle display and confirmation at the receiving end; that separate role is outside this matrix.

What about ecosystem totals?

The supplied background cites historical snapshots of approximately 45 OSPs, 15 Signing Agents, 16 Onboarding Agents, and 13 Vetting Agents. These figures have no dated source attached in the supplied material and are not verified current totals. Matrix role counts describe only these 17 rows, including Wisp’s in-process applications, not the full ecosystem or the number of authorized partners.

Sources & next steps

The official BCID pages support the role definitions and application path, not the company-by-company assignments above. Existing provider row notes are supplied summaries of public announcements, company sites, press releases, and secondary reporting; no individual source URLs were supplied. The Wisp row and use-case section were added from the supplied October 23, 2026 application update.

Official role definitions ↗Partner application ↗Contact BCID ↗Email BCID

For an authoritative, current roster, contact BCID directly or ask a known partner such as TransNexus or Numeracle which authorized parties they work with. Authorization requires the relevant BCID/CTIA agreements after application and review, per the supplied background.