CRM + SIP Trunk Caller ID: Controlling What Your Prospect Sees

Why Caller ID Is a Conversion Variable

Answer rate on outbound calls correlates directly with how the caller ID renders on the receiving handset. Three factors drive this:

Local vs. foreign number. A call from a local area code or in-country number answers at materially higher rates than a call from an international number. A prospect in Germany receiving a call from a +49 number answers at a different rate than the same prospect receiving a call from a +1 US number. The difference compounds when prospects have call-screening apps or carrier-level spam filtering enabled.

Attestation status. In the US and Canada, STIR/SHAKEN attestation causes the receiving handset to display "Verified Caller" (on supported carriers and handsets) rather than a raw number or "Potential Spam." An A-level attestation means the signing authority verified that the caller is authorized to use the presented number. This is a functional conversion lever.

Number reputation. Numbers accumulate reputation scores with analytics providers — Hiya, TNS, First Orion — based on call behavior patterns. A number that has never been flagged by a consumer or produced a spam complaint starts with a clean reputation. That reputation degrades if calling behavior is problematic (high call volume with no connected calls, short call durations, consumer reports).

Controlling caller ID means controlling all three of these variables at the provisioning level.

How CRMs Pass Caller ID to a SIP Trunk

When a CRM initiates an outbound call through a SIP trunk, it includes the caller ID in the SIP INVITE's From and P-Asserted-Identity headers. The trunk reads these headers and does one of two things:

Validates and passes through. If the presented number is provisioned to the account, the trunk accepts it and presents it to the terminating carrier unchanged.

Rejects or substitutes. If the presented number is not provisioned to the account, the trunk either rejects the call or substitutes the account's default caller ID. The behavior depends on the trunk provider's configuration.

This means the CRM's outbound caller ID field must contain a number that is provisioned to the UnlimCall account. It cannot be a number from a different provider, a number not yet provisioned, or a malformed string.

On-Demand Provisioning Across 33 Markets

UnlimCall provisions caller IDs on demand. There is no inventory pool — no pre-purchased block of numbers to draw from, no waiting for availability. When a team needs a +49 (Germany) DID for an agent calling into German prospects, the provisioning flow is: request the number in the portal, receive a dedicated DID, assign it to the relevant seat credential.

This matters for agencies and teams running multi-country outbound. A team calling into France, Spain, and Italy simultaneously needs three in-country DIDs — one per market — not a single US number trying to pass across three different country networks. The network page documents all 33 live markets.

Per-Agent vs. Per-Campaign Caller ID Assignment

Two common models exist for assigning caller IDs in a CRM-integrated setup:

Per-agent assignment. Each agent's SIP credential is paired with a dedicated DID. Every call that agent makes presents the same number. This is the standard model for teams where individual agents build relationships with specific prospect segments — the prospect sees a consistent number from the same agent over time.

Per-campaign assignment. A campaign in the CRM is assigned a specific DID, and all calls from that campaign present the same number regardless of which agent initiates the call. This is useful for A/B testing caller ID performance — rotating numbers across campaign cohorts to measure answer rate differences.

Both models are supported in the UnlimCall architecture. Per-agent assignment is the default; per-campaign assignment requires configuring the CRM to override the per-user caller ID with the campaign-level DID at the point of call initiation.

STIR/SHAKEN: Scope and Configuration

STIR/SHAKEN attestation is currently relevant for US and Canadian outbound calls. The framework does not apply to other markets. For the 31 additional markets in UnlimCall's network, caller ID transmission follows local CLI rules — typically meaning the presented number must be a valid in-country number to render correctly.

When UnlimCall provisions a US or Canadian DID to an account, that DID is eligible for A-level STIR/SHAKEN attestation on outbound calls. The attestation is applied at the SIP trunk layer. No CRM-side configuration is required.

For outbound teams calling US numbers, A-attestation is not optional if answer rate matters. "Potential Spam" labels applied by analytics engines cut answer rates significantly — the exact percentage varies by market segment and prospect type, but the directional effect is consistent across published research and practitioner data.

The GoHighLevel SIP integration guide covers how attestation passes through the GHL BYOC path specifically.

Number Rotation and Reputation Management

Some outbound teams rotate caller IDs to spread call volume across multiple numbers and avoid reputation degradation on any single number. This is a legitimate strategy when executed correctly.

When done poorly — rapid rotation with no relationship between rotation cadence and call volume — it signals robocall behavior to analytics engines and accelerates reputation problems rather than avoiding them.

The better approach: assign numbers to agents rather than rotating across a pool. Each agent's number builds a reputation that matches their actual calling behavior. If an agent is running clean, professional outbound calls with high connect rates and no consumer reports, that number's reputation reflects it.

For teams that genuinely need rotation — because they are running high-volume outbound and want to distribute load — provision multiple DIDs per agent from the pricing page and rotate at the agent level, not the account level.