Field service task records

What the tasks require

Rubric: Field app · Scheduling & dispatch

• T-01: From signup to the first job scheduled, including importing the 25 customers from CSV

  Customers imported with their service locations; first job scheduled

• T-07: Schedule 8 jobs across 3 techs; an emergency call bumps one

  Rescheduled, and the customer is notified automatically

• T-09: On a phone: open the job, see equipment history, add photos, notes and a checklist, capture a signature; repeat offline

  Everything syncs after reconnecting, with no data loss

Products and task evidence

Housecall Pro advertises a 14-day free trial, but its terms say the service is offered to users who reside in the US or Canada, and when we signed up on September 28, 2026 the onboarding form did not accept our Spanish phone number. Our lab is in Spain, so we have not run our tasks on it. What this page shows comes from public sources and is marked as documented, not tested.

Housecall Pro: insufficient evidence for these tasks.

Kickserv: insufficient evidence for these tasks.

ServiceTitan: insufficient evidence for these tasks.

Workiz: insufficient evidence for these tasks.

Price checked

Not verified

Last tested

2026-10-05

Last edited

2026-10-09

Profile verdicts

Recorded limitations

• Your payer is often not the owner of the service location: in our trial Jobber billed the client that owns the property, so a property manager's unit needed a workaround that either duplicates the location or demotes the tenant to a contact (T-03).
• You track individual units by serial number: Jobber had no equipment record in our trial, and history lives on the property, not the unit (T-04).
• Your customer list already has property managers or landlords: the importer takes one row per property and cannot link the payer, so that structure is rebuilt by hand after import (T-01, T-03).
• You expect the app's search to find a job by its number: in our test it returned the customer and the address, not the job (T-09).
• You want the displaced customer told automatically when an emergency bumps their slot: the reschedule notice is a manual send (T-07).
• You need card payments working on day one: in our trial only cash, check and manual payment records were available, because Jobber Payments was not set up on the account (T-10).
• You are counting on the lowest plan: the features we tested put a contractor on Grow, $199 a month for one person at the time of our check (T-16).
• You need per-unit history right away: the register showed our condenser with its serial, but nothing can be recorded against it until a ServiceM8 QR label is scanned on the unit (T-04).
• You expect the payer and site structure out of the box: as the product comes, billing another address is set per job and every unit address is retyped; the Client Sites add-on support described is untested by us (T-03).
• You expect offline work to sync on its own: in our test nothing uploaded after reconnecting until the app was closed and reopened, so a technician who waits for the sync may not see offline work (T-09).
• You bill replacements as percentages: the deposit is a hand-priced line that needs an item code, not a share of the job (T-08).
• Your customer list has several rows per customer: the importer merged same-name rows without warning and kept only the last address (T-01).
• You want equipment history without labels: each unit needs a ServiceM8 QR label scanned on site before any service can be recorded against it (T-04).
• Your office forces emergencies into full slots: in our run the displaced job dropped out of the day view, with no conflict marker on the board (T-07).
• You want card payments without extra setup: with no gateway active, the phone only recorded a card or cash amount by hand (T-10).
• You work from an Android phone: the full app is iOS, and the Android app is a separate "Lite" version we have not tested (T-16).

Related tool