Automatic Number Identification (ANI)
Automatic Number Identification (ANI) in Salesforce CTI (Computer-Telephony Integration) is the telephony feature that identifies the phone number of an incoming caller.
Definition
Automatic Number Identification (ANI) in Salesforce CTI (Computer-Telephony Integration) is the telephony feature that identifies the phone number of an incoming caller. Within Salesforce, ANI data is used to perform screen pops, matching the caller's phone number to existing Contact, Account, or Lead records so the agent sees the caller's information before answering.
In plain English
“Automatic Number Identification, or ANI, is the phone system feature that tells Salesforce the phone number of whoever is calling. Once Salesforce knows the number, it can look up the customer's record and show it to the agent before they even pick up the call.”
Worked example
When a customer at Pinemoor Capital calls the support line, the telephony system passes the caller's number - Automatic Number Identification (ANI) data - to Salesforce. The CTI integration matches the ANI against Contact records and pops the matching Account on the agent's screen before they answer. The agent picks up with full context: "Hello Mr. Patel, how can I help with your premium account?" ANI is the underpinning of every screen-pop integration; without it, agents would answer cold and ask for the customer's information manually.
Why Automatic Number Identification (ANI) matters
ANI is a telecom feature that provides the phone number of the originating caller on an incoming call, and in Salesforce CTI integrations it's the piece of data that drives screen pops. When a call arrives at a Salesforce-integrated softphone (Open CTI, Service Cloud Voice, or a CTI adapter), the system takes the ANI, searches Salesforce for a Contact, Account, or Lead with a matching phone number, and displays the matched record to the agent before they answer the call.
The quality of ANI-based screen pops depends on two things: clean phone number data in Salesforce (formatting matters; matching '+14155551234' to '(415) 555-1234' requires normalization) and intelligent matching logic for cases where multiple records share a phone number (like a shared company mainline). Well-configured ANI matching saves agents meaningful time on every call and dramatically improves the customer experience because the agent already knows who is calling when the conversation begins.
How organizations use Automatic Number Identification (ANI)
Relies on ANI matching to pop the right Contact record on every inbound call. Their Knowledge base is 90% accurate, and agents begin conversations with full context about the caller's recent Cases and Account history.
Built a custom matching rule that uses ANI to find the Account for a shared company mainline, then presents a list of Contacts at that Account for the agent to pick from. Raw ANI alone wasn't enough because multiple people share the main number.
Normalized all phone numbers in their org to E.164 format as part of an ANI-matching project. The normalization dramatically improved match rates from 70% to 95% because caller numbers came in via ANI in E.164 format.
Test your knowledge
Q1. What does ANI provide?
Q2. What does Salesforce do with ANI data?
Q3. Why does phone number formatting matter for ANI matching?
Discussion
Loading discussion…