TechAppForce

Service and operations

Field service and work orders

Schedule, dispatch and close out work orders, then bill for them on time.

Book a demoSee how it runs
  1. Requested
  2. Scheduled
  3. Dispatched
  4. On site
  5. Completed
  6. InvoicedDone
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
Jobs are booked on a whiteboard and confirmed by phone. Technicians report back by text, extra work is agreed on site with no record, and invoices go out weeks late because the paperwork is still in a van.
Who feels it: Service managers, dispatchers and field technicians

How it runs on TechAppForce

A day with it, step by step

Amber steps wait in a person's work inbox; everything else moves on its own.

  1. A job is bookedA heating and cooling contractor takes a call about a broken air-conditioning unit at an office. The dispatcher creates the work order.
  2. DispatchOn the scheduler, she drags the job to a technician with a free slot that afternoon. He is notified and the customer gets the visit time by email.
  3. Extra work on siteApprove or rejectThe technician finds a failed compressor, which takes the job over its estimate. The service manager approves the extra cost before he starts.
  4. CompletedAfter the visit, the technician adds photos and the parts he used, then marks the job completed. The job sheet PDF is generated.
  5. Billed the same dayCompletion sends the work order to the invoicing system, and the invoice goes out the same afternoon.
Illustration. The organisation and people are invented.

What gets configured

Settings you can read, change and release

No code for any of this, unless a rule truly needs it.

Records 4

  • Work order5 fields + history, files, comments
  • Site4 fields + history, files, comments
  • Visit5 fields + history, files, comments
  • Part used4 fields + history, files, comments

Stages 6

  1. Requested
  2. Scheduled
  3. Dispatched
  4. On site
  5. Completed
  6. Invoiced

Automatic 3

  • ScheduleScheduling a work order notifies the technician and emails the customer the visit time
  • WorkflowCompleting a work order sends it to your invoicing system over HTTP
  • WorkflowCompleted jobs not invoiced after two days are flagged to the service manager

Screens and reports 5

  • Scheduler of technicians and visits for the dispatcher
  • Work order view with site notes, photos and parts used
  • Data grid of jobs by stage for the day
  • Job sheet as a PDF, attached to the work order
  • Weekly jobs completed and parts used by technician, in Excel
Who approves, in detail

Extra work that takes a job over its estimate goes to the service manager role before the technician carries on. Above a larger amount, the account manager named on the customer record approves as well.

When the rules change

Bring your version of this.

A change a few months in is a reviewed release, not a rebuild. We will configure your version with you in a demo.

Book a demoAll use cases

Release: Lifecycle: work order

Stages
Unchanged: On site · Completed
Added: + Awaiting parts
Fields
Added: + Warranty job (yes or no)
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release
Illustration.