When you give an AI agent a phone number, you're giving it a human-era identity.
Phone number identity is rooted in physical possession. You have a number because you have a SIM card. You have a SIM card because you have a device. You have a device because you're a human in a location.
An AI agent has none of these properties. It's a software process that can be instantiated, cloned, migrated, and terminated. It doesn't possess anything. Physical possession as an identity anchor is fundamentally wrong for a non-physical entity.
What's actually wrong with phone numbers for agents
The practical consequences of phone-number-based agent identity:
Possession is not proof of authorization. If an agent's number is compromised — stolen credentials, a misconfigured webhook — an attacker can impersonate the agent. There's no cryptographic way for a recipient to verify that the call actually came from the authorized agent, rather than something that obtained the agent's Twilio credentials.
Identity dies with the number. When a phone number burns its reputation and gets rotated, the agent's identity is lost. All context attached to that number — conversation history, recipient relationships, trust signals — is gone. The new number starts from zero.
A number says nothing about the agent. When recipient +1-415-555-9876 receives a call from +1-415-555-1234, they know: this call came from this number. They don't know if it's an agent or a human, what organization it represents, what it's been authorized to do, or whether appropriate consent was obtained. A phone number carries no semantics beyond its digits.
Multiple channel identities. An agent that calls from +1-415-555-1234, sends SMS from a different number, sends email from [email protected], and sends WhatsApp from a third number is four different identities. A contact who texted one number doesn't know that a call from a different number is the same agent.
What cryptographic identity looks like
A cryptographic identity for an agent is rooted in a public/private key pair rather than a physical possession:
{
"acn": "acn://getdial.ai/yourco/sales-agent-prod",
"public_key": "ed25519:abc123...",
"owner": "did:web:yourco.com"
}Verification is a standard cryptographic operation. Any ACES-compliant system can resolve the ACN, fetch the public key, and verify the signature in under 50ms. No carrier involvement. No STIR/SHAKEN dependency. Pure cryptographic proof.
Persistence across infrastructure events
A cryptographic identity persists across events that would destroy a phone number identity:
Agent migration: Move the agent from one cloud provider to another. The ACN stays the same. The key pair moves with it. Identity is preserved.
Number rotation: The underlying phone numbers in the ACN's channel pool rotate for reputation management. The agent's identity — the ACN — stays the same. A contact who texted the old number gets their reply from the same ACN.
Agent version updates: Deploy a new version of the agent. The new version uses the same ACN. Session context carries over. Identity is preserved.
Multi-instance scaling: Ten instances of the agent run simultaneously. All use the same ACN, all sign messages with the same key pair. To the recipient, it's one agent — because it is one agent, just scaled.
The trust chain
Cryptographic identity enables a complete trust chain:
1. Agent claims identity: "I am acn://getdial.ai/yourco/sales-agent-prod"
2. Agent signs message: Signature is included in the communication envelope
3. Recipient resolves ACN: Fetches public key from registry
4. Recipient verifies signature: Cryptographic proof that message came from the claimed ACN
5. Recipient checks policy: ACN record includes entity type, owner, consent model, disclosure requirements
At step 5, the recipient has everything they need to understand what they're communicating with: an AI agent, owned by yourco.com, operating under TCPA express written consent, required to disclose agent identity at the start of every interaction.
This trust chain is not possible with phone number identity. A phone number carries steps 1 and 2 at most — and even that is only as reliable as STIR/SHAKEN attestation, which doesn't extend to the application layer.
The identity model for the agentic era
Phone numbers made sense as identity anchors when identity was tied to physical presence. SIM cards are the right identity primitive for entities that exist in physical space.
AI agents don't exist in physical space. They exist in key pairs. The identity primitive that matches their nature is cryptographic — persistent, portable, verifiable, and not dependent on any physical possession.
That's what ACNs are. Not a better phone number. A different kind of identity, designed for a different kind of entity.