EN TR
Get a quote
View all services
Web software

One app carries the brochure pages and the request queue.

System architecture

The pieces and their boundaries are settled before code.

Enterprise & commercial software

Several institutions, one system, records kept apart.

Mobile app

One codebase, both stores: iOS and Android.

Software consulting

We take a running system over and improve it.

AI consulting

AI only where the problem actually calls for it.

Get a quote
EN TR

Process Tracking · Umraniye

Process Tracking for Umraniye businesses

If a maintenance job starts as a phone call, its record ends up in a technician's notebook, and around the Dudullu estate in Umraniye that is a familiar arrangement. When you look for field service software, what you want to know is not who worked how many hours but where a call stands right now. AlgoKlima was built around that unit. A call opens against a device, goes to a technician, and closes in the field, not at a desk that evening.

Get a quote Tell us about your project

Process Tracking — Umraniye

Umraniye's texture is the Dudullu industrial estate: mechanical contracting, air conditioning service and small manufacturing side by side. If maintenance does not finish at one address, a single plant holds several units and the crew moves between buildings all day. The work closest to that sector profile is AlgoKlima, whose own field is air conditioning and appliance service. A call is opened against a device instead of an address, and units at the same site keep separate files. Coverage stops in a boiler room or under a machine, often exactly where a call gets closed, so the record queues on the phone first. There is no office on our side; the team works entirely remotely.

  • A call is filed against the device, not the address, so units at the same plant keep separate histories and a unit that changes hands takes its record with it.
  • Neither opening nor closing a call waits for a connection: the entry goes to a local queue on the phone, and once the network is back the queue clears in the order entries were written.
  • A closed call lands in that device's warranty, maintenance and fault file, so the next call opens with the earlier closings already in view and a repeat fault stops hiding.

Why Algoriel

  • Keeps working offline

    The field app keeps recording with no connection, and the queue reaches the server in order once signal returns. That is how AlgoKlima runs.

  • Entry from QR and location

    Where no fixed terminal can be installed, entry and exit are logged from a QR code and a location reading, and entitlement is worked out from those readings.

  • Records land the same hour

    Jobs close in the field, so the office sees where each one stands without waiting for end of day.

  • Office and field read one source

    The office panel and the field app read the same information, so nobody keeps a spreadsheet alongside it.

What we build

Process Tracking

  • What the record attaches to

    Rather than mapping a process in the abstract, we decide what a record hangs on. On the construction system a row belongs to a person and a site at once, and the two are never separated. In AlgoRandevu we are building a structure where a booking can attach to a person, a room or a piece of equipment.

  • The entry that stays open

    Instead of a live dashboard, one rule: a matched check-in and check-out produce the hours, and a check-in with no scan out stays open. Whatever is stuck shows up as that gap.

  • Who was where, on the record

    Because a single row carries both the person and the site, totals separate by site. When one worker spends the month across two sites, those hours never fall into the same bucket.

  • What is left when the figure is disputed

    Because payroll is derived from matched pairs, the number argued over at month end has a time- and location-stamped record behind it. There is no parallel calculation sheet to reconcile against; the dispute happens over the record itself.

  • Records taken beyond coverage

    In AlgoKlima's service flow the chain does not break where the network does. Once the connection returns the waiting entries are processed in the order they were created, and an edit made in the field and one made in the office merge into a single record through conflict resolution.

  • Process rules kept out of the code

    Rules like the length of a step and the gap between consecutive ones belong in a product setting, not in the code. The aim is that changing one does not mean shipping a release, and that is what we are building into AlgoRandevu right now.

Work like this

Process Tracking · Case study

AlgoKlima service management — a call opens against a device and closes in the field

Our own product for air conditioning, boiler and appliance service teams — not a client handover but a system whose upkeep we carry. A call opens against a device, goes to a technician, closes on site, and lands in that device's warranty and maintenance file. The hard part: the office panel and the field app can each change the same call without seeing the other, and conflict resolution folds both edits into one record. Laravel and Inertia run the panel with Tailwind on top, React Native (Expo) runs the phone, MySQL holds the data and Redis carries the reads.

Read the case study →

Working with Umraniye teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • You work remotely — does setup mean sending someone to the site?

    We have no office, and nothing gets installed at the site either. The app downloads to the technician's own phone, while devices, customers and call types are defined from the panel. Setup is configuration, not an installation visit.

  • What happens to a call opened under a machine, with no signal?

    It opens there and closes there. The entry waits in the phone's local queue, and when the network returns the queue clears in the order entries were written. A desk edit on the same call merges into it.

  • Would an off-the-shelf job tracking tool be enough for us?

    If a work order list and a calendar cover the job, it is enough and we say so. The line falls where a call has to attach to a device's service history. We publish no savings percentage, because nobody has measured one.

  • Can it connect to the accounting and stock systems we already run?

    It can, once two questions are settled: which side a call opens on, and whose version stands when both sides change it. A link built before those answers leaves the month closing with two lists that disagree.

Process Tracking in other cities

The other cities where we publish this service are below, grouped by province.

Other services for this location

What stands behind your month-end figure today?

Get a quote or open the service