How to Filter Calls by Zip Code

Asking Callers to input their Zip Codes using IVR Prompts

1. In your Campaign, add an IVR prompt for Zip Code Entry in the Prompts section. This prompt will play immediately when the call connects.

   
   
   

2. Create a prompt for Zip Entry Failed. This plays when the caller does not enter a valid Zip Code. Without this additional prompt, the call will not disconnect upon multiple entry failure. You may want this message to repeat a couple times. In the example below, it will play a total of four times, the first play, then three repeats.

   
   
   

3. Lastly create a prompt for Zip Entry Too Many Attempts, this will play an exit message prior to hanging up the call once too many failed entries have been submitted.

   
   
   

View our "How To Tag And Filter Calls Using Prompts" guide for more information on IVR prompts.

Adding Zip code Filters to Endpoints

Edit your Call Endpoint (Buyer) and add your desired Geo Tags using the tag wizard to instruct Retreaver to only route calls to these endpoints with a matching geo value:

Tags present on a buyer's "taglist" will instruct Retreaver to only route calls to your Endpoints (Buyers) from the designated geographical areas.

Below is a screenshot of the Tag Wizard - Open to the Geo tab, with Zip selected. Two Zip Codes have been added as an example, and one more is in the process of being added. Of course, most people tend to upload a CSV of Zip Codes to be added in bulk.

Adding these Tags will tell Retreaver that these are the Zip Codes this Call Endpoint (Buyer) can accept, and not to send calls from other Zip Codes.

Accepted Geo Tag values

Geo tags come in the following format:
geo:[ISO 3166-1 alpha-2 country code](-optional state, province or zip).

For American based geo tags, the accepted format would be: geo:us-ca.
This would tag a component with a California state tag.

For Canadian based geo tags, the accepted format would be: geo:ca-bc.
This would tag a component with a British Columbia province tag.

For American zip codes, the accepted format would be: geo:us-90210.
This would tag a component with a "90210" zip code.

Overriding Caller City/State using Zip Codes

A Caller ID does not always correctly reflect the callers current geographic location, if the caller had recently moved to a new state but had not purchase a new phone number - their existing phone number and subsequent area code would not match their current geographical location.

Because of this possibility, some affiliates might wish to override the caller city or state we automatically infer using the caller ID area code by directly supplying a zip code instead for more accurate state coverage.

Tag your call with a "caller_zip" tag value of XXXXX, where X represents the 5 digit U.S zip code. 

For HTTP Post call tagging methods - the supplied parameter would look like:      "caller_zip=90210"
For JSON/Javascript call tagging methods - the supplied field would look like:      "caller_zip:90210"

Tagging your calls with a zip code will allow for more accurate state coverage, especially if you expect your leads to have moved states recently or plan on moving to a new state in the future.

Note: Tagging a "caller_zip" to a call will overide all existing geo tags on a call, while tagging a "geo:us-XX" state will only append an additional state to a call.