A local presence dialer with numbers you actually own

Local presence: what it does for your team

A familiar number on screen

People are more likely to pick up a call from their own area code than from an unknown number across the country. That matters most for teams that call one region, such as real estate agents working their own market or commercial brokers covering one submarket.

Callbacks that reach you

Because the caller ID is a real number in your Twilio account, a lead who calls back rings your team in the Dialer instead of a dead end (inbound calls).

No spoofing

Rapidialer never shows a number you do not own. It chooses among the numbers you bought or ported into Twilio.

Local presence, step by step

1. Buy numbers where your leads are

   Get local numbers in your most-called area codes in Twilio, then sync them into Rapidialer.

2. Turn on local presence

   An owner or admin enables it in Dialing settings. Reps then see an Auto · local number caller ID option.

3. Rapidialer picks the number per call

   For each call it uses your number that shares the lead’s area code. Without a match, it falls back to the rep’s assigned line, then your default caller ID.

What it does not do

Plain limits, so you can decide before you sign up.

• For US and Canadian numbers the match is the exact area code; there is no fallback to a nearby area code or the same state.
• Rapidialer does not buy numbers for you and cannot remove a carrier spam label; it can only warn about numbers that look labeled and route rotated calls around them.
• The Chrome extension always uses the caller ID the rep picks, so automatic local presence applies in the web Dialer only.

Only numbers you own and answer

Rapidialer shows only numbers bought or ported into your Twilio account, never a number you do not control, and every one can take a callback. It can’t use Twilio Verified Caller IDs, because it syncs only the account’s own phone numbers. Whether local presence dialing is lawful for your calls is covered in the glossary entry; this page sticks to setup.

Twilio signs outbound calls with STIR/SHAKEN, and registering your business in Twilio’s Trust Hub lets your calls carry the highest attestation level (Twilio’s SHAKEN/STIR guide).

Does local presence calling still work with spam labels?

It works when the local number itself is clean. Carriers label numbers by how they are used, so a matching area code on a number already marked Spam Likely gets declined like any other. If your numbers start showing as spam, read why Twilio calls show as Spam Likely for the fixes.

In Rapidialer, the practical levers are volume per number and registration. Give each rep a regular line so unmatched calls spread across several numbers, buy local numbers only where your calls cluster, and register each one in Trust Hub and for caller ID name. Owners and admins can open Caller ID health under Analytics, which lists each number’s 30-day calls and answer rate and flags one whose answer rate over the last week falls under half the team’s, or under 5%, after at least 20 calls.

Which area codes should you buy numbers for?

Buy numbers for the area codes that make up most of your dials, and let everything else fall back to each rep’s line. Export your lists, count phone numbers by area code, and buy local numbers for the codes that make up most of your calls. Review the split each quarter; a handful of local presence numbers usually covers most of a regional list.

Turn on local presence in five steps

Setup takes a few minutes once the numbers exist in Twilio. You need an owner or admin login for steps two to four.

• Buy local numbers in Twilio for the area codes you call most.
• In Rapidialer, open Telephony in Settings and press Import from provider to sync them, or add one with Add number. Use Set default on the number that should cover every unmatched call.
• On the Team page, use Change outbound line to give each rep their regular line.
• Open Dialing in Settings, go to the Caller ID & hours tab and switch on Local presence. It applies to every agent in your organization.
• Reps leave the caller ID menu in the Dialer on Auto · local number.

How does Rapidialer choose the caller ID?

Rapidialer picks the first number that fits from a fixed order: a manual pick, a local match, a rotated number if rotation is on, the rep’s line, then your default. Each call works down this list and stops at the first number it finds:

• A line the rep picks by hand in the caller ID menu. Local presence applies only while Auto · local number is selected.
• Your number that shares the lead’s area code. If you own several in that area code, the one that shares the most leading digits with the lead’s number wins, so a number in the same exchange beats one that only shares the area code.
• Outside North America, your number with the longest shared prefix, which must cover at least three digits counting the country code.
• With Rotate caller IDs on, your number used least in the past 24 hours, skipping any that Caller ID health flags as likely spam-labeled (unless every number is flagged).
• The rep’s assigned line, then your default number.

Example: a Texas team with two local numbers

Say you own one 512 number for Austin and one 214 number for Dallas, and your rep’s assigned line is the Austin number. A lead in 214 sees the Dallas number. A lead in Houston’s 713 area code has no match, so the call goes out on the rep’s Austin line. Two numbers cost $2.30 a month at Twilio’s $1.15 rate for a US local number (Twilio voice pricing).

When the Dallas lead calls back, the call rings whoever is assigned the Dallas number. If nobody is, it rings the whole team at once, and if the assigned rep misses it, the rest of the team rings next. Teams that share local numbers across reps should decide who answers those callbacks. Power Dial uses the same rules for every call it places.

Why is a call not showing a local number?

Most often the rep picked a line by hand, or you own no number in that area code. Check these in order:

• The Dialer’s caller ID menu shows a specific number instead of Auto · local number. A manual pick always wins.
• Local presence is off on the Caller ID & hours tab. Agents cannot see that tab, so ask an owner or admin.
• No synced number shares the lead’s area code. A number bought in Twilio appears only after Import from provider on the Telephony page.
• The call was placed from the Chrome extension, which uses the rep’s chosen caller ID every time.
• The rep hears “No outbound phone number is configured. Please contact your administrator.”: there is no number to fall back to, so add one on the Telephony page and use Set default.

When is local presence not worth it?

Local presence pays off when your calls cluster in a few area codes. A national list spread over 200 area codes would need a number for each, at $1.15 a month apiece, plus a person to answer the callbacks and a CNAM registration for every one. For that pattern, one well-registered number per rep is simpler.

It also does nothing for numbers that already carry a spam label. A flag in Caller ID health is a warning drawn from answer rates, not a carrier lookup, so register each number through Twilio’s STIR/SHAKEN setup and Trust Hub first and test a flagged number from a phone you control.

Features that work alongside it

• Power DialSequential power dialing: the next contact is dialed after each wrap-up and a five-second countdown.
• Inbound callsCallbacks to your Twilio numbers ring the assigned rep in the browser, then the team.
• Calling hoursPer-list calling windows checked in each contact’s own time zone.

Local presence: questions and answers