What Does the [V] on Your Caller ID Mean?

A client called one morning to report that every screen in the office had started showing a bracketed capital V in front of the caller’s name. Nobody had touched the system. The question, reasonably enough, was what did you people do?

Nothing. Their upstream carrier had turned on verification display and the mark propagated to every handset on the account. This is the answer we now send when that ticket arrives, which is often enough that it deserved writing down.

The short answer

The [V] means the caller’s number was cryptographically signed by the carrier that originated the call, and your carrier checked that signature and found it valid. It is a trust upgrade, not a fault. Nothing broke, nothing needs fixing, and the calls themselves are unchanged. Your provider is simply telling you something it used to keep to itself.

The plumbing, in ninety seconds

For most of the history of the phone network, the number shown on an incoming call was an assertion rather than a fact: whoever placed the call told the network what to display and the network passed it along unchecked. That is the design decision the robocall industry was built on.

The fix is STIR/SHAKEN, which US voice providers were required by the FCC to implement in their IP networks by June 30, 2021 under the TRACED Act. It works like a wax seal. The originating provider signs the call, attaching a token that says this number really was handed to this call by us, and the terminating provider checks that signature against the certificate it was signed with before delivering the call.

Two pieces of information ride along with that, and conflating them causes most of the confusion we see. Attestation is the originating carrier’s claim about how well it knows the caller: A (full) means it knows the customer and confirmed they are entitled to that number, B (partial) means it knows the customer but not the number, and C (gateway) means it only knows where the call entered its network. Verification status is the receiving end’s report on whether the signature survived the trip: passed, failed, or not attempted.

The two do not move together: a top-grade call fails verification if its certificate expired en route, and a bottom-grade call passes happily as long as the signature is sound. Attestation is how much the originator vouches; verification is whether the vouching arrived intact. Carriers generally reserve the visible mark for calls that clear both bars.

Why it shows up as [V] specifically

Because the caller name field is very old and very small. CNAM records descend from the legacy line information databases and are capped at fifteen printable characters. There is nowhere in that field for a badge and no standard place on a desk phone screen to draw one, so carriers do the pragmatic thing: prepend the literal text [V] and truncate the rest to fit.

The mark is inserted upstream, before the call reaches your phone system. Pull a packet capture and the [V] is already sitting in the name field of the incoming call setup. The PBX displays what it is handed; it did not add the mark and cannot decline it.

That also explains the one legitimate complaint: three characters out of fifteen is a fifth of your name gone, and a business already at the edge of that limit notices. If the truncation is causing real trouble we can rewrite inbound caller ID at the trunk. On 3CX V20 that lives in the Admin Console under Voice & Chat, in the trunk’s Options, under “Reformat incoming or outgoing caller ID”, which accepts regular expressions and applies rules top down, first match wins. The inbound rules section elsewhere in the console matches on wildcards only, so the trunk is where this work belongs. We usually talk clients out of stripping it, but it is your display and it is a five-minute change.

What the mark does not promise

Verified does not mean safe. The FCC is direct about the limit: the framework helps identify when a displayed number may be spoofed, but it does not tell you who is calling. Verification proves the number was not faked and says nothing about the intentions of whoever dialled it. A telemarketer with a legitimate carrier relationship and legitimately assigned numbers gets a fully verified call and a [V] on your screen. What the framework really buys is traceability: when a caller misbehaves, the trail now leads somewhere. Modest on any single call, large for the network.

Verified also does not change the call. We had a receptionist convinced she could not transfer [V] calls. The transfer trouble was real, but the mark had nothing to do with it; the cause was elsewhere in the setup and we fixed it separately. Half of support work is separating the thing that changed from the thing that broke. Verification does not touch routing, transfers, hold, recording, or queues. It is text.

The rest of the label zoo

“Spam Likely” is not attestation. Those labels come from call analytics engines scoring numbers on behaviour: call volume, dialling velocity, rejection rates, the age of the number block, consumer reports. Those scores refresh continuously and are separate from whether a call was signed, so a verified, top-attested call can still be labelled spam if the number has a reputation problem. Authentication answers are you who you say you are. Analytics answers are you a nuisance.

Wrong or stale names are a CNAM problem. A caller showing up as a business that closed years ago, or as a generic entry like “Public Service”, is an old record for that number in a caller name database, or a cached copy of one. Numbers get reassigned and the records lag, sometimes by years; cache lifetimes across the industry are inconsistent enough that a correction can take days to propagate and may never reach some carriers. None of it is fixable from your phone system, because the record does not live there.

No mark at all is not a red flag. Plenty of legitimate calls arrive unmarked, because the originating network is not IP end to end, or the call crossed a segment that did not carry the signature, or the terminating carrier does not surface the result to the handset.

On the systems we manage we leave verification display on, and the briefing we give front desks is deliberately short, because a long one is not remembered: the [V] means the number is real, it does not mean the caller is honest, and read nothing into it being absent.

The other direction is the one worth worrying about

Everything above is about calls coming in, where the labels are mostly cosmetic. The side that costs money is going out: your calls landing as “Spam Likely”, showing the wrong company name, or showing no name at all. That is answered calls you never get, and unlike the [V], it is something we can work on directly.

If that sounds familiar, start with our write-ups on business calls being marked as spam and on branded calling, or the know-your-customer and STIR/SHAKEN background for the compliance side. Or skip the reading and email us the number that is displaying wrong: we will tell you what your outbound calls actually look like when they land, and what it takes to fix them.