Local presence dialing: does it still work, and is it legal?

Local presence is one of the few outbound tactics with an effect large enough that nobody argues about whether it exists. People answer numbers that look local. What has changed is that the naive implementation now actively backfires, and the difference between the two versions is entirely about who owns the number.

Why it works at all

A person deciding whether to answer an unknown number has about two seconds and three pieces of information: the digits, whatever name the network attached, and any label the carrier applied. A familiar area code is a weak but real signal that the call might be a school, a clinic, a neighbour, or a local business, categories worth interrupting yourself for.

An out-of-state number carries the opposite signal. Combined with no caller-ID name, it reads as exactly what most such calls are.

The shared-pool trap

Most products that advertise local presence implement it by drawing from a pool of numbers shared across all their customers. You dial a Denver prospect and the system presents a Denver number. So does everyone else on the platform, from the same pool.

Three things follow, and they compound:

1. You inherit strangers' reputation. The pool accumulates the complaints and traffic patterns of every campaign on it. A number that arrives at your account already labelled performs worse than a plain out-of-state number would have.
2. Callbacks go nowhere. A prospect who rings the number back does not reach you. On a warm list this is the single most expensive failure in outbound: a callback is the highest-intent event you can generate, and the pool throws it away.
3. You cannot earn Attestation A. STIR/SHAKEN attestation at the highest level requires the originating provider to confirm your right to use the number. It cannot do that for a number shared with dozens of other customers, so your calls are signed lower and scored accordingly.

Put together: the shared pool gives you the area code, then removes the two things that make a local number actually work.

Where the legal line sits

The Truth in Caller ID Act prohibits transmitting misleading or inaccurate caller ID with intent to defraud, cause harm, or wrongfully obtain anything of value. Intent is the hinge, and the practical test is refreshingly simple.

If a returned call reaches a real person on your team, you are on solid ground. If it does not, you have a problem that is both regulatory and commercial.

Doing it properly

When not to bother

• You sell nationally to enterprise. A recognisable head-office number and a registered name beat a spoofed-feeling local one for buyers who expect a national vendor.
• Your list is warm. People expecting your call answer it regardless. Spend the effort on getting the callback path right instead.
• You cannot service the market. A local number in a city you have no presence in raises a question on the call you would rather not answer.
• Your volume is small. Below a few hundred dials a week, per-number reputation is barely a factor and the operational overhead outweighs the lift.

The summary

Local presence still works, and the mechanism has not changed: a familiar number is more likely to be answered. What has changed is that carriers now score numbers, so a local number with a bad score is worse than an honest out-of-state one.

Own the numbers, name them, cap them, and make callbacks land. Do that and local presence is a durable advantage. Rent them from a pool and you are buying the appearance of the tactic without the substance.

How much lift to actually expect

Vendors quote large multiples for local presence. Treat any specific figure with suspicion, including favourable ones, because the effect size depends almost entirely on what you are comparing against.

The honest framing is that local presence is a multiplier on an already-healthy setup, not a rescue for an unhealthy one. Teams that add local numbers to a labelled, unregistered pool and see no improvement have not disproved the tactic; they have measured two problems interacting.

Measure it properly if it matters to you: run the same list, same script, same hours, split between a local number and your existing one, for long enough to clear normal daily variance. A week of data on a few hundred dials tells you more than any vendor benchmark, because it is measured on your list.

The callback path is the part people skip

It is worth stating separately because it is the most commonly neglected half of the setup. A local number lifts answer rates on the outbound call. What it does over the following days is arguably more valuable: people call back.

A prospect who missed your call, saw a local number, and rang it back is the highest-intent inbound event an outbound team generates. They are self-identifying as interested, at a moment of their choosing, with no cold-open to get through.

• Route callbacks to a queue, not to a single rep. The rep who dialled may be on another call; the caller will not try twice.
• Attach the campaign context. Whoever answers should see who this is and what they were called about, or the advantage is wasted in the first ten seconds.
• Answer inside business hours, every time. A local number that rings out teaches the market that the number is not real.
• Track callbacks as a distinct metric. They convert far better than outbound connects, and teams that do not measure them separately conclude, wrongly, that the numbers are not working.