Why Turkish times get misheard in phone bookings: the 'dörde çeyrek var' test

A patient calls a clinic in Turkey and says, in Turkish, that she can come tomorrow at "dörde çeyrek var". She means 15:45. The record says 16:15. She arrives on time and the chair is taken. Nobody spots an error, because the record shows a perfectly normal time.

This article looks at how Turkish time, day and phone number expressions get silently misread when speech on a call or a voice message is turned into text. It is a finding about Turkish specifically. The source is our own testing: on 23 September 2026 we ran Turkish expressions one by one and checked how each one ended up in the booking. The lessons apply to any clinic or salon that books by phone in Turkish, with or without an AI assistant.

Three outcomes: right, a question, silently wrong

A sentence spoken on the phone is first turned into text, and the appointment is read from that text. We put every expression into one of three classes.

• Right: the day and time land where the caller meant.
• Safe refusal: the system is not sure, leaves the field empty and asks the caller.
• Silently wrong: with no warning, it writes a different day, time or number.

The third one is the danger. A system that asks keeps the caller waiting a few seconds. A system that books the wrong time keeps the patient waiting at the door, and nobody notices until then.

What we found

The test used a fixed moment: Wednesday 23 September 2026, 10:00. Opening hours were Monday to Saturday, 09:00 to 20:00. So "tomorrow" means 24 September and "Monday" means 28 September.

In our own tests, 10 Turkish time patterns (18 separate phrasings) and 9 day patterns (12 phrasings) fell into the silently wrong class. Another 13 patterns went wrong when the day and the time were said separately and got mixed up. Phone numbers had 2. The most instructive cases are below, with a short English gloss.

Why Turkish times slip

The most common trap is the word "var". In everyday Turkish, "dörde çeyrek var" means the same as "dörde çeyrek kala", a quarter to four. When "var" was not recognised as "to", the numbers were read as "past" and the time moved forward. Other phrasings such as "çeyrek kala dört" and "üç buçuk" (half past three) were read correctly. The problem sits in certain patterns, not in Turkish times in general.

The second source is digits. When "15 30" or "11,30" reached the text in that form, the minutes were dropped and the time was rounded to the full hour. The third is a single letter. Turkish "geçe" means past, and "gece" means night. When the letter ç was lost in the text, a quarter past three became 03:15 at night and a closed hour was offered.

The fourth is self-correction. A caller who says "üç değil dört" corrects herself, but the first number was the one that got booked.

Why Turkish days slip

In Turkish the lower-case form of a capital I is a dotless ı. "PAZARTESI" in capitals became "pazartesı" when lowered, the word was not recognised and the day was read as Sunday. "CUMARTESI" became Friday. "Yarından sonra" was read as tomorrow and "haftaya bugün" as today, because only the first word counted.

"Ayın onu üçte" is two numbers merging. The 10th and "at three" sat side by side and became the 13th. "Cumartesi 10.10" was taken as the date 10 October instead of a time.

The costliest findings came when the day and the time were said separately. A caller said only "ayın on beşi", the 15th, and gave no time. The record showed a firm booking on 15 October at 15:00. For "5 ekim", 5 October, it wrote 17:00. A time said as "saat 11.05'te" became the date 11 May 2027. In other words, a time nobody said could be invented.

Phone numbers: an error the text cannot reveal

For Turkish phone numbers, most phrasings were either read correctly or the system asked. Two patterns stayed silently wrong. When one "iki" (two) in "iki yüz yirmi üç" (two hundred twenty-three) was lost, 223 was saved as 123. When the final "yedi" (seven) in "altmış yedi" (sixty-seven) was lost, 67 became 60.

We could not fix these two, because the text looks exactly like a correctly read number. The fix sits outside the text: use the caller's number when it is visible, and read the number back in groups when it is not.

Ask when unsure, always read back

The test also showed good behaviour. For vague answers such as "yarım" (half), "1430", "birazdan" (shortly) or "fark etmez" (any time), the system did not invent a time. It asked. When a caller offered two options, the first was booked and read aloud at confirmation, so the caller could correct it there. That is the right design: when unsure, ask instead of guessing.

We fixed the time and day patterns we found in testing and added them to our tests. That does not mean every way of saying a time in Turkish is covered, and a new pattern can always appear. So the same rule holds for an assistant and for your staff: time, day and number are read back before they go into the booking.

Checklist for anyone booking by phone in Turkish

1. Read the booking back with date, weekday and digits: "Monday 28 September, 15:30, is that right?"
2. When you hear "var" or "kala", repeat the time in digits. "Dörde çeyrek var" is 15:45.
3. Do not mix up "geçe" and "gece". Ask plainly whether it is morning or afternoon.
4. If the caller corrects herself with "değil", book the last thing said and read it back.
5. Turn "yarından sonra", "haftaya bugün" and "öbür gün" into a date and say it aloud.
6. If the day of the month and the time come in one sentence ("ayın onu üçte"), confirm each one separately.
7. If no time was given, do not write one. Ask.
8. If the caller gave two options, say which one you booked.
9. Read the phone number back in groups. If the caller's number is visible, use it.
10. In written messages, look twice at weekday names that arrive in capitals ("PAZARTESI").

We cover the full booking flow in our articles on clinic appointment automation and beauty salon booking automation. If you want an assistant that also answers the phone and writes bookings to your panel, see the AI Receptionist. Whatever system you choose, run this checklist on your own test call first.