FAQ
If you're running a small crew on pen-and-paper, spreadsheets, or a legacy system, these are the five things you actually need to hear before you switch.
About ten minutes. Add your technicians, drop a pin on your service area, and import your active jobs from a spreadsheet or CSV — no IT project, no installer, no onboarding call required. Most crews are dispatching their first job the same afternoon they sign up.
Yes. Upload your customer list, job history, and technician roster as a CSV or spreadsheet on day one, and we'll map the fields for you. Historical jobs stay searchable, so you don't lose anything from the last five years, and there's no double-data-entry while you get comfortable with the new system.
A flat monthly subscription — no per-job fees, no per-technician add-ons, no surprise upgrade charge when you grow. It's cheaper than a part-time dispatcher, and the ROI shows up fast in fewer missed appointments, faster invoicing, and the no-shows you recover on the operations dashboard. See the three tiers on the pricing page.
Yes — the technician mobile view is built for thumbs, not training. One-tap status updates from en-route to arrived to complete, and finishing a job requires a quick photo plus a short note, so you get proof of work without chasing your techs. Crews that pushed back on previous tools usually adopt FieldOS within a day.
Yes. Your schedule and login sessions live in a managed PostgreSQL database hosted on Render, so they survive server restarts, redeploys, and the kind of browser crashes that used to wipe in-memory tools. There is no local-only state — if your laptop dies at 7 a.m., your dispatcher logs in on another machine and the day is exactly where they left it.
Still on the fence? See it on your own jobs.
Book a 15-minute walkthrough or start a free trial and run a real scheduling day before committing.