Every ticket on the map, on the exact spot.

PinPoint is our own Freshdesk app. Inside the ticket, the agent searches an address and drags the pin until it sits on the right gate. The latitude and longitude are saved into ticket fields that belong to you. Whoever dispatches opens the PinPoint map from the left navigation bar and sees the whole queue at once, clustered by area and coloured by priority.

The PinPoint full-page map inside Freshdesk, with ticket clusters over Sao Paulo, Rio de Janeiro and Belo Horizonte and a synchronised ticket list on the left.
The whole queue, by location. Sixteen located tickets across three cities, clustered when you are zoomed out, with the ticket list on the left kept in sync with the map.

Two screens, and the coordinates stay in your Freshdesk.

PinPoint lives in two places inside Freshdesk and invents no database of its own. What it saves goes into ordinary ticket fields, which means the rest of Freshdesk can use it.

In the ticket

The PinPoint panel opens in the ticket sidebar. The agent types an address, picks the right match from the list, and drags the pin onto the exact spot. One click saves it.

On the map

The full-page map opens from the left navigation bar. Every ticket that has coordinates shows up there, grouped into clusters when you are far away, pin by pin as you zoom in.

In your own fields

Latitude and longitude are written to plain single line text fields on the ticket. Views, filters, automations, exports and reports can all read location from then on.

This is what your team sees.

Screenshots from a Freshdesk account with a real queue on it: sixteen located tickets spread across three cities, a mix of priorities and statuses.

The PinPoint panel in the Freshdesk ticket sidebar: an address search box, a small map with a blue pin, the coordinates read-out and the Save location to ticket button.
The panel in the ticket. Address search, a draggable pin, and the address read back to you. The button writes latitude and longitude onto the ticket; Clear empties them.
The PinPoint panel showing three geocoding results for Rua Augusta, in Consolacao, Jardim Paulista and Tijuca, each with its full address.
Ambiguous address. Three streets called Rua Augusta in different neighbourhoods. PinPoint lists every candidate with its full address so the agent picks, instead of the app guessing.
A pin popup on the PinPoint map showing ticket 43, its subject, the requester name, Open and Urgent badges, the street address, the coordinates and an Open ticket link.
From the pin to the ticket. Click a pin and you get the subject, the requester, the status and priority badges, the address, the coordinates, and a link that opens the ticket in Freshdesk.
The PinPoint map with the High and Urgent priority filters switched on, the ticket list narrowed to ten tickets and the clusters redrawn.
Filter by priority. High and Urgent switched on, and the list drops from fourteen tickets to ten. The map and the list always move together.
The PinPoint map filtered by the text Rio de Janeiro, showing four tickets in that city and the map zoomed to them.
Search the queue as text. Type a subject, a requester, a tag, a place or a ticket number. Here Rio de Janeiro leaves the four tickets in that city.
The PinPoint map zoomed to street level over Sao Paulo, with individual pins coloured red, orange and blue according to ticket priority.
Street level. Zoom in and the clusters break into single pins. The colour is the priority, and the legend stays in the corner.

Teams whose tickets happen at a place.

If your tickets carry an address, someone on your team is already copying that address into WhatsApp and opening Google Maps in another tab. That is the part PinPoint removes.

Field service and repair

A technician per region, an address per ticket. Seeing three open tickets two blocks apart is the difference between one trip and three.

Facilities and property

Many buildings, many wings, one ticket queue. The pin lands on the right wing, not on the street the building is registered at.

Installation and maintenance

The equipment sits at a place that no address describes well: a gate, a cabinet, a pole. Drag the pin and the exact spot is on the ticket.

Utilities and telecom

A flooded fibre box or a dead transformer is a location before it is a ticket. Clustered pins show where a storm actually hit.

Logistics and last mile

Delivery complaints spread over a city. The map turns a list of addresses into a route someone can plan.

Retail chains

Hundreds of branches supported by one help desk. Filter by priority and you see which regions are on fire right now.

About five minutes, and you own the data.

Create two ticket fields

Latitude and Longitude, both single line text. A Number field rounds the decimals and destroys the precision of a coordinate.

Copy an API key

From an agent who may view and update tickets. The key is a secure installation parameter: Freshworks encrypts it, uses it server-side, and it never reaches the browser.

Install and configure

Field names, the map centre and zoom it opens at, how many days back the map scans, the ticket cap, the tile provider and the geocoding host. Every external service can be pointed at your own infrastructure.

Pin your first ticket

Open a ticket, search the address, drag, save. Click the PinPoint icon in the left navigation bar and it is already on the map.

PinPoint needs a Freshdesk plan with ticket custom fields and API access, which means Growth or above. A Free account cannot create the fields the app writes to.

There is no PinPoint server.

No backend, no database, no telemetry. The app runs inside your Freshdesk account and writes only to the fields you created. We publish it and we cannot see your tickets, your coordinates or your API key.

Drawing a map does need two outside services. Geocoding, which by default is the OpenStreetMap Nominatim service and receives nothing but the address text, server-side. And map tiles, by default from OpenStreetMap. Both are settings, so an account that cannot send addresses to a public service points PinPoint at its own instances and nothing leaves.

Ticket text is HTML-escaped before it reaches a map popup, every outbound call goes through a declared request template, and the Leaflet libraries load from a CDN with pinned integrity hashes.

The things people ask first.

Is PinPoint free?

The app is free. The cost is indirect: every map refresh spends Freshdesk API calls, about 31 credits with the defaults of a 30 day window and a cap of 1000 tickets. On a busy account, narrow the window or lower the cap.

Do I need an account with a map provider?

Not with the defaults, which use OpenStreetMap. For a large team, the OSM usage policy does not allow heavy automated traffic, so it is worth paying a tile provider and pasting its URL template into the settings. The same goes for geocoding at volume.

Where do the coordinates live?

In text fields on your tickets, inside your account. Uninstall the app and the values stay where they are, because they were never ours to keep.

Does it work on Freshservice or Freshsales?

Today it is Freshdesk. The platform underneath is the same, so a port is real work but not a rewrite. If that is what you need, tell us.

What if the address is not on the map?

Rural addresses are often missing from OpenStreetMap. The agent searches whatever the geocoder does know, drags the pin to the right place and saves. The coordinate never depended on the search being right.

How do I get it installed?

Talk to us and we install it in your account, create the fields, configure the settings with you and walk your agents through it. We are an authorized Freshworks partner, so the Freshdesk side is our day job too.

Can it be customised?

Yes. We wrote it. Another field, another filter, or a link to your asset database is a scoped project, not a feature request into the void.

Put your queue on the map.

We install it, configure it and show your team how it works. Come talk to us.

Back to all solutions