Skip to main content
Local presence automatically selects a caller ID matching or close to the recipient’s area code, increasing pick-up rates by 20-40%.

How It Works

When you enable local presence:
  1. The CLI extracts the recipient’s area code
  2. It searches your Twilio numbers for an exact match
  3. If no exact match, it finds the closest geographic number
  4. If no numbers are close, it falls back to your primary number
Recipient: +1 415-555-1234 (San Francisco)
Your numbers: +1 650-xxx-xxxx (Palo Alto), +1 212-xxx-xxxx (NYC), +1 555-xxx-xxxx (Primary)

→ Selected: +1 650-xxx-xxxx (closest to San Francisco)

Prerequisites

  • Multiple Twilio phone numbers in different area codes
  • Numbers assigned to your Twilio account
  • CLI configured with Twilio credentials

Provision Numbers

Buy Numbers in Target Area Codes

  1. Go to Twilio ConsolePhone NumbersBuy a number
  2. Search by area code for regions you call frequently
  3. Purchase numbers for your key markets
RegionArea Codes
San Francisco Bay Area415, 650, 510
Los Angeles213, 310, 818
New York212, 646, 917
Chicago312, 773
Texas214 (Dallas), 713 (Houston), 512 (Austin)
Florida305 (Miami), 407 (Orlando)
You don’t need every area code. Having 5-10 numbers across major regions provides good coverage.

Enable Local Presence

Via Config

consuelo config set twilio.localPresence true

Per-Call Override

Enable for a single call:
consuelo calls start +15551234567 --local-presence
Disable for a single call (if enabled in config):
consuelo calls start +15551234567 --no-local-presence

Use Local Presence

Basic Usage

consuelo calls start +14155551234 --local-presence
The CLI automatically selects the best caller ID.

With Contact

consuelo calls start contact_abc123 --local-presence
Uses the contact’s phone number area code for matching.

In Queues

Local presence works with queue dialing:
consuelo queue create --name "California Prospects"
consuelo queue add queue_xyz --from-search "region:california"
consuelo queue start queue_xyz --local-presence
Each call in the queue uses local presence.

Verify Local Presence

Check which number was used:
consuelo history get CA1234567890
Look for from field in the output.

Geographic Matching

Exact Match Priority

If you have a number with the exact area code as the recipient, it’s always preferred.

Proximity Fallback

Without an exact match, the CLI calculates geographic distance:
  1. Looks up area code coordinates (lat/long)
  2. Calculates distance using Haversine formula
  3. Selects the closest number within ~100 miles

Fallback to Primary

If no numbers are within range, the primary number (twilio.phoneNumber) is used.

Area Code Database

The CLI includes a built-in database of US area code locations. No configuration needed. For international numbers, local presence still works but may have limited area code coverage.

Best Practices

Coverage Strategy

  • Buy numbers in your top 5-10 calling regions
  • Consider where your prospects are located
  • Update your number pool as you expand to new markets

Quality Over Quantity

  • 5 well-placed numbers > 20 random numbers
  • Focus on regions where you have the most prospects
  • Monitor which numbers get the most use

Track Performance

Compare connect rates with and without local presence:
# Without local presence
consuelo history stats --period week

# With local presence (after a week of use)
consuelo history stats --period week
Industry research shows local presence typically improves connect rates by 20-40%.

Troubleshooting

”No numbers available for local presence”

You need at least 2 numbers (primary + one alternate) for local presence to work.

”Using primary number for all calls”

Your Twilio account may only have one number. Buy additional numbers in different area codes.

”Unexpected area code selected”

The selection algorithm prioritizes:
  1. Exact area code match
  2. Geographic proximity
  3. Primary fallback
Check your available numbers:
consuelo config get twilio.phoneNumber
# Add more numbers via Twilio Console

Next Steps