Polyclinic CRM: instead of a switchboard that rings busy a single WhatsApp line

It organizes the traffic from the moment a patient first reaches your organization: a WhatsApp line instead of a switchboard that rings busy, branch routing, appointment records, and tracking of corporate agreements and price requests. Each patient's branches, latest messages and appointment history sit on one card, and your front desk works from a tidy inbox instead of a phone queue. ÖzgürKod is not an HBYS or hospital automation system; examinations, tests and billing stay in your own system, and the communication layer is managed here.

You draw your own routing scenario in the visual flow builder: the chatbot shows the patient a branch menu and branches based on the choice; it asks for details such as full name and preferred day, then hands the conversation to that branch's rep. Because it also works outside office hours, an appointment request that arrives at night is waiting as a ready record in the morning. To be clear: the chatbot does not perform medical triage or diagnose symptoms; it only routes using the menu and questions you define, and the decision stays with the doctor.

No. To be straightforward, ÖzgürKod does not send scheduled messages on its own. Here is how it works: tomorrow's appointments are listed branch by branch in the panel, and you send the notice in one click with a Meta-approved WhatsApp template. You can also reach the group of patients with appointments on the same day in bulk through the campaign module, and the duplicate-send guard prevents a patient from getting two messages. The content and timing of every send always go through your team's approval; in healthcare communication, this control is a deliberate design choice.

No. ÖzgürKod does not claim to integrate with HBYS, e-Nabız, Medula or laboratory systems; exam records, tests and invoicing stay in your existing system. ÖzgürKod's scope is the other side: the message traffic from the moment a patient contacts you through to the appointment and on to follow-up communication, specialty routing, corporate agreements and reporting. The two systems work side by side; your front desk team handles correspondence in ÖzgürKod, while medical records stay in your hospital information system.

You assign each rep to one or more branches; with role-based permissions, everyone sees only the conversations and records of their own branch, while management monitors the whole flow. Incoming requests are distributed to the next available rep via round-robin; a conversation coming from chatbot routing lands directly with the relevant branch team. All access is logged — under KVKK (Turkey's personal data protection law), a record is kept of who touched which health data and when. The rep performance report shows response time and conversion by branch.

Company requests come in as leads from the web form or WhatsApp; they are separated by the corporate tag and move through the pipeline's meeting, quote and agreement stages. You send package contents and prices with the PDF quote module and track the Approved/Revised status. Because companies that sign are tagged, when their employees write in, the front desk sees the terms instantly. You send periodic announcements to contracted companies through the campaign module. You set the contract renewal date as a task and follow it in the overdue work view.

In practice they describe the same need. Businesses usually search for "Polyclinic software", "Polyclinic software", "Polyclinic appointment software“ or “customer management software”; “CRM” is this solution is the international name. ÖzgürKod delivers all of these names on one platform: patient communication, appointments, quotes and orders, payment collection and reporting are all in one place. So whatever term you search with, the solution you reach is the same; you don’t need to set up separate software.