The pieces and their boundaries are settled before code.
Several institutions, one system, records kept apart.
One codebase, both stores: iOS and Android.
We take a running system over and improve it.
AI only where the problem actually calls for it.
Field service software
Custom field service software is built around your own customer, unit and crew records, on a technical footing we maintain ourselves. The job opens on the technician's phone and closes there even when there is no connection. Today we build it for HVAC, boiler and appliance service companies.
Field service software keeps the customer, the unit being serviced and the crew who go out to it in one system. The first decision is where each job is first recorded: it opens on the technician's phone, closes without a connection, and the office reads that same record. At AlgoKlima the customer sat in an office spreadsheet, the unit in a technician's notebook and the phone in between; today all three share one system.
An HVAC, boiler or appliance service company runs on three things kept in three places. The customer is a row in a spreadsheet at the office, the unit is a page in the technician’s notebook, and whatever the two do not know about each other travels by phone. AlgoKlima tracks the customer, the unit and the field crew in one system: the spreadsheet and the notebook give way to a single record, and the phone goes back to being a way for people to talk to each other.
The hard part in the field is the screen that waits for a connection. A form that cannot be sent stops the technician halfway through the job, which is why AlgoKlima’s field app is built as a ledger rather than a form: the job opens on the technician’s phone and closes there. Two hands on one record was the other question on the table from the start; two screens could write to the same job without either one noticing. That question belongs to the build rather than to a later bug report, so it was asked there, and how the record travels to the office is the case page’s subject.
Where a service request starts is a decision too. If a customer can open one from your website by naming the unit already installed, instead of calling, the record begins in writing rather than in somebody’s notes. Diotek takes post-installation maintenance and fault requests that way.
This page sits under enterprise software. How many institutions and screens share one system is that page’s question; what is described here is the face of that system which looks out to the field. We build AlgoKlima for HVAC, boiler and appliance service companies, with new work still going onto it, and your system is built on the same technical footing.
The boundary is worth stating. If the vehicle comes to you, your technician is not going out to anyone; the work is workshop service, with the arriving vehicle rather than an installed unit at the centre of the record. AlgoCar is built around the vehicle that arrives at the workshop, and the ERP page follows how the workshop side closes. This page holds the technician who opens the record at the customer’s address.
What replaces the spreadsheet, the notebook and the phone call:
The customer, the unit and the job open in one system, office and field read the same record, and there is nothing left to relay. At AlgoKlima those three used to travel between a spreadsheet, a notebook and a phone call.
A service record carries the customer, the unit being serviced and the technician who went out to it, so who went to which unit lives in the record rather than in somebody's head. AlgoKlima tracks those three things in one system.
The app in the technician's hand works like a ledger that runs by itself rather than a form filled in and held until it can be sent. At AlgoKlima the job opens on the phone and closes there when the work is done; how the record reaches the office is the case page's story.
The office panel and the app in the van can touch the same record without either side seeing the other, so which edit survives is settled while the record model is built. At AlgoKlima that was one of the first questions on the table, not a surprise found after launch.
The three trades share one shape: the technician goes to the address, the unit stays where it was installed, and the job record starts there. We build AlgoKlima for those three, and the feature work on it continues.
If the vehicle or the unit comes to you, your technician is not going out to anyone; the work turns in the workshop, and that is not what this page describes. AlgoCar is built around the vehicle that arrives at the workshop, and the rest of that chain is on the ERP page.
Every project goes through the same four stages: planning, architecture, modelling, development.
See our process
Our own workshop software, built around the car on the ramp. A work order, the parts it consumes and the invoice it produces run as one chain, and the accounting side hangs off that same record. Maintenance history lives on the plate and chassis, so it travels with the car.
Our own product for HVAC, boiler and appliance service companies. The customer and device records the office works from are the same ones the technician carries into the field. A job can be opened and closed in a basement with no signal, and service history stays tied to the device.
We have no office, so we do not provide on-site support either. The work runs remotely and we scope it on that basis.
It does. Your technician does not stop the job to look for a connection; the record opens on the phone and closes there. AlgoKlima's field app is a ledger that works with no connection at all, not a form that waits to be sent. How the record reaches the office is on the case page below.
That is settled at the start. You are not the one deciding afterwards which of two versions is right; the answer is written into the record model when it is built. AlgoKlima named that problem on day one: the office panel and the field app can touch the same record without either one knowing. Tell us in the quote form which records your office and your crew both touch today.
In part, it is. Without a technician going out to an address, yours is workshop service, and the centre of the record changes: the vehicle that arrives takes the place of the installed unit. AlgoCar opens a job the moment the car reaches the workshop, and nobody drives out to a customer. The ERP page follows the workshop side of the record, and the vehicle service case sits below.
We build it for HVAC, boiler and appliance service. Your system is built on the same technical footing, so nothing has to be designed from scratch for you. AlgoKlima is built for those three trades and the feature work on it continues. If your unit type is a different one, the quote form is where to name it and we will scope it from there.
It can start on the website. Your customer opens a maintenance or fault request without calling, naming the unit that is already installed. Diotek takes post-installation maintenance and fault requests through its website, and each request is built around the installed unit. Put down in the quote form where your requests come from today; where each job is first recorded is one of the first decisions we settle together.