The checkmark next to an incoming call is a signature check between two phone companies — worth understanding, and easy to over-trust.
“Calls With a Checkmark Have Been Verified by the Carrier” — What That Means
“Calls with a checkmark have been verified by the carrier” means the call passed STIR/SHAKEN authentication: the phone company delivering the call confirmed, cryptographically, that it really came from the number displayed on the caller ID. That is the entire claim. The FCC’s call-authentication page describes the check as letting the receiving phone company “verify that a call is in fact from the number displayed on Caller ID” — the number, not the name, and not the caller’s intentions.
A call wearing a checkmark can still be a sales call, a robocall, or a scam placed from a number the scammer legitimately controls. The sentence itself is the explanation some Android phones show in their call details; other carriers and handsets surface the same verification differently, or not at all.
This page covers what the checkmark confirms, what it doesn’t, why it appears inconsistently across phones, and how a business earns verified status on its own outbound calls.
What the Checkmark Actually Confirms
Behind every checkmark is the same mechanism. When a call is placed, the originating provider signs it — attaching a cryptographic signature plus an attestation level that says how strongly it vouches for the caller. The carrier on the receiving end verifies that signature before the phone rings. If the signature checks out, the receiving network knows the displayed number wasn’t spoofed in transit, and some phones mark the call accordingly.
The three attestation levels describe the strength of the vouching: A means the provider verified both the caller and their right to use the number, B means it knows the customer but can’t vouch for that specific number, and C means it only knows which gateway the call came through.
The full mechanics — signing, certificates, coverage data, and what each level does to your deliverability — live on the STIR/SHAKEN explainer, so this page won’t restate them.
One honest caveat about the checkmark specifically: no public Google documentation maps the Android checkmark to a particular attestation level, so the safest reading is the general one — the call arrived signed, and the signature verified. On the regulatory side, one sentence covers it: STIR/SHAKEN has been required in the IP portions of US phone networks since mid-2021, and every voice provider certifies its implementation in the FCC’s Robocall Mitigation Database.
Three Things the Checkmark Does Not Mean
It is not spam-proof. Spam labels are decided by analytics engines — First Orion, Hiya, and TNS score calls for the major US carriers — based mostly on calling behavior, with attestation as one input among many. Verified and unwanted coexist all the time: in TransNexus’s March 2026 data, providers that sign traffic for prolific robocallers attested 89.8% of those calls at the full A level.
The signature and the spam score are separate systems, which also cuts the other way — a legitimate business’s fully attested calls can still pick up “Potential Spam” or “Scam Likely” labels if the calling patterns look wrong. That side of the problem is caller ID reputation management, and it matters more day to day than the checkmark does.
It is not identity vetting. Verification stops at the number. Nobody checked what the business is, whether its name is accurate, or why it’s calling. The FCC’s framing is precise on this point: the receiving carrier verifies the call is from the number displayed — nothing further.
It is not a name display. The caller’s name comes from entirely different plumbing: legacy CNAM databases, which major US wireless carriers generally bypass in favor of their own analytics and app layers, or paid branded-calling programs. A verified call with no name record still shows up as a bare number — checkmark and all.
Why Some Phones Show It and Others Don’t
Two independent reasons, and both are worth knowing before you read anything into a missing checkmark.
First, there is no display standard. The FCC’s call-authentication page describes no standard consumer display for verified calls, and Wikipedia’s STIR/SHAKEN entry notes that a caller ID “might be appended with (verified)” — with display conventions still being discussed among carriers as far back as 2019. Every carrier and phone maker decides independently what a verified call looks like:
| Display | Where it appears | What to know |
|---|---|---|
| Checkmark, with “calls with a checkmark have been verified by the carrier” in call details | Some Android phones | Google publishes no documentation tying the checkmark to a specific attestation level |
| “Caller Verified” | T-Mobile’s historical branding for verified calls | Current T-Mobile pages no longer surface this wording; today’s exact on-screen string varies |
| “(verified)” appended to the caller ID | Some carriers and devices, per Wikipedia’s STIR/SHAKEN entry | No universal Android or iOS convention exists |
| Business name, logo, and call reason | Branded caller ID programs (First Orion, Hiya, TNS, CTIA’s BCID) | A separate paid layer for businesses — related to, but not the same as, the free checkmark |
The display layer keeps shifting, too. Google’s original Verified Calls program — business name, logo, and call reason in the Google Phone app — was fully turned down on January 31, 2023, per a Google notice quoted in partner documentation. April 2026 press reports (Android Headlines) describe a possible new Android-level verified-calls capability running through Google Play Services, but that is press reporting with no Google confirmation as of July 2026.
On the Apple side, Business Caller ID through Apple Business Connect was announced October 16, 2024 with a 2025 target (per 9to5Mac) — that is branded business display, a different thing from the carrier checkmark, and its rollout status wasn’t confirmed on Apple’s public pages as of July 2026.
Second, most calls arrive unsigned. In TransNexus’s March 2026 measurements, only 42.7% of calls reached the terminating network with a STIR/SHAKEN signature at all — 27.8% attested A, 3.5% B, and 7.5% C — largely because authentication is stripped whenever a call crosses an older non-IP network segment. More than half of legitimate calls arrive with nothing to verify, through no fault of the caller. An unmarked call is not evidence of anything.
How a Business Earns the Checkmark on Its Own Calls
You can’t sign your own calls — your originating provider does, and the attestation level it assigns is what the receiving network verifies. Three things move the needle, all covered in depth on the STIR/SHAKEN page:
- A direct provider relationship. Providers assign full A-attestation when they can confidently vouch that you’re authorized to use each calling number — which takes a real relationship: the provider knows who you are and provisioned your numbers. Traffic resold through layers of intermediaries tends to arrive at B, C, or unsigned.
- Clean number ownership. Numbers provisioned in your name, through your provider, with consistent registration are the ones a provider can stand behind at the A level.
- Behavior that matches a business people want to hear from. A signed call still gets scored. Steady volume, real conversations, and honored do-not-call requests do more for how your calls display than the signature does.
This is one of the reasons Enzo provisions and manages every caller ID through its own carrier rather than accepting bring-your-own numbers: 35 numbers per seat on Starter and 100 on Standard, owned and provisioned upstream where the signing happens, with reputation monitored and numbers rotated or swapped when health dips. And because Enzo places live agent-driven calls only — no prerecorded voice — the traffic its carrier signs looks like what it is: humans calling humans.
Beyond the Checkmark: Verified Calls With a Name and Logo
The checkmark is the free, consumer-facing edge of a bigger verification stack. The same signed STIR/SHAKEN token can carry Rich Call Data — display name, logo, and call reason — which is how paid branded-calling programs deliver a vetted business identity to the incoming call screen.
CTIA’s Branded Calling ID describes itself as an industry-led ecosystem for exactly this, and First Orion, Hiya, and TNS all sell branded display built on the same rails (named as examples of the category, not endorsements). For an outbound team deciding whether that spend makes sense, the trade-offs live on the branded caller ID page.
The Bottom Line
The checkmark means one narrow, useful thing: the carrier verified the call came from the number displayed. It doesn’t vouch for the caller, block spam labels, or show your name — and its absence often just means the call crossed a network segment that dropped the signature.
If you make outbound calls for a living, the practical order of operations is: get your numbers provisioned by a provider that actually knows you, then spend your energy on the calling behavior and number health that decide how your calls really show up.
See how Enzo handles provisioning, monitoring, and rotation as part of the product — book a free discovery call. Twenty minutes, and if Enzo isn’t the right fit, we’ll tell you.
Carrier, FCC, TransNexus, and vendor details as of July 2026; company names are trademarks of their owners. Display behavior varies by carrier and device — verify on current handsets.