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 · Atasehir

CRM for Atasehir businesses

In a company with several branches a customer card changes hands over time: a representative leaves, a file moves to another branch, the record ends up under somebody new. If the history was written under that card, it fragments in the move. For a head office in the Icerenkoy blocks of Atasehir the question is the same: what does the history hang off? AlgoCar anchors it elsewhere. The maintenance and repair file hangs off the plate and chassis, so when a vehicle changes owner its history travels with it.

Get a quote Tell us about your project

CRM — Atasehir

What describes Atasehir is a management shape rather than a sector: central reporting with branches beneath it. The CRM question follows from that shape — who owns the history. The work closest to this district's management profile is AlgoCar, our own product, whose upkeep we carry. Where it does not overlap belongs here too: AlgoCar was written for vehicle servicing. Campaign management, sales pipelines and call-centre logging are not things we can show, and no bank or insurer sits among our clients. What transfers is not the screens but what the history is anchored to. The panel runs on Laravel and Inertia, the field side on React Native (Expo); MySQL holds the records, Redis carries the reads.

  • History is anchored to the asset rather than the party: repair and maintenance files gather under the plate and chassis and stay put when the person holding the card changes.
  • Figures reaching the centre are not assembled from a second program, because the work order, the parts consumed and the invoice close on one chain, so cost and revenue read off the same record.
  • The limit is written down as well: campaign management, sales pipelines and call-centre logging fall outside this scope.

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 — history anchored to plate and chassis, never to a person card

Our own product: a service management system built around the vehicle on the workshop floor, whose upkeep we carry rather than a handover. The anchor sits on the asset, not the party. Maintenance and repair history gathers under the plate and chassis, so when a vehicle is sold the file goes with it, nothing is retyped onto the new owner's card, and no second record opens for the same asset. The rest of the chain feeds off that record: a work order opens, the part consumed is written to it, stock falls at that moment, and the invoice comes off the same record. The scope is service and trading; campaigns and pipelines sit outside it.

Read the case study →

Working with Atasehir 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 have an office or a representative in Atasehir?

    Neither, and we work entirely remotely. The first session with a head office is not spent on screens either: we list together which facts belong to a person and which belong to an asset. Development waits for that list.

  • If we merge two customer cards, what happens to the history?

    Nothing, because the history was never under the card. Maintenance records hang off the asset, so the file stays put while the card changes. That turns merging cards into ordinary tidying rather than an operation that risks losing years of work.

  • We serve corporate clients at branches, not vehicles. How does the idea apply?

    The question becomes what holds still in your business. What a plate and chassis are in a workshop, a contract, a site or a serial number is elsewhere. Hang the history there and a change of representative or branch stops cutting the record in half.

  • Would the centre not need a separate warehouse for reporting?

    At the scale we can show, it did not. In AlgoCar the trading and accounting side attaches to the same core as the service record, and a report is that record read from another angle. Multi-branch consolidation and financial reporting are outside what we have documented, so we do not promise them.

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