Get a quote

CRM · Besiktas

CRM for Besiktas businesses

A CRM on a head-office floor can start one step too late. Nothing is recorded until a form is filled or a call is made, so everything before that threshold leaves no trace. Gayrettepe and Etiler in Besiktas are where multi-brand groups keep their central floors. If the only thing between interest and a record is ringing people until they answer, that threshold gets expensive. Tahlil.com splits the threshold instead: its tahlilmatik calculators open a separate way into the platform, and a visitor gets something back before any account exists.

CRM — Besiktas

Besiktas is thick with head offices and multi-brand groups, and decisions are taken centrally. The work closest to that profile is Tahlil.com, and what it does not cover comes first: written as a health platform, it holds no sales funnel, no quote tracking and no deal stage. We have no agency or media client here, and campaign reporting is something we never built. What travels is the shape of the entrance: the calculator takes one value and hands back the reference range it falls in. Underneath: Laravel, MySQL records, a Redis cache, a Tailwind interface, React Native (Expo) on the phone, OneSignal for the notification.

  • The calculator is the platform's second entrance: one value goes in, the reference range comes back, and no account has to be opened first.
  • A model prepares the first reading, but the physician writes and approves the comment, so the wording that reaches a person leaves the approver's hands.
  • Following up does not rest on anyone remembering: the moment a comment is approved, a notification calls the person back to their own record.

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

Tahlil.com — a calculator as a second entrance, approval resting with one physician

Lab values interpreted under physician supervision. What this page leans on is the entrance. The tahlilmatik calculators open a separate way in: someone types a single value, reads which reference range the result falls in, and gets an answer without booking anything. The calculator is not a build of its own: it feeds off the same Laravel application as the site, the physician panel and the React Native (Expo) client, with MySQL holding records and Redis carrying the read load. On the reading side the order is fixed: a model drafts, the physician approves, and an OneSignal push follows. Boundary: no sales funnel, no deal stage.

Read the case study →

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

  • We run a head office, not a clinic. What does a health platform tell us?

    Tahlil.com is a health platform and we say so plainly; sales funnels, quote tracking and deal stages are not things that project can demonstrate. What carries across is the entrance itself: a tool that hands a visitor something useful stops the form being the only way in.

  • Would a tool like that calculator open a record on its own?

    What the calculator does on Tahlil.com is narrow: a value goes in, a reference range comes back. When a record opens, and which fields it carries, is a separate decision we write down together before building. The calculator is not a scoring engine.

  • Besiktas is full of agencies and media firms. Do you have a reference there?

    No. Agency work, media planning and brand communications are outside what we can show, and we do not write up a reference we do not have. Our portfolio sits in health, education, automotive and service operations, and we have no client in the district.

  • If a model drafts the reading, who owns what the customer finally sees?

    The physician who approves it. The draft arrives in the panel, the physician writes and signs off, and the final wording is theirs. The same question decides a CRM design: which person has the last word on a record.

Want to bring your customer tracking into one system?