Every visit to an asset, on one record, from the first Freshdesk ticket on
Keep the asset record where the work is done, and point every Freshdesk ticket at it. In Fieldproxy, each site holds the assets installed there, and every visit to an asset is kept on its record: what was found, what was done, parts used, readings and photos. When a ticket arrives with a serial number or asset tag, the job opens with that asset and its history attached. On site, the technician scans the asset's QR code to open the same record. The technician's notes go back to the Freshdesk ticket as private notes, so the agent sees what was done this time too.
Part of the Freshdesk integration. Fieldproxy replaces the asset spreadsheet and paper service logs, with asset management set up around your equipment and live within a day.
See your assets with their history
Send us your asset list. We show a Freshdesk ticket opening a job with the right asset and its past visits.
How it works
From a ticket about a machine to its full history, step by step
The history only helps if every visit lands on the same asset record. This is how each Freshdesk ticket adds to it.
- 1
The ticket names the asset
Customer, or the agent
A serial number, asset tag or model field on the Freshdesk ticket form, filled by the customer or the agent while troubleshooting. - 2
The job opens with the asset attached
Fieldproxy
When the ticket is sent, the serial number or tag is matched to the asset under the right site, and the job opens with the asset's past visits, readings and parts. - 3
The dispatcher sees what it needs
Dispatcher, helped by the Dispatch agent
The asset type tells the Dispatch agent which skills and parts the job likely needs, so it can suggest a technician with both. - 4
The technician confirms on site
Technician, Android or iOS app
Scanning the asset's QR code confirms it is the right unit, or attaches it if the ticket didn't name one. The history is on the phone, offline. - 5
The visit is recorded on the asset
Technician
Checklist answers, readings, parts used, photos and the signature are saved to the job and to the asset's history. - 6
The ticket hears what was done
Fieldproxy, written to Freshdesk
The technician's notes go to the ticket as private notes, and the ticket is set to Resolved or your chosen status.
What syncs
What moves between Freshdesk and Fieldproxy, which way and when
For asset history, the key is the asset identifier coming in and the visit notes going back.
| What | Direction | When | Detail |
|---|---|---|---|
| Serial number or asset tag | Freshdesk โ Fieldproxy | With the ticket | Matched to the asset under its site; no match means the technician picks or scans it. |
| Company and address | Freshdesk โ Fieldproxy | With the ticket | Matched to the customer and site that hold the asset. |
| Asset records | Freshdesk โ Fieldproxy | At setup | Imported once from your spreadsheet or old app; kept in Fieldproxy from then on. |
| Technician's notes | Fieldproxy โ Freshdesk | As they are added | Private notes on the ticket. |
| On site | Fieldproxy โ Freshdesk | At GPS check-in | Private note. |
| Full asset history on the ticket | Fieldproxy โ Freshdesk | On request | Set up per account. |
| Visit report and photos | Fieldproxy โ Freshdesk | On completion | On the job and the asset; attaching to the ticket is set up per account. |
| Ticket status | Fieldproxy โ Freshdesk | When the job is complete | Resolved, or a status you choose. |
See your own Freshdesk tickets turn into jobs before you commit.
Get DemoWhat stays, what moves
Freshdesk keeps the tickets. Fieldproxy replaces the field tools.
Freshdesk records the conversation about a fault. The machine's history, what was replaced last spring, the reading that has been creeping up, belongs to the asset and the field team. That record moves out of spreadsheets and paper logs into Fieldproxy.
Stays in Freshdesk
- The customer's report of the fault and the troubleshooting conversation.
- Ticket history per customer contact.
- Support macros and knowledge base articles.
- Freshdesk reporting on tickets.
Moves to Fieldproxy, and what it replaces
Dispatch and the schedule
The spreadsheet or whiteboard beside Freshdesk goes. Every technician and job is on one board and map, the Dispatch agent suggests who should go, a dispatcher approves, and any move can be undone.
The technician app
Any separate field app goes. Technicians use the Fieldproxy Android and iOS app, offline, with the site notes, asset history, your checklist, photos, signature and GPS check-in.
Sites, assets and QR codes
Each location on a ticket is a site record with its address, access notes and contacts, and the assets installed there with their history. A QR code per site and per asset opens the same record on the phone.
Mileage sheets and timesheets
GPS check-in and check-out sit on the job, and drives between jobs roll into a mileage claim a manager approves. See GPS timesheets and mileage.
Stock, quotes and invoices
Parts come off van or warehouse stock and are reordered on purchase orders. Quotes, invoices, payment links through Stripe and Tap to Pay run from the job, with two-way sync to QuickBooks Online, Desktop and Enterprise, Xero and Sage.
Ask it from Claude, ChatGPT or Copilot
Fieldproxy has its own MCP server: anything you can do in the app, such as finding the jobs waiting on a visit or raising the invoice, can be done from Claude, ChatGPT or Copilot, with a confirm step before any change.
Worked example, demo data
The third call about the same chiller, seen in time
Say Northfield Lab Services maintains chillers and incubators for university labs and runs support in Freshdesk. The asset tag is a required field on their fault form.
- 1
The ticket arrives
Ticket #5521 from the Biology building: chiller CH-14 alarm, temperature drifting. The agent asks for the asset tag, the lab manager enters CH-14, and the agent sends it to Fieldproxy. - 2
The history is attached
The job opens with CH-14 and its record: two visits in the last six months, both for the same alarm, both closed after a reset, and the condenser pressure readings rising each time. - 3
The right person goes
The Dispatch agent suggests Bram, who has refrigeration skills and a condenser fan motor in his van. The dispatcher approves; the ticket gets a scheduled note. - 4
On site
Bram scans the QR code on CH-14, sees the trend, and replaces the fan motor instead of resetting again. He records the new pressure reading and photos. - 5
Back to the ticket
His note goes to the ticket: fan motor replaced after repeat alarms, pressure back in range. The ticket is set to Resolved, and the visit is the third entry on CH-14's history.
Result: The repeat fault was fixed at the cause on the third visit instead of reset a third time, because the history was on the job before Bram left.
Names, sites and ticket numbers in this example are made up to show the flow. They are not a customer and not a result.
Setup
Connected, set up around your queues, live within a day
Most of the work is getting your assets into Fieldproxy once, under the right sites.
- 1
Send us your asset list
From a spreadsheet, an old field app or your Freshdesk custom fields. It comes across with free, assisted migration. - 2
Agree the identifier
Which ticket field carries the serial number or asset tag, and whether to make it required on your Freshdesk form. - 3
Set checklists per asset type
The readings, photos and parts each type of asset should record on every visit. - 4
Print QR codes
One per asset and per site, so technicians can open the record by scanning it. - 5
Connect Freshdesk and test
API key and automation rule, then a few real tickets through to check the right asset opens.
Moving off a spreadsheet or another field app? Sites, assets, customers and open jobs come across with free, assisted migration. Fieldproxy is one price per company with unlimited users, so support agents, dispatchers, technicians and contractors can all log in. See pricing.
Fit
Who this is for, and when it isn't the right fit
A good fit when
- You service equipment that comes back with repeat faults: HVAC, refrigeration, lab, medical, printing, vending.
- Asset history currently lives in spreadsheets, paper logs or a technician's memory.
- Customers can give a serial number or asset tag when they raise a ticket.
- You run planned maintenance and break-fix on the same assets.
Probably not the right fit when
- Your work isn't tied to specific equipment, such as cleaning or general repairs.
- Your assets already live in an ERP or asset system that must stay the master; that needs its own integration agreed at setup.
- You want Freshdesk itself to become the asset register.
Straight answers
Asset service history with Freshdesk: questions we get asked
Where does the asset history live?
How is a ticket matched to an asset?
Can Freshdesk agents see the asset history?
How do technicians open an asset on site?
Can we import the assets we already have?
What gets recorded on each visit?
Does this cover planned maintenance as well as tickets?
Can I ask about an asset's history from Claude or ChatGPT?
How long does it take to set up?
Related
Where to go next
Every helpdesk Fieldproxy connects to follows the same pattern: the ticket stays where it is, the visit runs in Fieldproxy, and the result goes back. The same flow for Freshservice, Zendesk, Zoho Desk and ServiceNow.
Know the machine before you arrive.
Send us your asset list. We show your Freshdesk tickets opening jobs with the right asset and its history.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.