> ## Documentation Index > Fetch the complete documentation index at: https://support.parker.work/llms.txt > Use this file to discover all available pages before exploring further. # Find records near a place > Ask Parker which Salesforce records are near a suburb, address, or one of your sites, and read the ranked table and map it returns. Ask Parker a location question in plain language. It answers with a ranked list and a map of your Salesforce records, usually in a second or two. ## Before you begin * Connect your own Salesforce login. See the [Quickstart](/quickstart). * The records you want to find need an address you can read in Salesforce. Parker places Australian addresses only. See [Current limits](/maps/how-locations-work#what-are-the-current-limits). Parker's answers come from your live data and can vary from one run to the next. Check important figures against Salesforce before acting on them, and use the sources Parker shows to see where an answer came from. ## 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. | Ask something like | What Parker does | | - | - | | Which leads are within 25 km of Parramatta? | Ranks leads by distance from that suburb, nearest first, with a map. | | Which leads are interested in a site near Geelong? | Searches by the location each lead is interested in, not where they are. | | Which Queensland leads are closest to Brisbane? Add their Rating. | Lists the nearest leads in that state and adds the extra column to the card. | | For leads created this week, which of our branches is nearest to each one? | Matches each lead to its nearest branch. | | Show all our branches on a map. | Plots every branch. | | How long is the drive from our Melbourne branch to our other Victorian branches? | Gives drive times. | | Plan a route to visit customers in Fremantle, Joondalup, and Midland. | Puts the stops in the best order, with the time for each leg. | | Find cafes within 2 km of our Adelaide branch. | Finds nearby places. | | What is the area around Ballarat like? | Shows census figures, such as population, median age, and household income, compared with the state. | | Is 100 Example Street, Sydney NSW 2000 a valid address? | Checks the address against the national address file. | | Which contacts are within 30 km of Parramatta? | Searches other Salesforce objects that hold addresses, not only leads. | If you name a place as a value, such as "leads whose preferred branch is Hobart or Darwin", Parker runs a normal Salesforce filter. That's exact and fast, and it doesn't use distance. ## Ask a location question In a chat, say which records you want and where, for example "Which leads are within 25 km of Parramatta?" To search by a different kind of location, say so: "leads **interested in a site** near Geelong" searches the location each lead is interested in. See [How Parker finds locations](/maps/how-locations-work). Parker writes a short summary, then shows a card with a ranked table and a map. Ask a follow-up to change the search, such as "only the ones in Victoria", "within 10 km instead", or "add their Rating". ## How do you read the result card? Parker's answer with a ranked table of 8 leads showing distance, what located each one, and status, and a map with numbered pins inside a 5 km circle. * **The table** lists the nearest 25 records. Select **Show N more rows** for the rest. Columns show the record, its details, the distance, and what located it. Fields you ask for, such as Rating, 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](/maps/how-locations-work#how-does-parker-protect-your-data). ## 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 Which leads are within 25 km of Parramatta? Which leads are interested in a site near Geelong? Plan a route to visit customers in Fremantle, Joondalup, and Midland. ## Troubleshooting 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. Say which location you mean, for example "leads interested in a site near Geelong" or "leads who own a property near Geelong". 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. That's expected. Distances and times worked out from Google appear only on the card and map. ## Related What each address field means, how precise a point is, and how your data is protected. Find records, pipeline, and activity in plain language. Show other answers as a chart, table, or diagram. Preview and turn on how Parker reads ambiguous location fields. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.