FieldproxyFreshdesk workflow ยท Feedback after the visit

Ask how the visit went, and keep the answer on the job

Freshdesk's satisfaction rating measures the support conversation. It doesn't tell you how the visit went or which technician did it. With Fieldproxy, a job that started as a Freshdesk ticket can send the customer a short feedback form after it is completed, built on your own forms, and keep the answer on the job, so it can be read by technician, job type, site or asset. Exactly when it is sent and what it asks is set up per account. The ticket is still set to Resolved from the job, and Freshdesk's own CSAT keeps working as it does today.

Part of the Freshdesk integration. Fieldproxy replaces the separate survey tool and the spreadsheet that matches answers to technicians, set up around your own forms and live within a day.

See feedback kept against your jobs

Tell us what you want to know after a visit. We set up the form and when it goes out.

Book your demo

60 minute video call ยท Step 1 of 2: your details, then pick a time

Number of employees

How it works

From finished visit to feedback you can act on, step by step

The flow is deliberately simple. The value is in keeping the answer next to the job it is about.

  1. 1

    The job is completed with proof

    Technician, Android or iOS app

    Required checklist items, photos and the customer's signature are done before the job can be completed.
  2. 2

    The ticket is closed from the job

    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. Freshdesk's own CSAT runs as usual.
  3. 3

    A feedback form is sent

    Fieldproxy, by your rule

    A short form about the visit goes to the site contact. Timing, channel and which job types get one are set up per account.
  4. 4

    The answer lands on the job

    Fieldproxy

    The answer is stored on the job with the technician, job type, site and asset, so it can be read in any of those ways later.
  5. 5

    Poor answers reach a person

    Service manager, or the owner you choose

    A low rating or โ€œnot fixedโ€ can be flagged to the person you choose, for example by the Watcher agent. They call the customer and, if needed, raise a return visit on the same job.
  6. 6

    A return visit reports to the same ticket

    Fieldproxy, written to Freshdesk

    Because one ticket links to one job, a return visit writes its notes to the same Freshdesk ticket, with the status you choose.

What syncs

What moves between Freshdesk and Fieldproxy, which way and when

Feedback is mostly a Fieldproxy concern. The Freshdesk side is the normal close of the ticket, plus whatever you choose to copy back.

WhatDirectionWhenDetail
Ticket and contactFreshdesk โ†’ FieldproxyWhen the ticket is sentThe contact becomes the site contact who gets the form.
Technician's notesFieldproxy โ†’ FreshdeskAs they are addedPrivate notes on the ticket.
Ticket statusFieldproxy โ†’ FreshdeskWhen the job is completeResolved, or a status you choose. Freshdesk's CSAT runs from here as usual.
Feedback formFieldproxy โ†’ FreshdeskAfter completion, by your ruleSent to the customer from Fieldproxy; timing and channel set up per account.
Feedback answer on the ticketFieldproxy โ†’ FreshdeskWhen the customer answersCopying it to the ticket as a private note is set up per account.
Return visitFieldproxy โ†’ FreshdeskIf raisedNotes and status go to the same ticket.

See your own Freshdesk tickets turn into jobs before you commit.

Get Demo

What stays, what moves

Freshdesk keeps the tickets. Fieldproxy replaces the field tools.

Teams usually measure visits with a separate survey tool and then try to match answers to technicians in a spreadsheet. Fieldproxy replaces both because the form and the answer sit on the job. Freshdesk keeps measuring support.

Stays in Freshdesk

  • Freshdesk's satisfaction survey on the support conversation.
  • Agent follow-up on the ticket.
  • Support reporting and CSAT dashboards.
  • Reopened tickets, handled by agents as today.

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 week of visits, and the one that wasn't fixed

Say Harrowgate Vending services coffee and snack machines in offices and runs support in Freshdesk. They send a two-question form the morning after each breakdown visit: Is it working now? Anything else?

  1. 1

    The visit

    Ticket #7730 from Quillon Insurance: snack machine not taking cards. Technician Dara replaces the card reader, gets the office manager's signature, and the ticket is set to Resolved.
  2. 2

    The form goes out

    Next morning the office manager gets the form. She answers: not working, the reader rejects contactless.
  3. 3

    The flag

    The "not fixed" answer is flagged to the service manager, Wren. She calls the office, then raises a return visit on the same job.
  4. 4

    The return visit

    Dara goes back, updates the reader's firmware and records it. A note goes to ticket #7730 and the status is set to Resolved again.
  5. 5

    The week in review

    Wren reads the week's answers by technician and machine model and sees two other complaints about the same card reader model, so she asks the supplier about it.

Result: A fix that didn't hold was caught the next morning instead of by an angry email a week later, and the pattern across one reader model showed up because answers sat on the jobs.

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 form and the rule take an afternoon to agree. The Freshdesk side is the standard connection.

  1. 1

    Write the questions

    One to three questions about the visit. We build them as one of your Fieldproxy forms.
  2. 2

    Pick when it goes

    Right after completion or the next day, and for which job types.
  3. 3

    Decide who hears bad news

    Which answers flag a person, and who that person is.
  4. 4

    Connect Freshdesk

    API key and automation rule, and whether answers should be copied to the ticket.
  5. 5

    Test on real jobs

    Send the form on a few real jobs to your own team first, 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 want to know how visits went, not just how support answered.
  • Feedback currently comes through a separate survey tool that doesn't know which technician went.
  • A fix that doesn't hold tends to come back as an angry email days later.
  • You want to compare feedback across technicians, job types or equipment models.

Probably not the right fit when

  • Freshdesk's own satisfaction survey already tells you what you need.
  • Your visits are rare enough that a phone call after each one is simpler.
  • You are looking for a tool to collect public reviews. That isn't what this is.

Straight answers

Feedback after field visits from Freshdesk: questions we get asked

Does Freshdesk's own satisfaction survey still work?
Yes. Freshdesk keeps measuring the support conversation as it does today. Feedback about the visit is a separate question, about the technician and the work, and is kept against the job in Fieldproxy.
What can the feedback form ask?
It is one of your own Fieldproxy forms, so it asks what you decide: a rating, a yes or no on whether the problem is fixed, or a comment. Keep it short; one or two questions get answered more than ten.
When is it sent?
After the job is completed. Whether it goes straight away, the next day, or only for certain job types, and by which channel, is set up per account.
Where is the answer kept?
On the job, so it can be read against the technician, job type, site and asset. Copying the answer back onto the Freshdesk ticket as a private note is set up per account.
What happens with a poor answer?
You decide at setup who should see it. A common choice is to flag it to the service manager so they can call the customer and, if needed, raise a return visit on the same job and ticket.
Can the customer sign off on site instead?
Yes. Many teams ask the customer to sign on the technician's phone at the end of the visit, with their name, and use the follow-up form only for jobs where the customer wasn't there.
Does this ask customers for public reviews?
No. This page is about feedback on the visit, kept for your own team. Fieldproxy doesn't add review requests unless you set one up yourself.
Can I ask Claude or ChatGPT about feedback?
Yes. Through Fieldproxy's MCP server, Claude, ChatGPT or Copilot can read feedback on jobs, for example the comments on last month's visits for one customer, with a confirm step before any change.
How long does it take to set up?
You are live within a day, including the Freshdesk connection, the feedback form and the rule for when it is sent.

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.

Hear about the visit, not just the ticket.

Tell us what you want to know after a visit. We set up the form and the rule on your own jobs.

Get Demo

Live within a day. Free, assisted migration. Unlimited users on one price per company.