Field Service

Field Service is for businesses that send people to a customer's site. You create a job for the work, say who is doing it and when, and the technician gets a work order describing the scope. From there the job moves through a fixed set of statuses until it is completed, and every change is written back to the same job record the office and the dispatcher are both looking at.

There are two office screens and one on-site screen. Field Service is the job list where work is created and tracked, Dispatch is the board where you move jobs between technicians and times, and a separate full-screen capture page is what a technician opens on a phone to file an inspection or a service report against the job.

What's included

Page	What it's for
Field Service	The Field service jobs list, status filters, and the New job form
Dispatch	The Dispatch board for dragging jobs between technicians, times, and days
The field capture page	What a technician fills in on site. It is a full-screen page with no dashboard sidebar, at /field in your workspace

Getting started

1. Open Field Service from the sidebar.
2. Select New job.
3. Pick a Customer. The list is your CRM contacts, so if it is empty, follow Add one in CRM first.
4. Choose a Service location, or pick + New location… and enter the Address for a new one.
5. Enter a Service type, for example HVAC repair, and set Scheduled for.
6. Choose a Technician, or leave it on Unassigned and assign it later from the board.
7. Fill in Scope and Instructions under Work order, then select Create job.

Creating a job

Customer and Service type are the only required fields. Everything else can be filled in later from the job's Edit screen or by dragging the job on the dispatch board.

Service location is where the work happens, and it belongs to the customer you picked. Choosing + New location… opens a short sub-form with Label (for example Main office), Address, City, State, and Postal code. Only the address is required, and the location is saved to that customer so it is there next time.

The Work order section is the technician's copy of the job. It contains what the technician sees on site, without customer pricing. Scope defaults to the description when left empty. You do not have to create the work order separately; it is generated with the job, which is why the form is headed "The work order is generated automatically when the job is created."

Once created, the job opens on its own page with the work order, a Documents area for files, and a Field submissions area for anything the technician sends in from site.

The job lifecycle

A job is always in one of five statuses: Scheduled, Dispatched, In progress, Completed, or Cancelled. New jobs start at Scheduled.

The path forward is fixed and only moves one way:

• Scheduled can become Dispatched.
• Dispatched can become In progress.
• In progress can become Completed.
• Any job that is not yet finished can become Cancelled.

Completed and Cancelled are the end of the line. A job cannot be moved backward, reopened, or jumped forward past a step, and the server refuses the change even if something tries it directly.

To change status, open the job and use the Move to: row at the top. Only the moves that are actually allowed from the job's current status are offered, so on a Dispatched job you see In progress and Cancelled and nothing else. Cancelling asks you to confirm first, under Cancel this job?: "The job moves to Cancelled and can't be reopened."

On the jobs list, the filter buttons across the top are All plus one per status, and the table columns are Job, Customer, Status, Scheduled, and Technician. A job with nobody on it reads Unassigned.

Assigning and dispatching from the board

Open Dispatch from the sidebar to get the Dispatch board, described in the product as "Drag jobs between technicians and time slots; every move updates the job record." That is the important part: the board is not a separate plan. Every drag changes the real job.

Use Today, and the arrows either side of it, to pick the day. The view buttons switch what the board shows:

• Grid: one column per technician, one row per working hour from 7 am to 7 pm, plus an Unassigned lane on the left. Jobs outside those hours sit in an Other row underneath.
• Date: a week at a time, with an unscheduled backlog strip for work that has no date yet. Drag a job from the strip onto a day to schedule it.
• Service and Location: the same day's jobs grouped by service type or by site.
• Map: grouped by service location for now. The page says so: "Map pins arrive with geocoding (F5). Until then, jobs are grouped by service location below."

What a drop does depends on where you drop it:

• Onto a time slot in the grid: assigns the job to that technician and moves it to that hour.
• Onto a technician's lane heading: assigns the job to them and keeps its existing time.
• Onto a day in the Date view: keeps the technician and the time of day, and moves it to that date.

A technician who has left your team still gets a lane, labeled Former teammate, so their jobs can be dragged off it.

To move a whole day's work at once, select Move a tech's day. Pick the Technician, a From day, and a To day, then Move day. As the dialog says, it moves "every open job a technician has on one day to another day, keeping the same times. Jobs already started or finished stay put." When it finishes you are told how many jobs moved and how many were skipped.

Editing and completing a job

Edit on the job page changes the job's details: Service type, Service location, Technician, Scheduled for, and Description. Status is deliberately not on this form: "Change the job's details. Status changes happen on the job page." Leaving the location or technician on Keep current location or Keep current technician leaves them as they are.

The work order is edited separately, with Edit inside the Work order card, which lets you revise Scope and Instructions while the job is running. The card reiterates that scope and instructions are for the technician and never show customer pricing.

To finish a job, move it to In progress when work starts and then to Completed. Nothing else is required and nothing is auto-completed for you; a job sits in In progress until somebody moves it. Files you want kept with the job go in the Documents area, which files them under Field Service Jobs.

Field submissions

Each job page has a Field submissions panel. It is a read-only record of what was filed from site against that job: the form values, who submitted them, and when. The office does not edit a technician's submission.

To file a submission, open /field in your workspace while signed in.

1. Under Link a job (optional), choose the job. Linking it makes the submission visible to the office on that job and gives photos a job to attach to.
2. Choose Equipment Inspection or Service Report and complete the required fields.
3. Allow camera or location access if you want to capture a photo or include GPS. You can also choose an existing photo. These permissions belong to your browser and device.
4. Select Submit and wait for confirmation. The form locks while it saves, then returns to Field capture after success.

An internet connection is required. These forms do not save drafts or queue submissions for later sync. If saving fails, your entries stay on the open form. If the report saved but a photo failed, keep the fields unchanged and retry from that form; SaaSy skips the photos already acknowledged. Before reloading or starting another capture after an uncertain result, check the job's Field submissions so you do not file it twice. Photos need a linked job; a standalone capture saves the report without uploading its photos.

On a phone

SaaSy installs to a phone home screen as an app, and the job pages are usable there. There is a related surface at /field/capture, Capture photos, for photographing jobsite work. Note that it files photos to a CRM project rather than to a field-service job. On Android you can share a photo into SaaSy from the operating system's share sheet; on iPhone and iPad that is not available, and the in-app camera is the way in.

Availability

The Field Service pages belong to the Service Operations module, which is on by default for the SaaS, Manufacturing, and General industry packs only. Agency, Professional services, E-commerce, Construction, and Nonprofit hide it. That hiding is cosmetic. Switch it back on under Settings → Navigation, and the pages work if you have the URL either way.

Field Service is a paid add-on excluded from every plan, including Starter, Growth, and Scale. It is flat-rated, and bought on its own it is $79/mo. You buy it from the add-on page itself with Add to subscription, which notes that it is "Billed as a flat-rate add-on to your current plan. Cancel anytime from Billing." Access unlocks straight away, without a reload. Access is also checked on the server, so the add-on has to be active before the jobs, dispatch, and capture pages return any data.

One thing that looks wrong and is not: if you told us at onboarding that you do on-site work, the Field Service and Dispatch items appear in your sidebar before you have bought anything. Seeing the item does not mean your workspace has the feature. Opening it shows the add-on page rather than the job list. That is expected, not an error.

See Modules, packs, and plans for how visibility and entitlement interact.