Zoho CRM for Real Estate Businesses in India: Complete Setup Guide
How to set up Zoho CRM for a real estate business in India. Covers lead…
Zoho FSM field service management is a purpose-built platform for companies that send technicians to customer sites. Whether your team installs HVAC systems, maintains commercial plumbing, deploys IT infrastructure, or services medical equipment, the core problem is the same: getting the right technician with the right parts to the right location at the right time, then converting that job into an invoice without manual data entry. Zoho FSM addresses each of those steps directly. This guide walks through how to configure it, dispatch work orders, equip your field team with the mobile app, and close the billing loop through Zoho Books.

Zoho FSM is a cloud-based field service management platform that handles the full service job lifecycle: customer request intake, work order creation, technician scheduling and dispatch, on-site job execution, and invoicing. It is part of the Zoho ecosystem, which means it integrates natively with Zoho CRM for customer records, Zoho Books for billing, and Zoho Inventory for parts management.
The platform is used across a wide range of field service verticals:
What these industries share is a dependency on accurate scheduling, real-time visibility of technician location, and rapid invoicing after job completion. Managing any of those three through spreadsheets or phone calls reliably fails once a team exceeds five or six field agents.
Before creating a single work order, you need to build the operational structure that determines who can do what job, where, and when. Zoho FSM handles this through three configuration layers: territories, skills, and availability.
Navigate to Settings > Field Force > Territories. Define territories as geographic zones, either by drawing boundaries on the map interface or by entering postal codes and region names. Territories control which agents are visible in the dispatch console when a work order is created for a specific location. This prevents a dispatcher in a multi-city operation from accidentally assigning a technician in one city to a job 200 kilometers away.
Under Settings > Field Force > Skills, create a skills library matching your service types. For an HVAC company, this might include skills like refrigerant handling certification, boiler servicing, ductwork installation, and electrical controls. Each agent profile then receives the relevant skills from that library. When a work order is created and tagged with a required skill, the dispatch console filters to show only qualified agents automatically.
Each agent has a working hours calendar and a leave calendar. Configure standard working hours under the agent profile, then record approved leave or scheduled training days in the leave calendar. The dispatch console respects these settings and will not schedule a work order during a technician’s unavailable hours unless a dispatcher manually overrides it.
The work order is the operational unit of zoho fsm field service management. Every job, whether it originates from a customer call, a CRM opportunity, or a preventive maintenance schedule, becomes a work order before any field action occurs.
Work orders can be created manually from the Work Orders module, generated automatically from a service request submitted by a customer through the self-service portal, or triggered by a preventive maintenance schedule. A work order captures the customer account, site address, service type, required skills, priority level, preferred time window, and any asset being serviced.
The dispatch console shows a calendar view of all agents in a territory alongside a queue of unscheduled work orders. Dispatchers assign work orders by dragging them onto an agent’s time slot on the calendar. The system checks for skill match, territory coverage, and availability conflicts before confirming the assignment. On confirmation, the assigned technician receives a push notification on the mobile app with the job details.
The technician navigates to the customer site using the address in the mobile app, checks in on arrival (which records GPS-stamped arrival time), and works through the job checklist configured for that service type. They log parts consumed from their van stock, upload photos of the equipment condition before and after service, and record any notes relevant to the next visit.
On job completion, the technician presents the mobile app to the customer for a digital signature. The signed record is time-stamped and stored against the work order. A job completion email with a summary is sent to the customer automatically if configured. The work order status then changes to Completed, which triggers the invoicing step in Zoho Books if the integration is active.

