FieldproxyIntegration guide ยท Zoho Desk

Dispatch technicians from Zoho Desk tickets, with every update back on the ticket

Keep Zoho Desk as your support desk and send the tickets that need someone on site to Fieldproxy. A tag, a field or a department marks a ticket as field work, and it becomes a job with the contact, the site and the asset attached. Fieldproxy schedules and dispatches it, the technician works it on the phone with GPS check-in, photos and a checklist, and scheduled, on the way and complete are added to the ticket as comments. When the job is done, the ticket moves to the status you choose, such as Resolved.

Fieldproxy is AI-native field service software, set up around how your team works and live within a day. It replaces the scheduling spreadsheet and any separate field app. Zoho Desk stays where customers raise tickets and agents answer them.

See your Zoho Desk tickets turn into jobs

Tell us which tickets need a visit today. We set it up on your own departments and fields before you commit.

Book your demo

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

Number of employees

How it works

From Zoho Desk ticket to finished visit, step by step

A typical setup. What marks a ticket as field work, the job types and the statuses written back are agreed with you.

  1. 1

    A ticket is marked as field work

    Zoho Desk agent, or a rule

    An agent adds a tag or sets a field such as Needs site visit, or the ticket arrives in a department that always needs a visit (installations, for example). Zoho Desk's webhook tells Fieldproxy. Tickets that can be solved remotely stay in Zoho Desk.
  2. 2

    The job is created with the site and asset

    Fieldproxy

    The contact, account, address, subject, description, priority and ticket ID are copied onto a new job. The account is matched to the customer and the address or a site field to the site record, with access notes and the assets installed there. A serial number or asset tag on the ticket attaches the asset and its history. If nothing matches, the job waits for the office with the reason.
  3. 3

    It is scheduled and dispatched

    Dispatcher, helped by the Dispatch agent

    The Dispatch agent suggests a technician by skill, distance and the day's load. A dispatcher approves, or routine job types are assigned by rule. Moves are previewed and can be undone. The ticket gets a comment: scheduled, with the technician and time.
  4. 4

    The technician heads out

    Technician, Android or iOS app

    The technician taps on the way, and the ticket gets a comment. The site notes, the asset's history and the job's checklist are on the phone, offline if signal drops.
  5. 5

    The visit is worked and proven

    Technician

    GPS check-in on arrival, the checklist with required photos and readings, parts from van stock, and the customer's signature. The job can't be completed until the required items are done.
  6. 6

    Complete, and the ticket moves

    Fieldproxy, written to Zoho Desk

    Complete is added as a comment with the technician's notes, and the ticket is set to the status you choose, such as Resolved. If a return visit is needed, it is added to the same job and the ticket says so.
  7. 7

    Billing from the job

    Fieldproxy

    Labour and parts on the finished job become an invoice with a payment link, or sync to QuickBooks, Xero or Sage.

What syncs

What moves between Zoho Desk and Fieldproxy, which way and when

Built on the Zoho Desk REST API and webhooks, with OAuth approved by a Zoho Desk admin.

WhatDirectionWhenDetail
Tickets marked as field workZoho Desk โ†’ FieldproxyWhen the tag, field or department matchesContact, account, address, subject, description, priority, attachments and the ticket ID become a job.
ScheduledFieldproxy โ†’ Zoho DeskWhen the dispatcher confirmsComment with the technician and the time window.
On the wayFieldproxy โ†’ Zoho DeskWhen the technician taps on the wayComment, so the agent can tell the customer someone is coming.
On siteFieldproxy โ†’ Zoho DeskAt GPS check-inKept on the job with the check-in time. Adding it as a comment is set up per account.
Ticket comments and job notesBoth waysAs they are addedKept in step, so an agent's comment reaches the technician and the technician's note reaches the ticket. Which comments are private or public is set up per account.
StatusFieldproxy โ†’ Zoho DeskOn completion, and at stages you mapYour own mapping between job stages and Zoho Desk statuses; on completion the ticket moves to the status you choose, such as Resolved.
Visit report and photosFieldproxy โ†’ Zoho DeskOn completionThe job report with photos, checklist and signature is on the job. Attaching or linking it on the ticket is set up per account.
Time on site and mileageFieldproxy โ†’ Zoho DeskOn completion; mileage per tripRecorded in Fieldproxy from check-in, check-out and GPS trips. Writing either to the ticket is set up per account.
Follow-up visitsFieldproxy โ†’ Zoho DeskWhen a return visit is bookedAdded to the same job, and reported on the same ticket.

