Ready system · Field service
Field Tek: Field service management
Requests reach one dispatch board, technicians record the job on their phone even offline, and they invoice before leaving the customer's site.
- Type
- Ready system
- Sector
- Field service
- Runs on
- A web dispatch board, a technician app for phones that works offline, and a link for the customer with no app to install.
Who it is for
If your maintenance or installation technicians work at customer sites, Field Tek is for you. When jobs go out in chat groups and signal drops, photos get lost and invoices wait a day. Requests are logged and assigned from one screen. Technicians open the job on their phone, even offline, take photos and the signature, and invoice before leaving.
How a working day runs
A service request reaches the office, and staff log who asked, what failed, and where. The supervisor sees requests and available technicians on the dispatch board, assigns the job, and follows its status. The job appears on the technician's phone with its details and checklist. On site the technician photographs the fault before and after the repair; if the work needs approval, the customer gets the quote on their phone and approves it from a link. If the signal drops, the app keeps the work until the connection returns. The technician takes the customer's signature and invoices before leaving. The office sees all of it on the same work order, and the supervisor reviews the evidence before closing the job.
What makes the difference
- The technician app works offline and keeps photos and signatures until the connection returns, then syncs them.
- Customers approve quotes, follow their request, and receive the invoice from a link, with no app to install.
- Photos and the signature attach to the work order behind the invoice, so the office can trust what happened.
- Requests, work orders, quotes, and invoices sit on the same customer record, so an agreed price never gets retyped.
How it is built
We build the dispatch board with Laravel and Vue because the office works in a browser. The technician app is built with Flutter for phones, with Offline Sync keeping the work safe when the network drops. PostgreSQL with RLS keeps each company's data apart. Photos and signatures are tied to the work order in the same database. E-invoicing is connected once the business has the required credentials in place.
- Laravel
- Vue
- Flutter
- PostgreSQL RLS
- Offline Sync
Screens8 screens
Scroll to move between screens.
Questions buyers ask
What happens if the signal drops at the customer's site?
The technician keeps working in the app: opening the job, taking photos, and collecting the signature. The app stores everything on the phone and syncs it with the office automatically when the connection returns, so nothing from the visit is lost.
Does the customer need to install an app?
No. The customer gets a signed link on their phone to follow the request, approve the quote, receive the invoice, and leave feedback, with nothing to install. The app is for your technicians only.
Does it fit air-conditioning maintenance companies?
Yes. The first scope was designed for air-conditioning maintenance and other field-service companies that run teams of technicians. We start by reviewing one real service journey from your company to set the right first step for your team.