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

CRM for Sisli businesses

When a booking plug-in fixes how long an appointment lasts at the moment it is installed, that length stops being a setting. Vali Konagi and Rumeli Caddesi in Sisli are cosmetics and beauty streets, and there a season campaign can stretch a consultation and shrink it again when the campaign closes, with the turnaround gap between consecutive slots shifting too. When the length lives in code, every change turns into a development request. We are building AlgoRandevu against exactly that, and it is still in development.

Get a quote Tell us about your project

CRM — Sisli

Central trade and cosmetics retail share the same streets in Sisli, and a brand's consultation desk sells as much as its window does. An appointment is not one thing across those desks either: a short product consultation on one, a long treatment on the next. The place we stand closest to that tempo is our own product, AlgoRandevu, and we will not dress it up. It is in development, we have no running installation to show, and it was not written for cosmetics retail; loyalty schemes and the till sit outside it. What we can show is where the rule lives. Underneath sit Laravel, MySQL records, a Redis cache, Inertia screens and Tailwind styling, the same setup our own panels run on.

  • Appointment length is held as a product setting, so a campaign that stretches or shortens a session changes the setting and leaves the code alone.
  • The turnaround gap between back-to-back slots belongs to that same setting, so a desk's reset time is not an assumption living outside the calendar.
  • What we do not promise is written down: AlgoRandevu is still being built, carries no cosmetics-retail preset, and has no running installation on 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

AlgoRandevu — appointment length held as a product setting

Our own product, under construction right now, with no finished installation on show. A booking tool can decide up front how long a session runs and how much room sits between two of them, and decide it by sector. We keep both values in the product's own settings: the business sets the length, a rule change costs no code change, and no separate build ships per sector. It goes together on the Laravel and Inertia ground that carries the AlgoKlima and AlgoCar panels, with records in MySQL, caching on Redis and Tailwind shaping the interface. The boundary is plain: no cosmetics-retail preset, no till, no loyalty scheme here.

Read the case study →

Working with Sisli 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 keep an office in Sisli, or send someone to the store?

    There is no office and nobody drives out; the work runs remotely. We start in writing instead: how long a session should run, how much room sits between two of them, and who is allowed to change that setting. Building follows.

  • Could a calendar plug-in cover this for us?

    If your session length never moves, it can, and we say so rather than quote a build. The line falls where a campaign stretches or shortens the session and you cannot make that change from a setting.

  • Can we install AlgoRandevu today?

    No. The product is still being built, we show no running installation, and we do not describe it as finished. What we can show today is AlgoKlima and AlgoCar running on the same ground.

  • Do you have a ready configuration for cosmetics retail?

    We do not, and we will not claim one. AlgoRandevu is being built so that no sector sits baked into it: no separate release for cosmetics, for treatment rooms, or for anything else. The rule stays in the business's own setting.

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