One ticket links to one job, so updates always land on the right ticket.

See your own Zoho Desk tickets turn into jobs before you commit.

Get Demo

What stays, what moves

Zoho Desk keeps the tickets. Fieldproxy replaces the field tools.

Teams on Zoho Desk often tell us scheduling technicians isn't in their plan, or that it is in a higher tier they don't want to buy for a few dispatchers. So visits get booked in a spreadsheet and a group chat beside the ticket. Fieldproxy replaces that, and the separate field app if there is one, not Zoho Desk.

Stays in Zoho Desk

  • Customers raise tickets by email, portal, chat or phone.
  • Agents answer customers and own the conversation.
  • Your Zoho Desk departments, SLAs, assignment rules and blueprints for support work.
  • Ticket reporting for the support team.
  • The ticket stays the record the customer and the agent look at.

Moves to Fieldproxy, and what it replaces

Dispatch and the schedule

The spreadsheet or whiteboard beside Zoho Desk 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 solar inverter fault, from ticket to resolved

Say Sunvale Energy installs and services rooftop solar for homes and small businesses, and runs support in Zoho Desk with an Installations department and a Service department.

  1. 1

    The ticket

    Ticket #3391 in the Service department: "Inverter showing an error, no generation since yesterday," from a bakery on Mill Road. The agent checks the monitoring portal remotely, can't clear it, and adds the tag site-visit.
  2. 2

    The job

    Fieldproxy matches the bakery to its site record (roof access by the rear ladder, ask for the owner) and the inverter from the site's asset list, installed two years ago. The job is created in To schedule.
  3. 3

    Scheduled

    The Dispatch agent suggests Ravi, who covers that area and is certified for that inverter range, tomorrow 9 to 11. The dispatcher approves, and the ticket gets a comment: scheduled, Ravi, tomorrow 9 to 11.
  4. 4

    An agent's comment reaches the field

    The owner replies that the rear gate is locked until 9:30. The agent adds it as a comment, it lands on the job's notes, and Ravi sees it before he leaves.
  5. 5

    The visit

    Ravi taps on the way (comment on the ticket), checks in at 9:34, replaces a failed fuse, records the generation reading in the checklist and photographs the inverter display.
  6. 6

    Complete

    His note and Complete go to the ticket as a comment, and the ticket moves to Resolved. The fuse comes off his van stock.
  7. 7

    Billing

    The callout and the part go onto an invoice with a payment link and sync to the accounting system.

Result: The agent never booked a visit by hand, the gate time reached the technician without a phone call, and the inverter's history now shows this repair for the next visit.

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 Zoho Desk tickets

Described by kind of tool. Each fits some teams.

ApproachFits whenWhat you give up
Zoho Desk alone, with a tag and a spreadsheetA few visits a week by your own staffNo technician app, required photos, schedule view or stock. Dispatch lives in someone's head.
Zoho's FSM extension for Zoho DeskYou want to stay inside the Zoho suiteCheck it against your visit types, checklists, offline use, stock and contractors. Zoho's help says each FSM record links to only one ticket.
A configurable field service system connected to Zoho Desk (Fieldproxy)Visits need checklists, sites have access rules, contractors do some work and billing comes from the jobA second system to run. It replaces your field tools, so plan the switch-off of the spreadsheet and any old app.

Zoho FSM extension behaviour from Zoho's help article on installing the FSM extension for Zoho Desk, as of November 2026.

