Rich Call Data for Outbound Teams: What It Is and How to Deploy It

The Gap Between What You Know and What the Consumer Sees

Your dialer knows exactly who it is calling and why. The consumer sees an unknown number. That information asymmetry is the root cause of declining answer rates across every outbound vertical — collections, insurance, healthcare, B2B sales — and Rich Call Data (RCD) is the infrastructure-layer fix.

RCD is a SHAKEN extension (PASSporT extension type rcd) that embeds structured metadata in the SIP signaling layer: your verified business name, a short call reason string (up to 40 characters), and optionally a logo URL. On supported devices — current Android with Google Phone app, iOS 17+ via CallKit — this data surfaces on the incoming call screen before the recipient taps accept or decline.

How RCD Differs From Standard Branded Calling Enrollment

Standard branded calling through Hiya, First Orion, or TNS requires enrolling your numbers in their databases out-of-band. The number itself carries no structured metadata — the analytics engine does a lookup in its own records when the call arrives.

RCD is inline. The metadata travels with the call in the SIP headers and PASSporT token. This has two practical consequences:

1. The information is current at call time, not dependent on a third-party database being up-to-date
2. You can change the call reason per-campaign without re-enrolling numbers — a re-enrollment appointment campaign reads "appointment reminder" while a sales campaign reads "account update"

The two approaches are complementary, not competitive. Run both.

Carrier and Device Support Landscape

As of mid-2026, RCD display on the consumer handset requires:

• An originating carrier that signs PASSporT tokens with the rcd extension (UnlimCall's SIP trunking does this for US and CA calls)
• A terminating carrier that forwards the PASSporT token rather than stripping it (Verizon and T-Mobile pass it; AT&T rollout is partial by market)
• A receiving device that parses and renders the payload (Google Phone app on Android 12+; iOS CallKit on iOS 17+)

The coverage is not universal, but it is large enough to generate measurable answer-rate lift at scale. A team placing 5,000 calls per day with 60% of those reaching RCD-capable devices and a 15% answer-rate improvement on those calls generates 450 additional conversations per day from the same list and agent headcount.

Connecting RCD to Your Dialer Configuration

RCD metadata is set at the SIP trunk level, typically as custom SIP headers or via the STIR/SHAKEN signing service your carrier operates. When configuring your trunk on UnlimCall:

• Your business name populates the cnam field on the trunk profile
• Call reason strings are passed as campaign-level parameters and injected per-call at origination
• Logo URLs point to a publicly reachable asset hosted on your domain (minimum 512x512 PNG)

For teams using multiple campaigns simultaneously — a mix of appointment setting and proactive account management, for example — per-campaign reason strings prevent a consumer dialing back from reaching a department that has no context for the call.

Measuring RCD Impact Cleanly

Isolating RCD's contribution to answer rate improvement requires controlling for other variables. The cleanest approach:

1. Split a homogenous list (same geography, same lead age, same time of day) 50/50 between trunks with RCD enabled and trunks without
2. Run the split for a minimum of 2,000 calls per arm to get statistical significance
3. Track answer rate, talk time, and positive outcome rate (appointment booked, payment arranged, etc.) separately

Teams running A/B testing on caller ID strategy should extend their testing framework to cover RCD as a separate variable from number type and rotation cadence.

RCD for International Outbound

RCD as a standard is US/CA-centric today. Outside North America, the equivalent mechanism varies by country. In Germany and the Netherlands, verified business name display through the carrier's own CNAM database is available for fixed-line origination. In the UK, Ofcom's SCITT framework (similar in intent to STIR/SHAKEN) is progressing toward signed delivery.

UnlimCall provisions caller IDs on demand across 33 live markets. For markets outside US/CA, the deliverability strategy relies more heavily on local number presence and clean call behavior than on signed metadata, because the infrastructure to carry and display RCD is not yet in place end-to-end. That will change, and the architecture to support it is already in the origination stack.

What RCD Cannot Fix

RCD is an identity layer, not a behavior layer. If your campaign has high abandonment rates, calls after 9 PM local, or a complaint history with analytics engines, RCD will not override those negative signals. Fix campaign hygiene first, then layer identity on top.

The sequence for a new campaign: clean list, compliant calling windows, managed abandonment rate, branded calling enrollment, then RCD. Identity amplifies clean behavior; it does not substitute for it.