A field service app that runs on the technician's phone

Jobs handed out by phone in the morning, service forms piling up in the glovebox, a spare part everyone assumed was in the van but ran out last week, and cash collected in the field that never reaches the office by evening. In field service, most of the loss comes not from failing to fix the fault but from not capturing the record on site. A field service app brings the work order, the part, the signature and the price together at the place the work happens.

How many separate apps does this need?

  • 01

    Technician field app (iOS + Android)

    The day's work orders, device serial number scanning, fault code selection, parts deducted from the van's stock as they are fitted, photo evidence, a customer-signed service form and full offline operation.

  • 02

    Customer tracking app / web tracking screen

    Service request status, appointment window, a notification when the technician is on the way, the reason for any parts delay, repair cost approval and access to the completed service receipt.

  • 03

    Admin panel (web)

    Work order pool and technician assignment, appointment calendar, per-van spare parts stock, in-warranty vs. chargeable classification, payment collection tracking, and performance reports by technician and region.

What the app includes

  • Scan the serial number, see the device's past repairs
  • Suggested spare-part list tied to the fault code
  • Two-sided confirmation when parts move between technicians
  • Tracking the removed faulty part back to the depot
  • A return-visit queue for jobs waiting on a part
  • Labour timer: start, stop, and bill the time on site
  • Auto-generated work orders from maintenance contracts
  • Countdown for the legal maximum repair period, with alerts
  • Loaner-device handover and return record per customer
  • Manufacturer-portal jobs dropping straight into the dispatch pool
  • On-call roster and after-hours emergency assignment
  • Versioned labour tariff so old jobs keep their old prices

State of the sector

In authorised service networks the work usually comes from the manufacturer or distributor, sent through their own portal; a firm that closes records late or cannot fix the fault on the first visit gets fewer jobs next period. In independent service businesses the customer calls the day the fault appears and whoever answers first wins. A business running on paper forms does not know a job is closed until the technician stops by the office in the evening, leaves invoicing to the next day, and argues about out-of-warranty charges on the doorstep. Competitive pressure comes not from price but from hitting the appointment window and removing the need for a second visit.

Metrics that matter here

  • First-visit fix rate — When the right fault code, the device history and van stock are visible in the field, the technician does not have to come back a second time for a part.
  • Time from work order opening to closing — Because the record is closed on site, jobs waiting on parts and files left hanging can be tracked day by day in the panel.
  • Per-van stock count discrepancy — A part is deducted from the van the moment it is fitted; losses, returns and defective parts are tracked as separate movements.
  • Repeat faults on the same device within 30 days — Device history and photo records separate whether a recurring fault comes from the workmanship or the part.

Common mistakes in this sector

  • Reducing the app to nothing but a work order list Showing the technician the jobs while leaving the form, the parts deduction and payment collection on paper means someone still keys data in at the office each evening. If the record is not completed in the field, the app does not lighten the work, it adds one more step on top of it.
  • Leaving offline support until later There is no signal in boiler rooms, basements or industrial estates. Trying to bolt offline capability on afterwards means rewriting the data model from scratch; it has to be built on a local database and an upload queue from day one.
  • Uploading photos at full size High-resolution images on every record eat mobile data, uploads stall halfway and the work order still looks open. Images should be resized on the device, form data sent first, and media able to resume from where it left off.
  • Leaving the pricing decision to head office On an out-of-warranty job, if the technician cannot quote a price at the door the job waits or turns into an argument with the customer. Price line items should be generated in the app and approved by the customer on screen, with the approved amount and time recorded.

Regulation and compliance

