Dispatch Freshdesk tickets by the time you promised, not by who shouted
Let the ticket's priority set the job's due time, and dispatch in order of that due time rather than in order of arrival. When a Freshdesk ticket becomes a Fieldproxy job, its priority comes across and sets a due-by time from your own response rules. The Dispatch agent suggests a technician who can get there in time, by distance, skill and the day's load, and a dispatcher approves. The Watcher agent flags a job that is heading past its due time while there is still time to act, and the ticket gets a private note at each step.
Part of the Freshdesk integration. Fieldproxy replaces the dispatch spreadsheet where due times are worked out by hand, and is live within a day.
See your priorities drive dispatch
Tell us what you promise per priority. We set up the rules and show a day of your tickets dispatched by due time.
How it works
From ticket priority to a technician on site in time, step by step
A support SLA times the reply. A field promise times the visit. This flow turns the first into the second and keeps both in view.
- 1
The ticket is sent with its priority
Freshdesk agent, or an automation rule
When a ticket is sent to Fieldproxy, its priority, ticket type and company come with it. These are the inputs for the due time. - 2
A due time is set on the job
Fieldproxy, by your response rules
Your rules turn priority, job type and customer into a due-by time, for example Urgent: on site within 4 hours. Business hours and contract customers are part of the rule if you need them. - 3
The queue is ordered by due time
Dispatch board
Jobs waiting to dispatch are listed by how close they are to their due time, so the dispatcher sees the one that matters first, not the one that arrived first. - 4
A technician who can make it is suggested
Dispatcher, helped by the Dispatch agent
The Dispatch agent ranks technicians by distance, skill, the day's load and van stock against the due time. The dispatcher approves, and the ticket gets a private note with who is going and when. - 5
At-risk jobs are flagged early
Watcher agent
The Watcher agent flags a job that is not moving toward its due time: not yet assigned, technician running late, or stuck in a stage. The dispatcher decides what to do. - 6
Arrival and completion go back
Fieldproxy, written to Freshdesk
GPS check-in adds an on-site note, so arrival time is a fact, not a phone call. When the job is done, the ticket is set to Resolved or your chosen status.
What syncs
What moves between Freshdesk and Fieldproxy, which way and when
For SLA dispatch, what matters is the priority coming in and the timestamps going back.
| What | Direction | When | Detail |
|---|---|---|---|
| Ticket priority | Freshdesk โ Fieldproxy | With the ticket | Sets the job priority and, through your rules, the due time. |
| Ticket type and company | Freshdesk โ Fieldproxy | With the ticket | Pick the job type and any customer-specific response rule. |
| Freshdesk due date | Freshdesk โ Fieldproxy | With the ticket | Carrying the ticket's own due date across, instead of computing one, is set up per account. |
| Priority changes on the ticket | Freshdesk โ Fieldproxy | After the job exists | Whether a raised priority re-times the job is set up per account. |
| Scheduled and assigned | Fieldproxy โ Freshdesk | When dispatch confirms | Private note with the technician and time window. |
| On site | Fieldproxy โ Freshdesk | At GPS check-in | Private note with the arrival, from the phone's location at the site. |
| Technician's notes | Fieldproxy โ Freshdesk | As they are added | Private notes. |
| Ticket status | Fieldproxy โ Freshdesk | When the job is complete | Resolved, or a status you choose. |
| Time on site | Fieldproxy โ Freshdesk | On completion | Recorded on the job; writing it to the ticket is set up per account. |
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 measures how fast support answers. It does not know where technicians are, how full their day is or how long the drive takes, so field due times end up worked out in a spreadsheet. That spreadsheet is what goes.
Stays in Freshdesk
- Freshdesk SLA policies for first response and resolution of the conversation.
- Ticket priority, set by agents or your automations.
- Support reporting on response times.
- The customer conversation about when someone will come.
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
Three tickets, one technician short, on a Monday morning
Say Lumen Gate Access services automatic doors and barriers for shops and car parks. Their rule: Urgent on site within 4 hours, High by end of the next working day, Normal within 5 working days.
- 1
Tickets arrive
By 8:30 three tickets are sent: #3301 Urgent, a supermarket door stuck open; #3302 Normal, a squeaking barrier arm; #3303 High, a car park gate slow to close. - 2
Due times are set
#3301 is due on site by 12:30 today, #3303 by end of tomorrow, #3302 by Friday. The dispatch queue lists them in that order. - 3
The urgent one is dispatched
The Dispatch agent suggests Tomรกs, 9 miles away with a door sensor in his van. The dispatcher approves; the ticket gets a note: Tomรกs assigned, 10:15 to 11:15. - 4
A risk is flagged
Tomรกs is held up on his first job. At 11:20 he hasn't left, and the Watcher agent flags #3301 as at risk. The dispatcher moves it to Hana, who is closer now, and the ticket gets a new note. - 5
On site and resolved
Hana checks in at 12:05. The ticket gets an on-site note, and when she finishes the ticket is set to Resolved. - 6
The rest of the week
#3303 goes onto Tomรกs's Tuesday route, and #3302 joins a Thursday run in the same area.
Result: The urgent door was fixed inside the promise because the risk showed up at 11:20, not at 12:31, and the agent could answer the supermarket from the notes on the ticket.
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
The work is agreeing the response rules. The Freshdesk connection itself is a few minutes for an admin.
- 1
Write down your promises
On-site or completion times per priority, job type and contract customer, with business hours if they apply. - 2
Map Freshdesk priorities
Each Freshdesk priority, and any custom field you use for urgency, to a response rule. - 3
Set up technicians
Skills, home areas, shifts and van stock, so the Dispatch agent knows who can make the time. - 4
Choose the warnings
When the Watcher agent should flag a job, and who sees the flag. - 5
Test on a real day
Run a day of real tickets through and compare the due times with what your team would have promised. Then go live.
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 promise on-site times by priority or by contract, and missing them costs you.
- Several technicians cover an area and the nearest free one isn't always the right one.
- The dispatcher currently works out due times by hand from the ticket.
- Support needs to tell customers when someone is coming without asking the field.
Probably not the right fit when
- You have no response promises and visits are booked whenever suits the customer.
- One technician covers everything; ordering the queue by hand is enough.
- You want the system to reassign jobs on its own with no dispatcher. Fieldproxy suggests and flags; a person approves.
Straight answers
SLA-based dispatch from Freshdesk: questions we get asked
Where does the job's due time come from?
Does Fieldproxy replace Freshdesk's SLA policies?
Is the technician assigned automatically?
What happens when a job is about to miss its due time?
Can an urgent ticket bump a job already on someone's day?
Do technicians see the due time?
What does the Freshdesk ticket show?
Can different customers have different response times?
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.
Dispatch by the promise, see the risk before the breach.
Tell us your response times per priority. We show a day of your tickets dispatched against them.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.