Answer โwhen is someone coming?โ from the Freshdesk ticket
For a ticket that needs a visit, the useful first answer is not "we've received your request" but "Sam is coming tomorrow between 9 and 11". That answer lives in the field schedule, not in Freshdesk. With Fieldproxy, the ticket is sent as a job, dispatched, and a private note with the technician and time window lands on the ticket as soon as the dispatcher confirms. The agent answers from the ticket, without messaging the field team, and later notes for on site and the technician's notes keep the answer current.
Part of the Freshdesk integration. Fieldproxy replaces the messages between support and the field team, and is set up around your own job types, live within a day.
See the field answer land on the ticket
Tell us what customers ask while they wait for a visit. We show the notes landing on your own Freshdesk.
How it works
From ticket to a real answer for the customer, step by step
The aim is that every question a customer asks while waiting for a visit can be answered from the ticket.
- 1
Freshdesk acknowledges the ticket
Freshdesk, as today
Your Freshdesk automation or canned response confirms receipt. Nothing changes here. - 2
The ticket is sent to the field
Freshdesk agent, or an automation rule
The agent ticks Send to Fieldproxy, or a rule sends ticket types that always need a visit. The job is created with the site and asset attached. - 3
A technician is suggested straight away
Dispatch agent, approved by a dispatcher
The Dispatch agent suggests a technician by distance, skill and the day's load as soon as the job arrives. The dispatcher approves, or a rule assigns routine job types. - 4
The ticket gets who and when
Fieldproxy, written to Freshdesk
A private note with the technician's name and the time window. The agent replies to the customer from it, in their own words. - 5
Changes and arrival follow
Fieldproxy, written to Freshdesk
A reschedule writes a new note; GPS check-in writes an on-site note. The agent's next answer is as current as the field. - 6
The close is explained
Fieldproxy, written to Freshdesk
The technician's notes say what was done, and the ticket is set to Resolved or your chosen status, so the closing reply has the facts in it.
What syncs
What moves between Freshdesk and Fieldproxy, which way and when
For first response, what matters is how quickly the field facts reach the ticket after the job is created.
| What | Direction | When | Detail |
|---|---|---|---|
| Ticket marked for the field | Freshdesk โ Fieldproxy | Agent tick or automation rule | Creates the job with contact, site, asset and ticket ID. |
| Scheduled and assigned | Fieldproxy โ Freshdesk | As soon as dispatch confirms | Private note with technician and time window. |
| Rescheduled or reassigned | Fieldproxy โ Freshdesk | When the change is confirmed | A new private note, so the old time isn't repeated to the customer. |
| On site | Fieldproxy โ Freshdesk | At GPS check-in | Private note. |
| Technician's notes | Fieldproxy โ Freshdesk | As they are added | Private notes. |
| Public reply to the customer | Fieldproxy โ Freshdesk | At a step you choose | Set up per account. Default is agents reply. |
| 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.
When the schedule lives in a spreadsheet or another app, the agent has to message the dispatcher to answer a simple question, and the customer waits for both. Fieldproxy replaces that loop; the agent keeps the customer conversation.
Stays in Freshdesk
- The receipt acknowledgement and canned responses.
- Every reply to the customer, written by an agent or your Freshdesk automations.
- First response and resolution SLAs for support.
- CSAT and support reporting.
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 dishwasher that won't drain, and three customer questions
Say Brightwick Appliance Repair fixes domestic appliances under manufacturer warranty and runs support in Freshdesk.
- 1
The ticket and the receipt
Ticket #44107 from a customer, Mrs Adeyemi: dishwasher won't drain. Freshdesk sends its usual receipt. The agent, Kofi, walks her through clearing the filter; it doesn't help, and he ticks Send to Fieldproxy. - 2
Dispatch confirms
The Dispatch agent suggests Ines, who covers that postcode and has a drain pump in her van. The dispatcher approves for tomorrow 9:00 to 11:00, and a private note lands on the ticket. - 3
Question one
Mrs Adeyemi replies: when is someone coming? Kofi answers from the note: Ines, tomorrow between 9 and 11. - 4
Question two
Next morning Ines's earlier job runs long and the dispatcher moves the visit to 11:00 to 13:00. A new note lands. When the customer asks if they're still coming, Kofi already knows the new time. - 5
Question three
Ines checks in at 11:20, and the on-site note appears. She replaces the pump, adds her note, and the ticket is set to Resolved. Kofi's closing reply says what was replaced.
Result: Three customer questions were answered from the ticket without a single message to the field team, including one about a change the customer hadn't heard of yet.
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 Freshdesk side is the standard connection. Most of the time goes into job types and dispatch rules, because those decide how fast the first real answer exists.
- 1
Agree what agents need to know
Technician, time window, arrival and what was done, and whether any of it should reach the customer automatically. - 2
Connect Freshdesk
API key from an admin agent and the automation rule that sends tickets to Fieldproxy. - 3
Set dispatch rules
Which job types are assigned by rule and which wait for a dispatcher, and the technicians' skills and areas. - 4
Pick the notes
Which steps write private notes, and whether any step writes a public reply, set up per account. - 5
Test with your agents
Run real tickets through and let agents answer from the notes before going 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
- Customers often ask support when a technician is coming, and agents have to ask the field.
- Dispatch lives in a spreadsheet or a separate app support can't see.
- You want agents to own the customer conversation, with field facts on the ticket.
- Visits get rescheduled and customers hear about it late.
Probably not the right fit when
- Customers book visits themselves in an online booking tool and rarely contact support.
- Support and dispatch are the same person at the same desk.
- You want Fieldproxy to message customers directly instead of agents. That is possible but set up per account, and many teams prefer one voice on the ticket.
Straight answers
First response on Freshdesk field tickets: questions we get asked
Does Fieldproxy reply to the customer?
What does the agent see on the ticket?
How quickly does the scheduled note appear?
Can the customer get an automatic acknowledgement?
What if the time changes?
Can customers check progress themselves?
Does this change Freshdesk's first response SLA?
Can I ask Claude or ChatGPT when a technician is due?
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.
The first real answer, already on the ticket.
Tell us what customers ask while they wait. We show the field notes landing on your own Freshdesk tickets.
Get DemoLive within a day. Free, assisted migration. Unlimited users on one price per company.