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

CRM · Tuzla

CRM for Tuzla businesses

In heavy manufacturing a planned service goes onto the calendar and a breakdown ignores it. Where a maintenance window only opens once a line stops, the call that cannot wait arrives while it runs. The Aydinli and Orhanli belt in Tuzla is heavy-industry ground. Both hang off the same customer and neither is the other job. That is the CRM question here: do the two work types blur into one record, or stay apart. AlgoCar was built on that split — our own product, whose upkeep we carry.

Get a quote Tell us about your project

CRM — Tuzla

A plant in Tuzla can open two kinds of work against the same supplier inside one year: a contracted service and an unplanned repair. Both draw from one shelf and both move at a different speed. The work closest to this district's sector profile is AlgoCar, and we say plainly where it stops. It was written for vehicle servicing, we have no marine or shipyard software to point at, and it was not shaped around dock operations. What travels is how a work type is kept apart inside the record. Laravel, MySQL records and a Redis cache sit underneath, Inertia brings the panel screens, and a React Native (Expo) field side writes into the same application. Nobody drives to a plant; the team works remotely.

  • Planned maintenance and breakdown repair open under their own work type, and whichever one consumes a part, it comes off the same store rather than a second one.
  • A part leaves stock as it is written onto the work order, so nobody fills a separate warehouse screen inside the narrow window when the line is down.
  • The boundary is stated too: AlgoCar was built around vehicle servicing, and we have no shipyard or marine operation work to show.

Why Algoriel

  • Booking, plan and invoice kept apart

    The dental CRM holds a treatment plan per tooth; an appointment attaches to a plan step, so moving the plan moves the calendar.

  • Request types split up front

    At Diotek a site survey and a service call are two separate flows and never share a form.

  • No second document

    Tahlil.com takes the values in and writes the specialist's reading onto the same record, so the result stays in one place.

  • History belongs to the equipment

    AlgoKlima keeps service history under the unit rather than the customer, so it travels with the unit when it changes hands.

What we build

CRM

  • A service plan that moves step by step

    A treatment or maintenance programme that runs over several sessions is kept as its own plan, separate from the bookings. In the dental clinic CRM the plan is built tooth by tooth and split into sessions spread over weeks.

  • Appointments tied to the plan

    Each appointment is attached to a step in the plan. When the plan changes or a session is added in between, the calendar updates with it.

  • Package and membership balances

    When you sell classes or services in packages, what a customer has left shows on their card. At Pilatesco a booking takes one class off the package, and cancellations and no-shows follow different rules.

  • Service history per device

    Warranty, maintenance and fault history for the equipment you service is kept against the device, not the person. At AlgoKlima three air conditioners at the same address keep three separate files.

  • History that survives a change of owner

    When a device passes to someone else, its history stays with the device instead of being retyped onto the new customer's card.

  • The work done and the invoice in one place

    The procedure sits on the customer's record, so what was billed and what was carried out are read from the same place and nothing is entered twice.

Work like this

CRM · Case study

AlgoCar — scheduled work and calls open apart, parts come off one store

Our own product: a service management system whose upkeep we carry rather than a client handover. The split sits here — work booked onto the calendar and a call that arrives unannounced open as separate work types, while both gather under the same customer. On the parts side there is no split. Whichever type consumes a part, it comes off one store, and it leaves stock as it is written onto the work order. The invoice comes off that same order, so trading and accounting are never matched across two programs. The scope stands as written: AlgoCar was built for vehicle servicing, and marine operations are not work we can show.

Read the case study →

Working with Tuzla 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

  • Do you send anyone to the plant to install it?

    No, the work runs entirely remotely. The starting point is a decision rather than code: where a maintenance job and a breakdown call part company inside the record. Building starts once that is settled.

  • We run heavy manufacturing upkeep, not a vehicle workshop. What does AlgoCar tell us?

    That it was written for vehicle servicing, which we state as it is. What carries across is not the vehicle screens but how the work type is separated: scheduled work and calls open apart, and parts come off one store either way.

  • Do you build vessel or shipyard software?

    No. There is no marine work in our portfolio and we will not claim any. What we describe is the shape of a maintenance and repair record, and that shape behaves the same in a plant as in a workshop.

  • The maintenance window is tight and the crew cannot stop for a stock screen.

    They do not have to. A part leaves stock the moment it is written onto the work order, with no second screen waiting to be filled. The stock movement shows up as the job closes.

CRM in other cities

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

Other services for this location

Want to bring your customer tracking into one system?

Get a quote or open the service