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

CRM for Umraniye businesses

Mechanical contracting crews in Umraniye do not belong to one address. The same fitter is on one customer's site in the morning and another's after lunch, and when the work is spread between the new blocks in Esensehir and the refurbishment along Alemdag Caddesi, that swap happens more than once a day. So the customer record has to hold something beyond hours worked: it has to hold who stayed on whose site. Construction workforce attendance answers that inside the record.

Get a quote Tell us about your project

CRM — Umraniye

Mechanical contracting, air conditioning service and small manufacturing sit side by side in Umraniye, and what they share is that the work happens on a customer's site and that the site is temporary. On a temporary site there is no permanent building to fit a reader to. The work closest to how this district operates is the construction workforce attendance system we built. Where it stops is plain: it was written for building sites, and a service contract or a manufacturing shift plan is not something we can show. What carries across is that the person and the site sit together on the record, and the site is never a name picked off a list. Laravel takes the entries, MySQL holds them, and a React Native (Expo) app runs on the worker's own phone.

  • One entry carries two facts at once: the QR code establishes who scanned, and the location establishes which site they scanned on.
  • Time the same fitter spends on different customer sites stays apart, so a person's day never rounds up into a single address.
  • The scope is written down: the system was built for building sites, and service contract management or manufacturing shift planning is not work we can 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

Construction workforce attendance — the record holds person and site together

A building site is not a permanent address. No turnstile goes on the gate, and workers move between sites. The system was built for that: entries and exits are recorded through a QR code and a location check, where the code establishes who scanned and the location which site they scanned on. Because both facts land in one record, the site is never typed or picked off a list, and one person's time on different sites stays separate. The field app runs on the worker's own phone through React Native (Expo), Laravel takes entries and MySQL holds them, so nothing is left to dismantle.

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

  • Do we have to fit hardware on our sites?

    No. The system runs on the worker's own phone, so there is nothing to mount at a gate. When the job ends there is also nothing to dismantle, move, or replace on the next site.

  • We are a mechanical contractor, not a builder. What does this record say to us?

    That it was written for building sites, which we state as it is; service contract management and shift planning are not work we can show. What carries is the shape of the record, with the person and the site on one line.

  • What happens if a worker picks the wrong site?

    They do not pick one. The location establishes the site and the QR code establishes who scanned, and the two land in a single record. Because the site is not a field to fill, there is no wrong choice to make.

  • Do you have a team in Umraniye?

    No, and nobody is sent to a site; the team works entirely remotely. What a setup needs is not a visit but a decision: which site counts as whose customer, and what a scan has to establish before it becomes an entry.

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