Dispatch technicians from Freshdesk tickets, and keep every ticket up to date
Keep Freshdesk as your support desk and send only the tickets that need someone on site to Fieldproxy. An agent ticks a field such as Send to Fieldproxy, or a Freshdesk automation rule does it for them, and the ticket becomes a job with the contact, the site and the asset attached. Fieldproxy dispatches it, the technician works it on the phone with GPS check-in, photos and a checklist, and each step goes back to the same ticket as a private note. When the job is done, the ticket is set to Resolved, or to the status you choose.
Fieldproxy is AI-native field service software, set up around how your team works and live within a day. It replaces the dispatch spreadsheet and any separate field app. Freshdesk stays where customers raise tickets and agents answer them.
See your Freshdesk tickets turn into jobs
Tell us which tickets need a visit today. We set it up on your own fields and job types before you commit.
How it works
From Freshdesk ticket to finished visit, step by step
This is how a typical setup runs. The condition that sends a ticket, the job types and which updates go back are agreed with you.
- 1
A ticket needs someone on site
Freshdesk agent, or an automation rule
The agent ticks a field such as Send to Fieldproxy, or a Freshdesk automation rule matches a condition (a ticket type, group, tag or custom field) and calls Fieldproxy's webhook. A ticket that can be fixed by phone or remotely stays in Freshdesk and never becomes a job. - 2
The job is created with the site and asset attached
Fieldproxy
The contact, company, address, subject, description, priority and ticket ID are copied onto a new job. The company is matched to the customer record and the address or a site field to the site, with its access notes and the assets installed there. If the ticket names an asset (a serial number or asset tag), the asset and its service history are attached. If nothing matches, the job waits for the office with the reason, instead of going out half-filled. - 3
The right technician is picked
Dispatcher, helped by the Dispatch agent
The Dispatch agent suggests a technician by skill, distance, the day's load and the due time. A dispatcher approves, or routine job types are assigned by rule. Changes are previewed and can be undone. - 4
The ticket hears who is going
Fieldproxy, written to Freshdesk
A private note on the ticket says the job is scheduled and which technician is assigned. The agent can answer the customer's "when is someone coming?" without messaging the field team. - 5
The visit runs on the phone
Technician, Android or iOS app
GPS check-in on arrival, the site's access notes, the asset's history, the checklist for this job type with required photos and readings, parts from van stock and the customer's signature. The app works offline and syncs when signal returns. - 6
Progress and the result go back
Fieldproxy, written to Freshdesk
On site and the technician's notes are added as private notes. When the job is complete, the ticket is set to Resolved, or to the status you choose. If a return visit or a quote is needed, the job stays open and the ticket says why. - 7
Billing comes from the job, not an email
Fieldproxy
Labour, parts and charges on the finished job become an invoice with a payment link, or sync to QuickBooks, Xero or Sage. Freshdesk is not involved in billing.
What syncs
What moves between Freshdesk and Fieldproxy, which way and when
Fieldproxy connects through the Freshdesk REST API v2 and Freshdesk automation webhooks, with an API key from an admin agent. The rows marked set up per account are possible on the Freshdesk API but are agreed with you, not switched on by default.
| What | Direction | When | Detail |
|---|---|---|---|
| Ticket that needs a visit | Freshdesk โ Fieldproxy | When an agent ticks the field, or an automation rule matches | Contact, company, address, subject, description, priority, attachments and the ticket ID become a job. |
| Company and contact | Freshdesk โ Fieldproxy | With the ticket | Matched to an existing customer and site contact. No match means the job waits for the office, rather than a duplicate customer. |
| Scheduled and assigned | Fieldproxy โ Freshdesk | When a dispatcher confirms the technician and time | Private note with the technician and the time. |
| On site | Fieldproxy โ Freshdesk | At GPS check-in | Private note, so arrival is shown by the check-in rather than a phone call. |
| Technician's notes | Fieldproxy โ Freshdesk | As the technician adds them | Private notes with what was found and done. |
| Ticket status | Fieldproxy โ Freshdesk | When the job is completed | Set to Resolved, or a status you choose. Only after the job's required checklist items are done. |
| Visit report and photos | Fieldproxy โ Freshdesk | On completion | The branded job report with photos, checklist and signature is on the job. Attaching it or linking it on the ticket is set up per account. |
| Time on site | Fieldproxy โ Freshdesk | On completion | Recorded on the job from check-in to check-out. Writing it to the Freshdesk ticket as a time entry is set up per account. |
| Mileage | Fieldproxy โ Freshdesk | Per trip, rolled up monthly | Kept in Fieldproxy as GPS trips and a monthly claim per technician. Not written to the ticket unless you ask for it in the closing note. |
| Later ticket updates | Freshdesk โ Fieldproxy | When the ticket changes after the job exists | Which changes (priority, a new note from the customer) should update the job is set up per account. |
Each ticket links to one job, so a ticket sent twice updates the same job instead of creating another.
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 is good at the conversation: who asked, what they asked, how fast you answered. It was not built to decide which technician goes, carry the site's access rules to a phone, force a photo before a job closes or count the parts that left the van. Those pieces usually end up in a spreadsheet, a group chat and a separate field app. Fieldproxy replaces those, not Freshdesk.
Stays in Freshdesk
- Customers raise tickets by email, portal, chat or phone, as they do today.
- Agents answer customers and own the conversation.
- Your Freshdesk SLA policies, automations and canned responses.
- Ticket reporting and CSAT for the support team.
- The ticket stays the record the customer and the agent look at, with the field story written onto it.
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
A coffee machine fault, from ticket to resolved
Say Corvane Coffee Systems services espresso machines in cafรฉs across one region and runs support in Freshdesk. Most tickets are fixed by phone. This one is not.
- 1
The ticket arrives
Ticket #20417 from Harbour Lane Cafรฉ: "Group head leaking, machine unusable." Priority Urgent. The agent walks the owner through a reset, it doesn't help, and she ticks Send to Fieldproxy. - 2
The job is created
Fieldproxy matches Harbour Lane Cafรฉ to its site record (back door access before 7 am, key code in the site notes) and the ticket's serial number to the machine, a two-group espresso machine installed last spring. The job lands in To dispatch with the ticket ID. - 3
Dispatch picks a technician
The Dispatch agent suggests Priya, 4 miles away, finishing a descale at Elm Street Bakery, with a group head gasket kit in her van stock. The dispatcher approves. Freshdesk gets a private note: Priya assigned, today 13:30 to 14:30. - 4
The agent answers the customer
The cafรฉ owner replies asking when someone is coming. The agent reads the note and answers in one line, without messaging anyone. - 5
The visit
Priya checks in at 13:42 and a private note says she is on site. She scans the QR code on the machine, opens its history and sees the same gasket was replaced 9 months ago. She replaces it, takes before and after photos, records the brew pressure in the checklist and gets the owner's signature. - 6
Back to the ticket
Priya's note (gasket replaced, pressure normal, water filter due next month) goes to the ticket as a private note, and the ticket is set to Resolved. The report with photos and signature is on the job, and the gasket is taken off her van stock. - 7
Billing
The callout and the gasket go onto an invoice with a payment link. The owner pays by card and the payment syncs to the accounting system.
Result: The agent never chased the field, Priya never retyped the ticket, and the next time this machine has a fault, both the agent and the technician can see this visit on the asset's history.
Names, sites and ticket numbers in this example are made up to show the flow. They are not a customer and not a result.
The options
Ways to run field visits from Freshdesk tickets
Described by kind of tool. Each fits some teams; check the trade-offs against how your visits actually run.
| Approach | Fits when | What you give up |
|---|---|---|
| Freshdesk alone, with a custom field, a group and a spreadsheet | A handful of visits a week, all by your own staff, no stock and no planned maintenance | No technician app, no required photos or checklists, no schedule view and no van stock. Dispatch lives in someone's head. |
| Freshdesk's own Field Service add-on | You signed up before May 5, 2023 and already use it | Freshdesk's support site says it is closed to newer accounts and is not getting further enhancements. |
| A field app from the Freshworks Marketplace | Agents want to book visits without leaving Freshdesk | Check what it does offline, whether checklists can be required, and whether it covers stock, contractors and invoicing. Many are scheduling add-ons, not full field systems. |
| A configurable field service system connected to Freshdesk (Fieldproxy) | Visits need their own checklists, sites have access rules, contractors do some of the work, and billing comes from the job | A second system to run. It replaces your field tools, so plan the switch-off date for the spreadsheet and the old app. |
Freshdesk add-on status from Freshdesk's support article โA guide to field service for helpdesk agentsโ, as of November 2026. Running Freshservice for IT and facilities rather than Freshdesk? See the Freshservice integration.
Workflows
Freshdesk and Fieldproxy, workflow by workflow
Ticket-to-job conversion
Which tickets become jobs, how they are matched to a site, and what happens when they don't match.
SLA-based technician dispatch
Dispatch against the due time the ticket's priority promises, not against whoever is free.
Escalation automation
A job that stalls is flagged before the customer chases the ticket.
First response from the field
The ticket learns who is going and when, so the agent's first answer is a real one.
Asset service history
Every visit to an asset on one record, so the next technician and the agent see what was done.
Customer feedback after the visit
Asking for feedback after the job is done, with the answer kept against the job.
The longer answer for IT teams on the Freshworks stack: how to dispatch technicians from Freshservice tickets, with GPS tracking and mileage.
Setup
Connected, set up around your queues, live within a day
The Freshdesk side needs an admin for a few minutes. The rest is done by Fieldproxy's team.
- 1
A 30-minute call
Which tickets need a visit, which fields carry the site and the asset, what should go back to the ticket and who sees it, and how a job is done on site. - 2
Connect Freshdesk
An admin agent creates the API key and adds the automation rule that sends a ticket to Fieldproxy when it matches your condition. - 3
Map tickets to jobs
Ticket types, groups, priorities and custom fields are mapped to job types, sites and assets. You pick the notes and the status written back. - 4
Build the field side
Job stages, checklists with required items, technicians with skills, van stock, and your invoicing and accounting sync. Sites and assets come across with free, assisted migration. - 5
Test on real tickets, then go live
Send a few real tickets through, complete them on the phone and check what lands back in Freshdesk. Then switch off the spreadsheet.
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
- Support runs in Freshdesk and some tickets end in a technician visit: equipment, appliances, IT hardware, property maintenance.
- Technicians drive between customer sites, and sites have access rules or assets with a history.
- You want required photos, checklists and a signature before a job counts as done.
- Contractors do some of the visits and should not need a Freshdesk seat.
- Billing, stock or mileage currently lives in spreadsheets beside Freshdesk.
Probably not the right fit when
- Every ticket is solved remotely. Freshdesk already does the job.
- A few visits a month by one person; a calendar may be enough.
- You want field updates to edit every Freshdesk field both ways in real time. The write-back is notes and status, with anything more agreed per account.
- You already run a full field service system you are happy with and only need a connector between the two.
Straight answers
Freshdesk and field service: questions we get asked
Can a Freshdesk ticket create a field service job automatically?
What gets written back to the Freshdesk ticket?
Is the Freshdesk integration two-way?
Will re-sending a ticket create a duplicate job?
Does the customer see the field updates?
Freshdesk had a Field Service add-on. Why use a separate system?
Do technicians or contractors need a Freshdesk agent seat?
What does Fieldproxy need from Freshdesk to connect?
How long does setup take?
Can I ask Claude or ChatGPT about jobs that came from Freshdesk tickets?
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.
Keep Freshdesk. Give the visit a proper home.
Tell us how a ticket becomes a site visit today. We show it running on your own fields and job types.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.