On Zoho CRM as well? Accounts, contacts and deals can connect too: see the Zoho CRM integration.

Setup

Connected, set up around your queues, live within a day

The Zoho Desk side needs an admin for a few minutes. The rest is done by Fieldproxy's team.

  1. 1

    A 30-minute call

    Which tickets need a visit, which fields carry the site and the asset, what goes back to the ticket and who sees it.
  2. 2

    Connect Zoho Desk

    A Zoho Desk admin approves the connection with OAuth.
  3. 3

    Choose the trigger

    Pick the tag, field or department that marks a ticket as field work.
  4. 4

    Map fields and statuses

    Ticket fields to the job, and job stages to the Zoho Desk statuses written back.
  5. 5

    Build the field side, test, go live

    Job types, checklists, technicians and skills, van stock and invoicing. Sites and assets come across with free, assisted migration. Run real tickets through, check the ticket, 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

  • Support runs in Zoho Desk and some tickets end in a technician visit.
  • Scheduling technicians isn't in your Zoho Desk plan, or the spreadsheet beside it has become the real schedule.
  • You need required photos, checklists and signatures before a job counts as done.
  • Contractors or technicians should work without Zoho Desk seats.
  • Stock, mileage or invoicing for visits lives in spreadsheets today.

Probably not the right fit when

  • Every ticket is solved remotely.
  • A few visits a month by one person.
  • You want everything, including field work, inside the Zoho suite and are happy with Zoho's own FSM extension.
  • You want to replace Zoho Desk itself. Fieldproxy keeps it as the support desk.

Straight answers

Zoho Desk and field service: questions we get asked

Can a Zoho Desk ticket create a field service job automatically?
Yes. You choose what marks a ticket as field work: a tag, a field value or a department. Matching tickets become Fieldproxy jobs with the contact, account, address and ticket ID. The rest stay in Zoho Desk.
What does the Zoho Desk agent see after the job is created?
Comments on the same ticket as the job moves: scheduled, on the way and complete, with the technician's notes. When the job is done, the ticket is set to the status you choose, such as Resolved, so the agent can answer the customer without asking the field team.
Is it a two-way sync?
Tickets come in, and job updates and the final status go back. Ticket comments and the job's notes are kept in step, with your own mapping between Zoho Desk statuses and job stages. Which other ticket fields should update the job after it is created is agreed per account.
Our Zoho Desk plan doesn't include scheduling. Does that matter?
No. Scheduling, dispatch, preventive maintenance and job cards run in Fieldproxy, and notes and status go back to Zoho Desk. Your Zoho Desk plan only needs to allow the API and webhooks for the connection.
Will a follow-up visit create a second job?
No. One ticket links to one job. A return visit, for a part that had to be ordered for example, is added to the same job and reports back to the same ticket.
Are updates visible to the customer?
Whether job updates are added as private or public comments is your choice per step, set up per account. Many teams keep scheduling and on-site updates private and let the agent send the customer reply.
How is this different from Zoho's own FSM extension for Zoho Desk?
Zoho's help pages describe an FSM extension that creates requests, estimates and work orders from a Desk ticket, with each FSM record linked to one ticket. Fieldproxy is a separate field service system set up around your workflow, with its own technician app, sites and assets, stock, invoicing and AI agents, connected to Zoho Desk through its API.
Do technicians need a Zoho Desk licence?
No. Technicians and contractors work in the Fieldproxy app. Fieldproxy is one price per company with unlimited users.
What does Fieldproxy need to connect?
A Zoho Desk admin approves the connection with OAuth. You then choose what marks a ticket as field work, how ticket fields map to the job, and which statuses are written back.
How long does setup take?
You are live within a day. The team maps your Zoho Desk fields and departments, builds your job types and checklists, and moves your sites and assets over with free, assisted migration.

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, Freshdesk, Zendesk and ServiceNow.

Keep Zoho Desk. Schedule the visit properly.

Tell us how a ticket becomes a site visit today. We show it running on your own departments and fields.

Get Demo

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