Before you begin
- Connect your own Salesforce login. See the Quickstart.
- The records you want to find need an address you can read in Salesforce. Parker places Australian addresses only. See Current limits.
What can you ask?
Ask the way you’d ask a colleague. Parker picks the right search and tells you how many records it couldn’t place.
If you name a place as a value, such as “leads whose interested store is Yeppoon or Chuwar”, Parker runs a normal Salesforce filter. That’s exact and fast, and it doesn’t use distance.
Ask a location question
1
Name the records and the place
In a chat, say which records you want and where, for example “Which leads are within 25 km of Roxburgh Park?”To search by a different kind of location, say so: “leads who want a franchise near Beechboro” searches the store each lead wants. See How Parker finds locations.
2
Read the summary and the card
Parker writes a short summary, then shows a card with a ranked table and a map.
3
Refine in the same chat
Ask a follow-up to change the search, such as “only the ones in Victoria”, “within 10 km instead”, or “add their Lead Score”.
How do you read the result card?
- The table lists the nearest 25 records. Select Show more for the rest. Columns show the record, its details, the distance, and what located it. Fields you ask for, such as Lead Score, appear as extra columns.
- The count is yours. Parker counts the matching records you can see in Salesforce. If it’s still counting, the card fills in the full number when it’s done.
- The footer says what Parker couldn’t place: records with no address, records outside Australia, and records with only a state. Ask Parker to include state-only records, and it lists them without a distance.
- The map shows numbered pins that match the table rows. Pins that are close together group into a cluster with a count.
- Expand map opens an interactive map. Select a pin to see its record, or select a table row to find its pin. On a phone or tablet, the map opens full screen.
- The number chip next to each name opens that record in Salesforce.
Some distances and drive times appear only on the card and map, not in Parker’s written summary. That’s a condition of using Google’s location data. See Privacy and data rules.
Check it worked
- The card’s count matches what you expect to see in Salesforce for that filter.
- Each row says what located it, such as a street address or a suburb.
- The footer explains any records Parker left out.
Example prompts
Find leads near a suburb
Search by wanted location
Plan a day of visits
Troubleshooting
A record I expected isn't on the map
A record I expected isn't on the map
Check the card’s footer. Parker can’t rank a record that has no address, only a state, or an address outside Australia. It also shows only records your own Salesforce login can read.
Parker searched where leads live, not the store they want
Parker searched where leads live, not the store they want
Say which location you mean, for example “leads who want a franchise near Beechboro” or “leads who own a property near Beechboro”.
My first location question today was slower
My first location question today was slower
Twice a day, Parker checks that its location index covers the records you can see. While it checks, your first search uses a slower direct path. Later searches are fast again.
A distance is on the map but not in Parker's answer
A distance is on the map but not in Parker's answer
That’s expected. Distances and times worked out from Google appear only on the card and map.
Related
How Parker finds locations
What each address field means, how precise a point is, and how your data is protected.
Ask about Salesforce
Find records, pipeline, and activity in plain language.
Charts and diagrams
Show other answers as a chart, table, or diagram.
Location readings (admins)
Preview and turn on how Parker reads ambiguous location fields.