Field Service
Field Service is ERPat's module for businesses that send people to customer locations — appliance repair, HVAC, IT support, facilities, installations, pest control and similar. It connects the office, the field technician and the customer on one record, from the first request to the paid invoice, with a branded customer portal and an installable offline technician app.
What This Module Is For
Small and multi-branch service organizations lose time and money to scattered coordination — phone calls, spreadsheets and paper job sheets passed between customer service, dispatch, technicians, inventory and billing. Field Service replaces that with a single operational record so nothing is dropped between "customer called" and "invoice paid."
A request comes in, becomes a scheduled work order, is assigned to a qualified technician, is carried out on site (with tasks, photos, signature, parts and time captured — even offline), reviewed, turned into an invoice, and paid. Customers can request and track service through the portal without calling the office.
Module at a Glance
Where users usually start
- Dashboard (open requests, jobs today, SLA risk, unbilled work)
- Service Desk — Service Requests → convert to a Work Order, and the Service Locations they happen at
- Dispatch Board — the board (Pro) and the Calendar
- Quotes & Billing — Quotations and the Billing Queue
- Agreements — Service Contracts and SLA Policies (Pro)
Primary user groups
- Business owners monitoring service work and revenue
- Dispatchers and service coordinators
- Field technicians and crews
- Inventory, billing and quality staff
- Customers, through the public service portal
Lite and Pro
Field Service runs in two modes, controlled by feature flags — not separate products.
Lite SME defaults
Service requests, work orders, basic scheduling, mobile execution, quotes, billing and a basic customer portal. This is the default on install.
Pro Multi-branch
Adds the drag-and-drop dispatch board, SLA policies with escalation, service contracts, preventive maintenance, van stock, crews and route recommendations. Enabled per tenant in Settings.
Documentation Map
Getting Started
Enable the module, run migrations, assign permissions, choose Lite or Pro, and prepare templates, skills, technicians, customer sites and assets.
Daily Operations
The service-to-cash SOP: intake and triage, convert to a work order, schedule and dispatch, execute on site, review, quote, bill, plus the portal and offline app flows.
Administration
Feature flags, permissions, settings, notifications, cron jobs, the AI-assist opt-in and data-privacy acknowledgement, and the two API stacks.
Reference
Screens, the work-order lifecycle statuses, the fs_* data areas, cron jobs, widgets, the profile tab and API endpoints.
Research Evidence
The live module files inspected to write this guide — controllers, models, migrations, jobs, config sidecars and libraries.
FAQ & Troubleshooting
Common issues (no availability slots, parts not reducing stock, can't invoice, AI unavailable), a glossary and support escalation.
Operator Outcomes
- Understand what the module owns and where it appears in the ERPat workspace.
- Know the first setup tasks required before staff use live data.
- Run the request → work order → assign → complete → approve → bill flow consistently.
- Identify which permissions, settings, portal, APIs, jobs or widgets need administrator review.
- Recognize how Field Service reuses Clients, Warehouse, Finance, Forms, Assets and Notifications instead of forking them.