Send your field team the right job

A field service app runs the work your team does at customers’ homes and sites. It takes the booking, sends the job to the right technician, gives them what they need on their phone, and closes the job with proof, a report and an invoice.

It usually has three sides. The office works from a dispatch board that shows every job and every technician for the day. Technicians work from an app with their jobs, directions, checklists and a way to record the work. Customers book, hear who is coming and receive the report, on WhatsApp, by text or on your website.

The value is in the rules between those sides: who gets which job, what must be recorded before a job can close, when a contract visit is due, and what happens when a technician is running late.

It pays off first for businesses whose technicians make several visits a day: AC and appliance service, solar installation and maintenance, lifts, pest control, security systems, water purifiers, medical equipment, facility management and home services.

The signs are the same everywhere. Jobs are handed out on WhatsApp each morning and rearranged all day. Technicians call the office for addresses and history. Repeat visits happen because the right part or the right skill wasn’t on the first one. Service reports come back on paper, so invoices go out late. Contract visits are tracked in a diary, and the customer notices a missed one before you do.

For a home services company in Austin, every booking used to depend on a phone call and a string of text messages, and each job was offered to pros one text at a time. We built a pro app, a dispatch board and job matching, and the team now runs the day from one board instead of a stream of messages.

Matching starts with a few plain questions: who has the skills for this job, who covers this area, and who is free at that time. Workload, the parts in each van and the customer’s history can count too, such as sending the technician who fitted the equipment last year.

Jobs can be assigned by the office or offered to technicians, who accept them in the app. In Austin, each booking is offered to pros who cover that zip code and service and are free at that time, best-rated first; the first to accept takes the job, and if nobody accepts in time it appears on the dispatch board for the team to place by hand.

Route planning comes next. Once each technician’s jobs are known, their visits are ordered to cut travel time while keeping the time windows customers were promised, and the board shows when a late job puts the rest of the day at risk.

The app should make the visit easier, not add paperwork. Each job shows the address and directions, the customer’s history, the reported fault, any manuals or drawings, and the checklist for that kind of job.

Technicians record what they did as they work: checklist items, before-and-after photos, readings, parts used and notes. Plant rooms, basements and rooftops often have no signal, so everything is saved on the phone and sent when the network returns. The Coimbatore driver app we built works the same way on highways, saving each proof of delivery until there is a network.

The app is written in the languages your technicians read, such as Hindi, Gujarati, Tamil or English, with large buttons and as few screens as the job allows. We test it with technicians on real visits rather than in an office.

A job is closed at the customer’s door, not back at the office. The technician completes the checklist, adds the photos and parts, and the customer signs on the phone or gives a one-time code. The service report goes to the customer on WhatsApp or by email straight away.

Before-and-after photos protect both sides. In the Austin pro app, they settle disputes about what was agreed and what was done, and every job’s photos, messages and history sit together on the dispatch board.

Billing follows from the same record. The invoice is built from the job, with GST where it applies, and payment by UPI, card or cash is recorded against it, so accounts sees a paid invoice the moment the job closes. Where customers pay by saved card, they can be charged when the job is marked complete, as Austin homeowners are.

Many service businesses earn most of their steady income from annual maintenance contracts. Each contract records the customer, the equipment, the visits it covers and its renewal date.

Preventive visits are created before they fall due and confirmed with the customer, so they are planned like any other job instead of remembered. Warranty periods are recorded per piece of equipment, so the technician knows on site whether a repair is chargeable. Renewals are flagged early, with the visit history attached, which makes the renewal conversation easier.

A first visit fails most often for want of a part. The app keeps stock for each van and each branch, records the parts used on every job, and lets technicians request parts from the field.

When a job is matched, the parts it is likely to need can count too, so it goes to a technician who carries them. Parts used flow into the invoice and into stock at the same time, and a weekly view shows which parts run out and which sit unused in vans.

Most calls to a service office are a customer asking when someone will come. The answer should reach them first.

Customers book on WhatsApp, your website or by phone, into one queue. They receive the technician’s name, the time window and a message when the technician sets off. Calls between customers and technicians can go through masked numbers, as in the Austin apps, so neither side sees the other’s real number. After the visit, a short rating tells you how the job went while it is still fresh.

Field service works best when it shares records with the rest of the business. Customers and equipment can come from your CRM, invoices and payments can flow to accounting software such as Tally or to your ERP, and parts can follow your inventory. If you also need attendance and payroll for the same team, Hearth HRMS, the HR and payroll software we are building, has field and site teams check in on their phone at an allowed location.

We need three things from you: your job types and checklists as they are today, recent jobs with their outcomes, and an owner on your side, usually the service manager. Before we build, we agree the measures that matter: response time against what you promise, jobs per technician per day, repeat visits, time from job to invoice and calls asking where the technician is. We watch them through the pilot.

A field service app is best launched one branch or team at a time. Technicians are trained in person, on their own phones, and the office runs the old way alongside for a short while until the board is trusted.

In Austin, pros were onboarded onto the app before customers could book, so there were checked pros ready in every zip code on launch day. After launch, we run the system with you: we tune the matching rules and checklists, add job types and reports, and keep the apps working as phones, maps and payment providers change.