Field service and AMC reporting: a practical guide for service companies

Field service and AMC reporting means recording every engineer visit (which customer, which machine, what was wrong, what was done, which parts were used, and whether the job is closed) so the office can close complaints, bill parts and prove AMC visits. The records are simple. Getting them from technicians every day, for every job, is the hard part.

This guide is for owners and service managers of companies that maintain equipment at customer sites: HVAC and air conditioning, lifts and elevators, RO and water purifiers, CCTV and security systems, solar plants, diesel generators, and IT hardware and printers.

What a service company needs to record

Across all these trades, one visit produces the same core facts. The service report format covers them in detail, with a free Excel template. In short:

• Who and where: engineer, customer, site.
• Which machine: equipment type and serial number.
• Why: complaint number and what the customer reported, or "AMC preventive" if it was a scheduled visit.
• What happened: fault found, work done, parts used with quantity.
• Where it stands: done, partial or pending, and the next action for anything not done.
• Proof: a photo of the work and the name of the person who signed off.

What changes by trade

The core stays the same; the details engineers should mention change with the equipment.

Complaint closure: the loop that leaks

A complaint comes in on the phone. Someone writes it in a register or a sheet and calls an engineer. The engineer visits. Then, very often, nothing is written back. The complaint looks open in the office while the customer considers it fixed, or it looks closed because nobody has heard otherwise, while the customer is waiting for a part.

The fix is simple to describe:

1. Every complaint gets a number when it is logged.
2. Every visit is recorded against that number, with a status of done, partial or pending. One row per visit, so a complaint needing three trips shows three rows.
3. Pending always has a next action and a date. "Waiting for part" is not a next action; "return with compressor on 03-10-2026" is.
4. Someone reads the pending list every morning. Ten minutes, before engineers are assigned for the day.

Step two is where it breaks. The first, third and fourth steps happen in the office. The second depends on an engineer who is already driving to the next call.

Parts tracking without a store clerk at every site

Parts are where service margins disappear. A capacitor that left the store but never appears on any report was either used and not billed, used on a job outside your books, or is sitting in an engineer's bag. You cannot tell which without the report.

• Parts on every service report, with quantity. "Gas filled" should be "R32, 0.6 kg".
• Against a serial number, so a machine that eats a part every month stands out.
• A weekly check: parts issued from the store against parts reported. The difference is the conversation to have.

The daily problems every service manager knows

• Paper job cards arrive late or not at all. They come back in a bundle at the end of the week, some unreadable, some missing, none with the serial number.
• The WhatsApp group is full but unsearchable. Engineers post photos and one-line updates, which is genuinely useful in the moment. A month later, finding every visit to one customer means scrolling through thousands of messages. The comparison of WhatsApp groups and structured reporting goes into this.
• Forms and apps go unused. A form with fifteen fields is fine in an office. On a rooftop, with a phone in one hand, it gets skipped, or filled at night from memory.
• AMC renewals without evidence. The customer says nobody came in July. You believe someone did, but cannot show a dated, signed record.
• No idea who did not report. Silence looks the same whether the engineer finished five jobs or none.

A simple setup that works

Before choosing any tool, agree on these in the office:

1. A list of customers and sites, spelt one way.
2. Equipment serial numbers for every machine under AMC.
3. One sheet with one row per visit, using the columns in the service report format.
4. A daily habit: pending list in the morning, missing reports in the evening. The guide to tracking field staff daily reports covers the evening check.

With that in place, the only remaining question is how the row gets filled in from the site.

vBol for service teams

vBol lets engineers report a visit the way they already talk to the office: on WhatsApp. They save one number as a contact and, before leaving the site, send a voice note, a photo of the work or their location, in Hindi, Marathi, Tamil, Kannada, Telugu, Gujarati, Bangla, Punjabi, Malayalam, Odia, Urdu or English.

vBol transcribes the note, fills in the fields of your service job record (customer, equipment, complaint, work done, parts used, status, time on site) and reads the record back on WhatsApp in the engineer's language, with buttons to confirm or fix a field. Nothing is written until the engineer confirms. The confirmed row goes into your Google Sheet, an Excel workbook on OneDrive or SharePoint, or the matching module in Ekatm ERP, with the photo and location attached to the row.

At 7 PM the owner or service manager gets one WhatsApp message listing what was filed, by whom, and which engineers sent nothing that day. If engineers also file expenses the same way, large ones, such as a part bought locally, get their own flagged line.

There is no app to install, no login and no training for engineers; most teams file real records the same day. Vritti sets up your record types and destination sheet with you, and it works whether you have five technicians or five thousand. It is free for 30 days (up to 5 confirmed reports per person per day during the trial), then ₹199 per user per month for teams of up to 100 users, with a custom plan for bigger teams. See pricing.