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

CRM for Beylikduzu businesses

On a sales floor a booking does not always belong to a person. Sometimes what is held is a demo room; sometimes it is the machine the buyer stands beside. When a tool hangs its calendar off staff, the room and the equipment end up in a notes field, and that note is what turns into two bookings on one slot. Yakuplu and Gurpinar in Beylikduzu are sales-floor streets, so the question lands there too. In AlgoRandevu, the product we are building now, what a booking attaches to is chosen inside the product.

Get a quote Tell us about your project

CRM — Beylikduzu

Trade in Beylikduzu happens where the product is on show. A buyer walks in and takes a slot for a demonstration or a fitting; when what it holds is a space rather than a colleague, the calendar has to say so. The closest work to that texture is AlgoRandevu — our own product, under construction, and we neither call it finished nor give a delivery date. Its limits are worth stating: a booking product with no catalogue and no payment step, not a screen mounted on a sales floor, and furniture or textile work is nothing we can show. What we describe is keeping the resource selectable. We build it on the same Laravel and Inertia ground as AlgoKlima and AlgoCar, with MySQL holding records, Redis as the cache layer and Tailwind shaping the panel.

  • What a booking attaches to is picked inside the product — a person, a room or a piece of equipment — so the business marks its own resource and we write no per-sector variant.
  • The product is built on the same Laravel and Inertia ground as our AlgoKlima and AlgoCar panels, which keeps the screen logic familiar to anyone already using one of them.
  • The aim is to gather a booking that currently runs by hand between a calendar and a messaging thread into one panel; what we describe is the build in progress, not a finished product.

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

AlgoRandevu — in the build, a booking binds to a person, a room or equipment

Our own product, still under construction: not finished, and no delivery date given. In the structure we are working on, a booking is not written against a colleague by default. The resource can be a person, a room or a piece of equipment, and the business chooses which one from inside the product, so no per-sector variant has to be written. We build it on the same Laravel and Inertia ground as our AlgoKlima and AlgoCar panels, with MySQL holding bookings, Redis as the cache layer and Tailwind shaping the interface. The aim is to gather a booking that runs by hand today into one panel. Boundary: no catalogue, no payment step.

Read the case study →

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

  • Is AlgoRandevu finished? When could we install it?

    It is not finished. We are building it now and we give no delivery date, which is why the page says so. What can be discussed today is the structure: keeping the thing a booking binds to selectable inside the product.

  • Why does writing a booking against a room rather than a person matter?

    It moves where the constraint lives. If there is one demonstration room, a booking held against that room blocks a second one. When the resource does not sit on the booking record, the same hour looks free in two places at once.

  • Would you install a touchscreen on our sales floor?

    That is separate work. For a screen application running on a device the business owns, what we can show is the KGM SsangYong showroom kiosk, written in React Native (Expo). AlgoRandevu is a panel product rather than something mounted on a floor.

  • Would an off-the-shelf booking app cover us?

    If every booking belongs to one named person, it will, and we say that instead of quoting a build. The line starts where the thing being held is a room or a machine, because then the resource has to sit on the record itself.

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