Freshdesk Field Service
Some tickets can't be closed from a desk. Somebody has to drive somewhere with a part. That's the entire case for Freshdesk field service management.
What Freshdesk field service management adds
Freshworks offers field service management as a capability that sits alongside its helpdesk products rather than inside the base ticketing product. Whether it comes as an add-on, a bundle or a separate subscription depends on what you're on, so get that answered by sales rather than from an article.
What it adds conceptually is consistent wherever you buy it.
The connective tissue is that the customer-facing ticket stays the customer-facing ticket. The visit hangs off it. That separation is what stops your support queue filling up with tickets that are open for a fortnight because a van is booked for Thursday.
The signals you need it
Most support teams don't, and shouldn't buy it. These are the honest triggers.
Two or more of those, and the tooling pays. One of them, and you can probably fake it with a custom status and a shared calendar for another year.
Faking it before you buy it
I would always try the cheap version first, because it tells you what you actually need.
Create a ticket status that means scheduled for a site visit, and configure it so the SLA clock does not run while a ticket sits there. That one change makes your metrics honest immediately, and it costs nothing. The ticket status guide covers how the clock behaviour is set.
Add fields for the visit date, the assigned engineer and the site address. Build a view filtered to scheduled visits, sorted by date. That is a scheduling board, badly, and it works up to a handful of visits a week.
Where it falls over is predictable and worth watching for. Double bookings, because nothing enforces capacity. Travel time, because a view has no map. And the engineer's experience, because you are asking someone in a van to use a full helpdesk interface on a phone. When those three start hurting, buy the real thing.
Freshdesk or Freshservice underneath
Worth being clear about which product the field work hangs off, because they are different businesses.
If the person raising the job is an external customer with a service contract, Freshdesk is the natural home. The ticket is a customer conversation, the visit is fulfilment.
If the person raising it is an employee and the work is infrastructure, an office move, a hardware swap, a site network install, then Freshservice is the better base, because you also want the asset record updated when the job closes. The Freshservice hub and the product comparison both go into that split.
Plenty of organisations end up with both, and that's fine as long as somebody owns the boundary. What you must not do is run field jobs in one product and the asset register in another with no link between them, because the first time a technician replaces a part, your inventory quietly becomes wrong.
What to measure once it's running
Four numbers, and they are not the ones people start with.
Everything else is decoration. Get first-time fix moving and the rest tends to follow.
Frequently asked questions
What does Freshdesk FSM add to a ticket?
Freshdesk service tasks: an appointment, a technician and a location attached to the ticket. Freshdesk FSM is a separate module, and without it a field visit is just a ticket somebody remembers.
Does Freshdesk include field service management?
Not in the base ticketing product. Freshworks offers field service capability alongside its helpdesk products, and how it is packaged depends on your subscription, so confirm the current arrangement with Freshworks directly.
What is a service task?
A unit of on-site work that hangs off a ticket, with its own status, owner and schedule. It keeps the visit separate from the customer conversation so neither distorts the other.
Do field technicians need a full agent licence?
Typically not. Field technician access is licensed differently from a full support agent, which is a large part of why the capability is worth buying rather than improvising.
Can I manage site visits in Freshdesk without field service management?
Up to a point. A scheduled status that pauses the SLA clock, a few custom fields and a filtered view will handle a handful of visits a week. Double bookings and travel planning are where it breaks.
Should field service run on Freshdesk or Freshservice?
Freshdesk when the requester is an external customer under a service contract. Freshservice when the requester is an employee and the job also needs an asset record updated.
Duplicate jobs, duplicate visits
When a customer chases a scheduled visit by email, you get a second ticket. Ticket Merger merges it into the original automatically, so nobody dispatches twice.
Start free trial14-day free trial. No credit card required.