All posts
Voice Cloning Made Caller ID Meaningless. What Replaces It?
SecurityBy Dial Engineering·5 min read·October 8, 2026·0

Voice Cloning Made Caller ID Meaningless. What Replaces It?

For a century, a familiar voice on the line was proof enough. Synthetic voices ended that, and caller ID never really worked as proof anyway. Here is what has to carry trust instead, and what you can do about it today.


Imagine a finance manager named Dana. Her phone rings. The screen shows her CEO's number, and the voice on the line is unmistakably his: the slightly rushed cadence, the habit of starting sentences with "Look,". He needs a wire sent before close of business, and he asks her not to loop anyone in.

Every signal Dana has ever used to decide "is this really him?" just said yes. Every one of them can now be faked.

This is not a prediction. It is the logical end of two trends that have been running for years: caller ID that anyone can spoof, and synthetic voices that need only a short audio sample to imitate a person. Put them together and the oldest trust mechanism in telephony, "I know that voice," stops working.


Caller ID was never an identity system

Caller ID displays a number. That is all it was ever designed to do. For decades, the number shown to the recipient was whatever the originating network said it was, and the network mostly believed whoever was calling in. Spoofing was trivial enough that the United States passed the Truth in Caller ID Act in 2009 to make malicious spoofing illegal. Laws do not stop people who already ignore laws.

The industry's technical answer was STIR/SHAKEN, which major US carriers were required to deploy in 2021. It signs calls so the terminating carrier can see how confident the originating carrier is about the caller. The whitepaper behind Dial's thinking describes the three attestation grades plainly:

  • A (Full): the carrier knows the customer and that they are entitled to use the number.
  • B (Partial): the carrier knows the customer but not that they own the number.
  • C (Gateway): the call passed through and the origin is unverified.
  • That is real progress against number spoofing. But notice what it attests: that a call legitimately entered the network through a given carrier on behalf of a given customer. It says nothing about who is speaking, whether the speaker is a person or a model, or whether anyone authorized this specific conversation. A fully attested call can still carry a cloned voice. STIR/SHAKEN answers "did this call come from where it claims?" The question Dana needs answered is different: "is this the person I think it is, and is he really asking for this?"


    The voice was never proof either

    Humans are decent at recognizing voices in good conditions and poor at it in the conditions that matter: a bad connection, a stressful moment, an urgent request. Fraudsters have always known this, which is why "grandparent scams" and impersonation of executives existed long before synthetic speech. What cloning changes is the cost curve. Impersonation used to require a skilled mimic and a lot of luck. Now it requires a sample and a tool.

    So we have to stop treating the sound of a voice as a credential. A voice is an input, like a face in a photo or a signature on a scan. It can inform judgment. It cannot carry authentication.

    This applies in both directions. People will be fooled by synthetic voices. And legitimate AI agents will increasingly call people, which means recipients need a way to tell "a company's honest agent that disclosed itself" from "an impersonator wearing a familiar voice."


    What has to carry trust instead

    If neither the number nor the voice can be trusted alone, trust has to move to something that can be checked. Three layers do the work.

    1. Carrier attestation, preserved. STIR/SHAKEN stays. It makes bulk number spoofing harder and gives carriers a signal. It is a floor, not a ceiling.

    2. Cryptographic identity at the application layer. The ACES whitepaper proposes that every agent has a key pair and a registry record. Messages are signed, and a counterparty verifies the signature against the registry, so proof of identity does not depend on carrier-level attestation alone. The record also carries an explicit entity type, so "this is an agent" is machine-readable rather than something you infer from how it sounds.

    3. Policy and disclosure. The same paper describes mandatory disclosure: when it is required, the agent's first turn names itself as an AI and says who it is calling for before anything else. This does not stop criminals, who ignore rules. It does something subtler: it makes honest behavior the standard, so that a call which does not follow the standard is itself a signal.

    Here is the key shift. In the old model the recipient had to decide, in real time, from vibes. In the new model the recipient's phone, the receiving system, or an assistant acting for the recipient can check a signature in the background and surface the result. The human gets a verdict, not a puzzle.


    What recipients can do right now

    Cryptographic identity will take time to spread. Until then, use habits that do not depend on trusting the sound of anything.

  • Hang up and call back on a known number. The single most effective defense. Use a number you already had, not one the caller gave you.
  • Agree on a shared secret with people who can ask for money or access. A family word, a team phrase. Low tech, high value.
  • Treat urgency plus secrecy as the alarm. "Do it now and tell no one" is the shape of nearly every impersonation scam.
  • Move high-stakes requests to a second channel. If the CEO calls about a wire, confirm over a channel that is verified differently: a signed email, a message in the company chat.
  • Be suspicious of what you cannot verify, not of what sounds wrong. The cloned voice will sound right. That is the whole point.

  • What builders can do

    If you run agents that call people, you are part of the answer or part of the problem. Practically:

  • Disclose first. Say you are an AI and who you represent, before any other content.
  • Give your agent its own identity rather than borrowing a human's number and voice.
  • Sign what you send wherever your stack lets you, so a verifier has something to check.
  • Never clone a real person's voice without their explicit consent, and never present a synthetic voice as a specific real individual.
  • Offer a verification path: a way for the recipient to confirm the call is genuine, such as a callback to a published number.
  • This is the kind of thing Dial handles at the infrastructure layer: agent identity, signed messages, and disclosure enforced before a call goes out, so individual builders do not each reinvent it.


    The takeaway

    Caller ID was a label, and a voice was a feeling. Neither was ever a credential, and synthetic speech has simply made that impossible to ignore. What replaces them is boring and good: attestation from carriers, cryptographic identity from the application layer, and disclosure as a default. Until that is everywhere, hang up and call back.

    Dana, by the way, did exactly that. The real CEO was in a meeting and had no idea what she was talking about.

    Did you enjoy this post?

    0 claps