DocsCall TrackingCollecting ZIP Codes on Calls

Collecting ZIP Codes on Calls

The four ways Lead Distro AI captures a caller's ZIP code on inbound calls, so calls route to the destinations that cover the caller's area: from the caller's number, from the number they dialed, from a keypad prompt, and from data your traffic partner sends ahead of the call.

Last updated:

Call Tracking is in beta and turned on per account. If you don't see Calls in your left sidebar, email support@leaddistro.ai and we'll switch it on for you.

A caller's ZIP code is how Lead Distro AI decides which of your destinations should get the call. Match the ZIP against each destination's area, and only the destinations that cover the caller ring. This page lists every way we can learn a caller's ZIP. You can use one or several at once, and they all end up in the same place: the ZIP on the call, which drives routing and shows up in reports. For how to set the areas each destination covers, see Routing to Local Agents by Territory.


The four ways, at a glance

MethodWhere the ZIP comes fromCaller has to do anything?
From the caller's numberThe phone network's best guess for the calling numberNo
From the number they dialedA region you set on the tracking numberNo
Keypad entryThe caller types their 5 digit ZIPYes
Sent ahead of the callYour traffic partner posts it before they transfer the callNo

1. From the caller's number (automatic)

Every inbound call arrives with an approximate city, state, and ZIP that the phone network attaches to the calling number, at no cost and with nothing for the caller to do. Lead Distro AI reads it on every call and uses it to route. It is a good default, but it is the number's home area, not where the caller is standing, so it can be missing or off for mobile and internet numbers. The next three methods are how you make it more exact.

2. From the number they dialed (a number's region)

You can pin a default region to a tracking number, so every call to that number is treated as that area. This is perfect for a number that only runs in one market, like a Florida ad number. On the campaign's Tracking Numbers tab, click a number's Region cell and set the state (and a ZIP for a tighter center).

  • Fallback (default): the number's region is used only when the caller's own location is unknown, so a real caller ZIP still wins.
  • Always use this region: every call to this number counts as that market, no matter what the network reports.

3. Keypad entry (ask the caller)

Turn on Collect ZIP Code in the call flow to have the caller key in their own 5 digit ZIP before the call routes. This is the most exact method, because it comes straight from the caller. On the campaign's Call Flow tab, open the Collect ZIP Code step, switch it on, and optionally set your own prompt (the default is "Please enter your 5 digit ZIP code"). The ZIP the caller enters is used for routing and saved on the call.

The keypad step is fail-open: if a caller doesn't enter a ZIP, the call still routes using whatever location we already have (their number, or the tracking number's region). No call is ever dropped for a missing ZIP.

You can pair keypad entry with the IVR menu step ("press 1 for sales"). We ask for the ZIP first, then show the menu, so the destination gets both the caller's area and their menu choice.

4. Sent ahead of the call (from your traffic partner)

If a partner pre-qualifies a caller and then transfers the live call to your tracking number, they can send you the caller's details, including their ZIP, in a quick web request just before the call lands. We match those details to the incoming call by phone number and use the ZIP for routing, with no prompt for the caller. This is the same idea as a warm transfer. See Warm Transfer (Pre-Call Data) for how a partner sends the data.


What happens with the ZIP once we have it

However the ZIP arrives, it does the same job: it is matched against each destination's area (a radius around a center ZIP, a city, a state, or a list of ZIPs), and only the destinations that cover the caller ring. The ZIP is also saved on the call for your reports. Set the areas your destinations cover with Geographic Routing.


FAQ

Frequently Asked Questions

Do I have to pick just one method?
No. You can use several at once. A keypad ZIP or a partner-sent ZIP is treated as more reliable than the network's guess, and a tracking number set to "Always use this region" wins over everything, so you can layer them.
Will the caller always be asked to enter their ZIP?
Only if you turn on the Collect ZIP Code step. The other three methods are automatic and silent. If you turn it on and the caller doesn't enter anything, the call still routes on the location we already have.
Can I filter destinations to specific ZIPs?
Yes. Give each destination a ZIP area (a radius, a city, a state, or a list of ZIPs) and the caller's ZIP is matched against it. See Zip Code Filtering and Routing to Local Agents by Territory.
Does this compare to how Ringba collects ZIP codes?
Yes. All four of Ringba's methods (caller profile, number pools, a keypad Gather, and inbound data enrichment) have a match here, and Lead Distro AI adds ZIP-radius targeting on top so a destination can cover everything within a set number of miles of a center ZIP.

If you have any questions, send us an email at support@leaddistro.ai