STIR/SHAKEN for Call Centers vs. Enterprises: Different Problems

The Enterprise Problem: Protecting Brand Numbers

A large enterprise typically has a small set of externally published telephone numbers — main lines, customer service numbers, sales lines — that appear in marketing materials, on websites, and in customer communications. These numbers have brand equity. Consumers expect calls from them to be legitimate.

For enterprises, STIR/SHAKEN is primarily a defensive problem. Someone is spoofing your published number to run a scam. Consumers answer because they recognize your number. The FCC's STIR/SHAKEN rules exist partly to address this scenario.

The enterprise's STIR/SHAKEN task is ensuring that calls originating from their published numbers are signed at A-level, so terminating carriers can confirm the call is genuinely from that organization. Simultaneously, when someone else spoofs the enterprise's number, the spoofed call will arrive either unsigned or at C-level, creating a signal that allows detection.

Enterprises operating their own SIP infrastructure — a PBX or UC platform connected to SIP trunks — need to ensure their trunk provider supports A-level signing for the specific numbers in their published inventory. They typically do not rotate numbers, do not run high daily call volumes per number, and do not need on-demand caller ID issuance. Their problem is one-time setup: get A-level signing on our permanent numbers, keep it there.

The Call Center Problem: Volume, Velocity, and Behavioral Management

Outbound call centers face a fundamentally different challenge. They may run hundreds or thousands of dials per agent per day. They need caller IDs that match the geographic market being called. They rotate numbers to manage reputation signals. They may operate across dozens of campaigns with different calling profiles.

For call centers, STIR/SHAKEN is not just a setup question. It is an ongoing operations variable that interacts with call velocity, number rotation frequency, caller ID selection strategy, and campaign-level behavioral management.

The key differences:

Number velocity. An enterprise uses the same numbers for months or years. A call center may need fresh numbers for every new campaign, every new geographic market, or every time a number accumulates enough behavioral risk to warrant rotation. This requires a SIP trunking provider that can issue new caller IDs on demand — at A-level attestation — without a provisioning queue measured in days. UnlimCall's on-demand caller ID model is designed specifically for this use case: request a number for a market, get a network-managed DID with A-level signing capability, not a number from a shared pool with recycled history.

Geographic coverage. A national enterprise may need caller IDs for five markets. A call center running campaigns for insurance, home services, or financial products may need caller IDs in 33+ markets simultaneously, each matching the local area code of the prospects being dialed. See UnlimCall's 33-country coverage.

Attestation as an operational metric. Enterprise teams check attestation once, during setup. Call center operations managers need to monitor attestation levels as an ongoing metric — verifying that newly issued numbers are being signed at A-level, checking that numbers that have been rotated are not exhibiting degraded signing, and tracking whether unusual call patterns have generated complaints that affect future signing treatment.

Shared Infrastructure vs. Dedicated Trunks

Many call centers operate on shared SIP infrastructure — trunks that serve multiple customers of the same wholesale provider. This creates an attestation risk that enterprises on dedicated trunks do not face: if other customers on the same shared infrastructure are running high-complaint-rate traffic, carrier reputation scoring may begin to apply scrutiny at the infrastructure level, not just the individual number level.

Enterprises on dedicated SIP trunks do not share infrastructure with external parties. Their signing reputation is entirely a function of their own calling behavior. Call centers need to ask their SIP trunking provider whether their traffic is on shared or dedicated infrastructure, and how customer isolation is handled in the signing and reputation management system.

Regulatory Timeline Differences

Enterprises and call centers face different compliance timelines on STIR/SHAKEN implementation requirements. The FCC's mandate for STIR/SHAKEN implementation was phased, with small providers and non-IP carriers getting extended deadlines. Enterprise customers of legacy PBX systems connected to TDM trunks may still be on infrastructure that cannot sign calls natively.

For call centers operating at scale on modern SIP infrastructure, there is no legitimate reason to be running unsigned or C-level traffic in the US or Canada in 2024. The infrastructure requirement is a SIP trunk with a provider that has completed STIR/SHAKEN certification. The operational requirement is choosing caller IDs from a provider that can issue A-level attestation. These are solvable problems.

Enterprises on legacy TDM PBX infrastructure may have a longer migration path. Their mitigation filing with the RMD covers them during the transition, but terminating carriers are increasingly treating mitigation-only traffic with more scrutiny as the deadline for full implementation recedes into the past.

The Daily Rate Difference: Enterprise vs. Call Center Economics

The economic structure of enterprise vs. call center telephony spending shapes which STIR/SHAKEN issues get prioritized.

Enterprise teams typically buy SIP trunking at flat monthly rates for a set number of channels, with dedicated numbers. Their attestation problem is a setup cost, not a recurring cost. Call centers — especially those that buy flat-rate per-seat capacity at $99 per agent per month on US and Canada — are managing a high-velocity, high-turnover operation where attestation quality is a daily performance variable that directly affects revenue.

For enterprises, STIR/SHAKEN is an IT compliance task. For call centers, it is a revenue operations problem. The tools required are different, the monitoring cadence is different, and the provider relationship requirements are different.