Walk down Incilipinar or past the clinics clustered near Gaziantep University Hospital and you will find dozens of single-doctor muayenehane practices where the economics of the front desk never quite add up. A solo GP sees patients from morning until evening. The phone rings during consultations, during lunch, and long after the door is locked. Half the callers speak Turkish; a large share speak Arabic. To cover both languages across a full day you would need two receptionists, and no single-doctor practice in this city generates the visit volume to pay for two shifts. This is exactly the gap the right muayenehane yazilimi is now built to close.
This post works through the actual numbers a Gaziantep solo practice faces, why the "just hire a part-time secretary" answer breaks down here specifically, and how one AI agent covering Turkish and Arabic changes the math.
Why Gaziantep's Language Mix Breaks the One-Secretary Plan
Gaziantep is not an average Anatolian city when it comes to who is calling your clinic. Years of cross-border movement and settlement have made Arabic a working language across large parts of the city, from Sahinbey neighborhoods to the industrial districts where families have put down roots. A muayenehane here does not serve a monolingual Turkish caseload. On any given day the phone carries a mix of Turkish-speaking locals and Arabic-speaking patients, many of whom will simply hang up and try another clinic if the person who answers cannot understand them.
That single fact quietly doubles your staffing problem. A receptionist who speaks only Turkish handles maybe half your inbound calls cleanly. To cover the rest you either hire a second bilingual person, ask one over-stretched employee to muddle through in a language she half-knows, or accept that a meaningful slice of Arabic-speaking callers never becomes a booked appointment. None of those is a good answer for a solo doctor watching every lira.
The illustrative arithmetic is stark. If even a fifth of your inbound calls come from Arabic speakers, and a good portion of those callers give up when they hit a language wall, you are losing bookings every single day that your fixed costs — rent, SGK, the doctor's own time — do not shrink to match.
The True Cost of Two Secretaries in a Single-Doctor Practice
Practice owners tend to think about reception cost as a monthly wage. The real figure is larger and messier. Once you add the employer's social security (SGK) contributions, paid annual leave, sick days, national holidays, and the inevitable turnover of front-desk staff who leave for a hospital job or a call center, one "affordable" secretary costs substantially more than the number on the payslip.
Now try to staff for language coverage and continuous hours and the model falls apart:
- One receptionist cannot answer the phone while she is checking a patient in, taking payment, or on her lunch break. Calls to a solo muayenehane cluster exactly when the front desk is busiest.
- The clinic's useful phone hours stretch well beyond a single shift. Working patients call early, at midday, and in the evening after they leave their own jobs.
- Bilingual Turkish-and-Arabic reception staff are in demand across Gaziantep's clinics and businesses, so wages for genuinely fluent hires are not low, and good ones get poached.
Put those together and honest coverage looks like two people, or one-and-a-half, for a practice that can barely justify one. Meanwhile every unanswered ring is a patient who books elsewhere. The following flow shows where a typical solo-practice call actually leaks.
flowchart TD
A[Patient calls muayenehane] --> B{Front desk free}
B -- No, with a patient --> C[Call goes unanswered]
B -- Yes --> D{Language match}
D -- Turkish --> E[Booking taken]
D -- Arabic, staff cannot help --> F[Caller hangs up]
C --> G[Patient books rival clinic]
F --> G
E --> H[Appointment kept]
G --> I[Lost revenue]Every path that ends in the lost-revenue box is a cost that does not show up on any payslip, which is precisely why it goes unmanaged for so long.
One AI Agent, Turkish and Arabic, From Day One
Here is where a modern AI front desk changes the comparison. Instead of hiring for language and hiring for hours as two separate expensive problems, a single AI agent handles both at once. CallSphere's AI receptionist answers every inbound call, in Turkish or Arabic, and switches based on how the caller speaks — no menu tree, no "for Arabic press 2." It books appointments straight into the practice calendar, answers the routine questions that eat a receptionist's day (opening hours, address near which district, whether the doctor takes a given complaint), and does light triage to flag anything urgent for the doctor's attention.
Crucially, it does this at every hour. The call that arrives at 21:00 from a shift worker in Sahinbey gets answered and booked the same as the one at 10:00. There is no lunch gap, no queue during check-in, and no second-shift wage.
For the persona this post is written for — a solo GP with a large Arabic-speaking base — the multilingual voice capability is not a bonus feature. It is the whole reason the numbers work. You get bilingual coverage without a bilingual hire, and you get it across all 24 hours without a night shift. You can see the full capability set on the /features page, and the plans that a single-doctor practice can actually afford on /pricing.
Running the Real Numbers for a Gaziantep Muayenehane
Let us frame the comparison the way a practice owner would on the back of a receipt. Treat these as illustrative ranges, not quoted figures, because every practice differs.
A single competent receptionist, fully loaded with SGK and leave, is one salaried cost that still leaves you uncovered on language and hours. Adding a second person to close those gaps roughly doubles that line. Against that, an AI agent subscription runs at a small fraction of one salaried receptionist — and it never takes a holiday, never resigns, and never leaves the Arabic calls unanswered.
But the sharper number is the revenue side. Consider a practice that currently misses a handful of bookable calls a day because the line was busy or the caller spoke Arabic. Recovering even part of those into kept appointments, at a typical muayenehane visit fee, can cover the entire cost of the AI within the month — before you count any saving on wages at all. The staffing saving is real, but the recaptured demand is what actually moves a solo practice's income.
flowchart LR A[Inbound demand] --> B[AI answers every call] B --> C[Turkish and Arabic handled] B --> D[24 hour coverage] C --> E[More bookings kept] D --> E E --> F[Recovered revenue] F --> G[Pays for itself before wage savings]
None of this asks the doctor to become bigger than a single-doctor practice. It simply stops the practice from paying, in lost visits, for a front desk it cannot afford to fully staff.
Setting It Up Without an IT Department
The natural worry for a solo GP is that any software with "yazilimi" in the description means a project — servers, a technician, weeks of setup. That is the old model. A cloud AI front desk needs no on-site hardware and no dedicated IT staff. In practice, onboarding a muayenehane looks like this:
- Point your existing practice phone number to the AI, or use a new number, whichever you prefer.
- Tell the system your working hours, visit types, fees, and address, and confirm how you want urgent complaints flagged.
- Load a short list of common questions and answers, in Turkish and Arabic, so callers hear your practice's own information.
- Take a few test calls yourself in both languages, then go live.
The doctor stays a clinician, not a system administrator. Everything runs from a simple dashboard, and changes — a holiday closure, a new fee, an extra appointment slot — are edited in seconds without calling anyone. Because the AI books directly into the schedule and follows up with reminders, the self-filling calendar also cuts the no-shows that quietly drain a solo practice, without adding a task for the doctor.
What Changes for the Doctor and the Patient
The point of all this is not technology for its own sake. It is that a Gaziantep solo GP gets to run a practice that answers every patient in their own language, at any hour, without carrying two salaries the caseload cannot support. The Arabic-speaking family that used to hang up now hears a voice they understand and lands in the calendar. The Turkish-speaking regular no longer gets a busy tone during the lunch rush. The doctor stops being interrupted mid-consultation by a phone only he can answer.
For a single-doctor muayenehane weighing one AI against two secretaries, the honest conclusion is that they are not really the same job. Two secretaries were always an attempt to patch a coverage problem the budget could not fund. One AI agent simply removes the gap — quietly, in two languages, around the clock — and lets the doctor get back to the patients in front of him.