The Zoho FSM mobile app runs on iOS and Android. It is the primary interface for field technicians throughout the workday and is designed to function with minimal data entry from the technician’s side.
On logging in, a technician sees a chronological list of their assigned jobs for the day with customer name, address, service type, and required arrival window. Each job card expands to show the full work order details, service history for the asset being serviced, and any pre-filled checklist items.
Technicians log parts consumed during a job by searching the parts catalog from within the app. If the part is in the technician’s van stock, it is deducted from their inventory record automatically. If the part needs to be ordered, the technician can raise a parts request from the app, which creates a purchase requisition in Zoho Inventory.
The app records GPS location in the background while the technician is clocked into their shift. The dispatch console shows each agent’s current location on a map in real time. Travel time between jobs is tracked and logged, which feeds into the profitability reporting for each work order (labor cost includes drive time, not just on-site time).
The most financially impactful part of a zoho fsm field service management deployment is usually the Zoho Books integration, because it eliminates the billing lag that costs service businesses revenue.
Without integration, the sequence is: technician completes job, drives back to the office, submits a paper or email report, office staff creates an invoice manually, invoice is sent days later. With the integration active, the sequence is: technician marks job complete and collects signature, work order status updates to Completed, Zoho Books creates a draft invoice automatically using the parts and labor recorded in the work order, office staff reviews and sends.
Once active, the average time from job completion to invoice delivery drops from 3 to 5 business days to under 2 hours for most teams. For a service company completing 150 jobs per month at an average invoice value of $400, cutting the billing delay by four days recovers meaningful cash flow on an ongoing basis.
Choosing between these three platforms comes down to company size, budget, and how deep your existing software ecosystem goes.
| Criteria | Zoho FSM | ServiceTitan | Salesforce Field Service |
|---|---|---|---|
| Target company size | 5–200 technicians | 10–500+ technicians | 50–5,000+ technicians |
| Starting price | ~$35/agent/month | ~$125/agent/month | ~$150/agent/month |
| Billing integration | Native (Zoho Books) | Built-in | Requires Salesforce Billing |
| CRM integration | Native (Zoho CRM) | Built-in | Native (Salesforce CRM) |
| Mobile app offline mode | Yes | Yes | Yes |
| AI scheduling optimization | Basic | Advanced | Advanced (Einstein) |
| Implementation complexity | Low to medium | Medium to high | High |
ServiceTitan is purpose-built for trades businesses and includes revenue-focused features like sales proposals and financing integrations that Zoho FSM does not have. Salesforce Field Service is the choice for enterprise operations that need the full Salesforce platform for customer management, analytics, and AI-assisted scheduling at scale. For most businesses with 5 to 100 technicians that are already in the Zoho ecosystem, Zoho FSM covers all operational requirements at a fraction of the cost of either alternative.
Does Zoho FSM work without an internet connection for field technicians?
Yes. The Zoho FSM mobile app has an offline mode. Technicians can view job details, update work order status, log parts used, and collect customer signatures without a connection. The data syncs automatically once the device reconnects to the internet.
Can Zoho FSM handle recurring maintenance schedules?
Yes. Zoho FSM supports preventive maintenance schedules where work orders are created automatically on a set frequency, daily, weekly, monthly, or custom intervals. Each recurring work order inherits the asset, location, and skill requirements from the original configuration.
How does Zoho FSM route and assign work orders to the nearest available technician?
The dispatch console in Zoho FSM displays agent locations on a map in real time using GPS data from the mobile app. Dispatchers can drag and drop work orders to agents manually, or use the auto-assign feature which allocates based on proximity, skill match, and current workload.
Is Zoho FSM suitable for companies with fewer than 10 field technicians?
Yes. Zoho FSM’s pricing starts at around $35 per agent per month, and there is no minimum agent count. Small teams benefit from the same dispatch, mobile, and invoicing features as larger operations. The setup time for a team of 5 to 10 technicians is typically under two weeks.
What is the difference between Zoho FSM and Zoho Desk for field service?
Zoho Desk is a customer support ticketing system designed for handling inbound queries and support cases. Zoho FSM is purpose-built for managing physical field jobs, including work order creation, technician dispatch, parts inventory, GPS tracking, and on-site customer sign-off. For businesses that send technicians to customer sites, Zoho FSM is the appropriate tool.
Zoho FSM field service management works best when the territory structure, skills library, and Zoho Books integration are configured before the first work order goes live. Teams that take a week to set up the operational data correctly typically see dispatch efficiency and billing speed improve within the first month of use.
Our team builds systems that actually work. No fluff, just honest architecture and clean implementation.