Businesses providing after-sales service are required under Turkish Ministry of Trade regulations to issue a service receipt for every job, to observe the maximum repair period and to document this on request; the receipt the app produces should therefore carry the date, the device, the work performed and the customer's approval so it stands up in disputes taken to a consumer arbitration committee. For chargeable jobs, the obligation to issue an e-Arşiv invoice (Turkey's mandatory e-invoicing system) should run from the same record as the payment collected in the field. Customer addresses, phone numbers, device photos and technician location data all fall under KVKK (Turkey's data protection law, aligned with GDPR): the privacy notice, access permissions and retention periods must be defined from the outset.

The real challenges in this sector

  • Closing a work order where there is no signal

    Service work usually happens in a basement boiler room, an elevator shaft or the back block of an industrial estate, and there is no data connection there. The app has to download the work order, the parts list and the form template to the device; the technician writes the form, the photos and the signature to a local database on the handset; and the queue uploads in order once signal returns. If head office changed the same record, the conflict must not be silently overwritten but flagged in the panel for resolution.

  • Deciding in the field whether a job is under warranty or chargeable

    If the technician cannot answer “is this chargeable?” at the door, the job stalls right there. The app should scan the serial number or barcode on the device label and look up the warranty start date, out-of-scope damage and any extended warranty; if the job falls outside warranty, it should generate a price proposal itemised by labour and parts and have the customer approve it on screen. That approval record is what ends the argument when a dispute surfaces later.

  • Every service van is a separate mini warehouse

    Parts sit in the technician's van, not the central warehouse. If stock is not deducted from that specific van the moment a part is fitted, the count never reconciles and head office raises work orders against parts that do not exist. The app has to handle per-van stock, technician-to-technician transfers, return records for the old part removed, and a separate category for defective parts; it should also raise an automatic replenishment request for any item that drops below its critical level.

  • The two-hour appointment window and the wasted visit

    The customer has to be home; every visit turned away at the door burns the van's fuel, the technician's hours and another appointment that day. The app should send the customer a window notification and an “on the way” message, push reschedule requests into the panel, fill a same-day gap with a waiting job nearby, and record a no-access visit with a photographed reason.

  • The weight of service forms, signatures and evidence photos

    Before-and-after photos of the device, the rating plate label and the customer's signature are the only evidence in a consumer dispute, but dozens of photos per record eat mobile data and leave the sync half finished. Images should be resized and compressed on the device, form data sent before media, and interrupted uploads resumed from where they stopped. The service receipt should be generated as a PDF and sent to the customer immediately.

Required integrations

  • Invoicing straight after the service receipt through an e-Arşiv / e-Fatura integrator (Turkey's mandatory e-invoicing system, GİB-compliant — GİB is the Turkish Revenue Administration)
  • Card payment at the door and payment links via iyzico or PayTR (Turkish payment providers) or a bank virtual POS
  • Manufacturer and distributor authorised service portals: warranty lookups and spare parts ordering
  • Tracking parts shipped from the central warehouse to the technician with Yurtiçi, Aras, MNG or PTT (Turkish courier companies)
  • Appointment window, on-the-way and job-complete notifications over SMS and WhatsApp Business
  • Stock, account and payment reconciliation on the Logo, Mikro or Netsis side

Who this page is for

  • A newly founded independent appliance or air-conditioning service

    Every job is billable and there is no manufacturer portal. Start with work orders, photo forms, on-screen signature, the PDF receipt and payment on the doorstep; van stock begins with one vehicle and portal integration is simply not needed.

  • A manufacturer's regional authorised service partner

    Jobs arrive from the manufacturer's portal and closing time is measured. The weight sits on the warranty split, serial-number coverage lookup, core returns and the repair-period countdown; taking payment matters less.

  • A building-systems firm working on maintenance contracts

    Work arrives on a calendar, not from a breakdown: scheduled servicing of lifts, boilers and fire systems. Contract-driven work-order generation, a per-building asset list, maintenance checklists and renewal reminders lead; emergency call-outs run off an on-call roster.

A phased plan that splits the budget

  1. 1

    Phase 1 — A work order one crew can close end to end 5-7 hafta

    Dispatch pool, technician assignment, the field form with fault and action codes, photos, on-screen signature, a PDF service receipt and the offline queue. This alone replaces the paper form. The offline data model is built first, because bolting it on later means rewriting how every record is stored.

  2. 2

    Phase 2 — Parts and money: van stock, warranty, payment 4-6 hafta

    Van-level stock with parts deducted at the moment of fitting, transfers between technicians, faulty-part returns; warranty-or-paid decision from the serial number with on-screen price approval; card payment and payment links on site, linked to Turkey's e-Arşiv electronic invoicing. Stock and cash only add up once Phase 1's records are reliable.

  3. 3

    Phase 3 — Customer side, contract maintenance and outside portals 4-6 hafta

    Customer tracking screen with on-the-way notifications, work orders generated from maintenance contracts, jobs flowing in from a manufacturer or distributor portal, loaner-device custody, plus technician and region reports. This comes last because it depends on outside parties, whose access approvals can hold up the schedule.

Typical scope and timeline

Technician field app (iOS + Android), admin panel and customer tracking screen. Work order pool and assignment, appointment window notifications, serial number scanning, fault and operation codes, per-van spare parts stock, in-warranty vs. chargeable classification, photo evidence, on-screen signature, PDF service receipts, offline operation and sync, in-field payment collection, e-Arşiv invoicing connection and store release.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Sector-specific workflow Off-the-shelf field software ships with work orders, routing and forms; a standard repair job runs from day one. Service-specific steps — warranty split, faulty-part returns, the maximum repair period countdown — usually survive only as free-text fields in a generic form.
Connecting to existing accounting Common packages may already connect to Turkish accounting systems (Logo, Mikro) and e-invoicing providers; where that exists, setup is quick. Rules like how customer accounts are opened or whether a warranty job is invoiced at all are written to match how you actually work; a prebuilt connector will not bend to them.
Monthly per-user fee versus one-off investment With a handful of technicians a monthly subscription is cheap and low risk; if it does not fit, you stop next month. As the crew and seasonal hires grow, the per-user fee climbs every year; with custom software cost grows with added scope, not headcount.
Data ownership and moving historical records Most packages offer an export; the job list and customer data come out as tables. The real asset — signed service receipts, evidence photos and per-device fault history — usually comes out incomplete; in your own database it stays attached to the device serial number.

Sector glossary

First-time fix
Finishing the job in a single visit. Service quality is judged on this: every return trip for a part burns fuel and swallows another appointment slot that day.
Maximum repair period
The legal ceiling, under Turkish after-sales rules, for completing a repair. The clock starts when the device is taken in; if it runs out the consumer can demand a replacement, so it is tracked daily.
Core return
Sending the removed faulty part back to the depot. Manufacturers require it on warranty jobs; a part left in the technician's van usually means the warranty claim is not paid.
Van stock
The spare parts a technician carries in the vehicle. It is counted as a separate warehouse; if a fitted part is not deducted at once, counts drift and dispatch schedules jobs against parts that no longer exist.
Loaner device
A device lent to the customer while the repair drags on. Unless who took it, with which serial number and when is recorded, it is never collected back — a quiet source of lost inventory.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →