After completing this guide, you will understand how ANET’s Verified Location feature works, how to configure it within your environment, and how the system verifies spoken caller locations during non-emergency call workflows.

ANET’s Verified Location feature converts a caller’s spoken description of a location into a structured, verified address that can be used confidently for dispatch and response workflows.

During a call, ANET:

• Listens to how the caller describes their location

• Interprets the spoken location

• Verifies the location against mapping and geolocation services

• Reads the interpreted location back to the caller

• Asks the caller to confirm whether the location is correct

• Stores both:

  • the original spoken location, and

  • the verified location

This feature helps agencies manage non-emergency calls where automatic location data is unavailable.

Unlike traditional 911 calls, most 10-digit non-emergency calls do not include automatic location data such as ANI/ALI.

As a result:

• callers may describe locations informally,

• addresses may be incomplete or unclear,

• and dispatchable incidents may still require accurate location verification.

Examples of spoken caller descriptions include:

• “by the Walmart”

• “128… no, 182 Main”

• “southbound highway near mile marker 12”

Verified Location helps ANET collect and confirm location details similarly to how a trained call taker would manually verify information.

ANET can verify several types of locations, including:

• Street addresses

• Cross streets

• Business names

• Chain businesses

• Landmarks

• Parks

• Highway directions and mile markers

Before using Verified Location:

• Verified Location must be enabled within your ANET environment

• Your intent configuration must include a location-related follow-up question

Example:

“Where did the incident occur?”

From your ANET non-emergency environment, navigate to the Location tab.

Turn the Enable Verified Location toggle ON.

When enabled:

• ON = Blue

Search for and select the city or jurisdiction you want ANET to use during location verification.

Examples include:

• New York

• Los Angeles

• Seattle

After selecting a city, ANET automatically generates configuration values for that jurisdiction.

Select Save to apply the configuration.

Do not manually edit any automatically generated configuration values.

These fields are displayed for engineering visibility and troubleshooting purposes only.

Editing these values may cause:

• inaccurate verification behavior,

• failed demos,

• or unsuccessful location matching.

The caller describes where the incident occurred.

Example:

“I last saw it at the corner of 82nd and 3rd Avenue on the Upper East Side.”

ANET:

• transcribes the spoken location,

• searches for matching locations,

• and prioritizes results relevant to the configured service area.

Verification may use:

• Google geolocation services

• ESRI mapping layers (when configured)

ANET asks the caller to confirm the interpreted location.

Example:

“I found East 82nd Street and 3rd Avenue in New York. Is that correct?”

The location is marked as verified.

Example:

“Yes.”

ANET asks follow-up questions and attempts verification again.

Example:

“No, it was closer to Lexington Avenue.”

If multiple matching locations exist, ANET asks additional questions to narrow the result.

Example:

“I found multiple Chick-fil-A locations nearby. Can you share cross streets, landmarks, or additional details?”

This helps improve dispatch accuracy for chain businesses and commonly named locations.

If ANET cannot confidently verify a structured address, the system preserves the caller’s spoken wording instead of guessing.

Examples may include:

• “two thirty two ninety second street”

• “one twenty eight main”

• “southbound interstate near mile marker twelve”

This reduces the risk of incorrect dispatch information caused by uncertain address interpretation.

The Insights View displays both:

Verified locations can also be:

• viewed in Google Maps,

• displayed within archived call records,

• and mapped using the same interface used by ACT.

https://www.loom.com/share/59727705a6e24c8caab11e7040425ff9

For additional assistance or configuration support, contact:

Support@prepared911.com