How it works
- You dial a number (e.g.
+15125550147) - The system extracts the area code from the E.164 format (
512) - It searches your provisioned phone numbers for one with a matching area code
- If found, that number is used as the caller ID for this call
- If no exact match, your manually selected caller ID is used as fallback
useCallerIdSelection and runs automatically whenever the selected contact changes.
Enabling local presence
On the home screen: check the Prefer local presence calling checkbox below the caller ID dropdown. In settings: go to Settings → Dialer and toggle Enable local presence. The settings page describes it as: “Automatically select the closest matching caller ID.” When enabled, the caller ID dropdown still shows your selected number, but the system overrides it at dial time with the best local match.Preview tool
The settings page includes a Preview Caller ID tool:- Go to Settings → Dialer
- Scroll to the Local Presence section
- Enter a phone number in the preview field
- Click Preview
- The system shows which caller ID would be selected, and whether it’s an exact area code match
GET /v1/local-presence/preview?phoneNumber=X on the backend.
Requirements
- Multiple phone numbers provisioned in your Twilio account with different area codes
- The more area codes you cover, the better your matching rate
If you only have one phone number, local presence has nothing to match against. It will always use your single number.
Best practices
| Practice | Why |
|---|---|
| Cover your target markets | If you call into Texas, provision numbers with 214, 512, 713, 817, 210 area codes |
| Don’t over-provision | Twilio charges per number per month. Cover your top 10-15 area codes, not every code in the country |
| Monitor answer rates | Compare answer rates with and without local presence in your analytics dashboard |
| Stay compliant | Local presence is legal in the US — Consuelo only uses numbers you actually own, not spoofed numbers |
Local presence + parallel dialing
When parallel dialing is active with local presence enabled, each call in the batch can use a different caller ID based on the recipient’s area code. Contact A in Austin sees a512 number, Contact B in Houston sees a 713 number — all in the same batch.
Next steps
- Configure Caller IDs — provision numbers for local presence coverage
- Caller ID — manage your outbound numbers