Local presence caller ID in HighLevel: how it picks a number and how many to buy

How HighLevel picks the number

For every call, HighLevel looks for the closest match it owns, in this order, and uses the first one it finds.

1. A number matching the contact's ZIP or postal code.
2. A number in the contact's area code.
3. A number in an overlay area code covering the same place.
4. The nearest number by distance.
5. A number in the same region.
6. The sub-account's default number.

Details of the matching that matter

Location matching covers numbers in the US, Canada, the UK and Australia. It works from the Web Dialer, the HighLevel mobile app and desk phones, so it applies whichever one a rep dials from.

A contact you call again sees the same number. HighLevel keeps the caller ID it picked for repeat attempts, so the contact sees one number from you rather than a new one on every attempt.

Older write-ups describe a three-step version that starts at area code. HighLevel's own article, updated in September 2026, starts at postal code and lists the six steps above. Go by that, and check the current screen, because HighLevel has changed this before.

Buying local numbers doesn't turn local presence on. The setting does.

Turning local presence on

The setting lives at sub-account level, so an agency running several sub-accounts switches it on in each one that dials.

1. Go to Settings, then Phone System, then Voice, then Other Settings.
2. Open Outbound calls and configure Local presence dialing.
3. Save, then place a test call to a phone with a known area code and check the number that shows up.

Keeping some numbers out of the rotation

You may not want every number in the pick. A main office line that customers know, or a number printed on a mailer, is better kept for its own job. HighLevel lets you reserve up to 50 numbers from automatic selection. A reserved number can still be chosen by hand for a call.

That 50 is a cap on reservations, not on how many numbers the sub-account can hold. HighLevel's article doesn't yet spell out every click for reserving a number, so follow the controls your screen shows rather than a list from elsewhere.

Verified Caller IDs and numbers on your own Twilio account can be part of local presence too, if that's how your phone setup runs.

How many numbers to buy

There is no right count that fits every account. Size the list against where your contacts actually are, and let the fallback steps cover the rest.

1. Export the contacts you plan to call and count them by area code, and by ZIP or postal code if you have it.
2. Buy numbers for the places with the most contacts first.
3. Leave thinly covered places to the overlay, distance and region steps.
4. After the first run of calls, look at which contacts went out on the default number and decide whether that place needs its own number.

When calls keep showing the default number

HighLevel falls back to the default when a contact has no usable location data or when no number you own matches anything about them. Before buying more numbers, check the data: a contact with no postal code on file leaves the matcher only the phone number to go on.

Then check the setup. Is Local presence dialing switched on in this sub-account? Is the number you expected reserved? Is the call going out from the sub-account that owns the local numbers?