Case Study: Before and After EKSENAI — A Clinic’s Intake System in Their Own Words

Before we installed the system, I would walk into the clinic on Monday morning and my first question was always the same: “How many leads did we get this week?” The answer was always a version of the same shrug. Not a number. Not a breakdown. A shrug. Maybe a rough estimate from whichever coordinator I happened to catch first. “I think maybe 30? Ask Sara, she had the WhatsApp on Friday.”

Last Updated: 20260821T0

That clinic had 5 coordinators, was receiving 100–150 inbound leads per month across rhinoplasty and liposuction inquiries from Germany, the Netherlands, and the Gulf, and was spending €2,800/month on Google Ads. They had no idea what happened to most of those leads. What follows is a composite case study based on the pattern I see repeatedly across Istanbul clinics at this scale, the details are anonymized and combined, but nothing in this account is fabricated. Every failure mode described here is real. I’ve seen all of it.

What Did a Typical Monday Morning Look Like Before?

The clinic director: I’ll call him Kerem, arrived at 9:00 AM every Monday and spent the first 90 minutes trying to reconstruct the previous week’s intake from whatever information he could gather. This was not a management failure. It was the only option available to him.

Sara had the main WhatsApp Business number on her phone. She had responded to leads over the weekend from her personal device because the business number was only accessible from the office desktop and she’d been working from home Saturday. Those conversations existed on her personal phone. They were not logged anywhere. She hadn’t had time to enter them into the clinic’s spreadsheet because it was the weekend and she was handling the conversations as they came in, not transcribing them.

Ahmed had been handling Arabic-speaking Gulf leads from a separate WhatsApp number the clinic had set up for that market. He was on leave Monday. The number was on his personal phone. The number was unavailable. Three leads from the previous Friday had not been responded to. Nobody in the clinic knew this until a patient called the main line on Monday afternoon to ask why no one had gotten back to them.

The spreadsheet, the closest thing the clinic had to a CRM, had 34 lead entries for the previous week when Kerem counted them on Monday. Based on what he knew about ad spend and typical traffic, he estimated the actual lead volume was 90–110. The gap between 34 and 90 was not fraud or incompetence. It was what happens when coordinators are responsible for manually logging conversations that happened on phones they were also using for personal communication, in the middle of actual patient conversations, without a system that made logging easier than not logging.

Kerem’s Monday morning question — “how many leads did we get?”, was unanswerable because the answer lived in five different phones, two different WhatsApp numbers, and a partially-updated spreadsheet. He was running a business on anecdote.

What Does Monday Morning Look Like Now?

“I open my laptop before I leave the apartment,” Kerem told me three months after the system went live. “I see exactly what came in over the weekend. I can see every conversation. I can see which ones got a response and when. I can see which ones are still open. I can see if Ahmed didn’t respond to something: I can see the timestamp on the last message. Before, I would have found out about that on Tuesday if I was lucky.”

The change is not primarily about the dashboard. It is about what the dashboard enables. Before, Kerem managed coordinators by presence and intuition. He could sense when something was off but had no way to pinpoint it. Now, when he sees that a coordinator’s TFCR has dropped from 92% to 71% over a week, he has a specific conversation to have. Not “I feel like you’ve been less responsive lately”, a conversation that coordinators can dispute and that creates tension without resolution, but “your first-response compliance dropped 21 points this week, let’s look at why.”

The coordinators, initially resistant to the new system, now describe it as easier than what they were doing before. The manual logging work, which was the most friction-prone part of their day, is handled by n8n automatically. Every incoming conversation is logged to Supabase with the patient’s contact, message content, timestamp, and channel. The coordinator’s job in the new system is to respond and advise, not to administer. Sara, who previously estimated she spent 30–40% of her time on logging and administrative tasks, now estimates that’s under 10%.

What Were the Three Most Significant Operational Changes?

1. The First-Response Problem Was Solved Without Hiring

Before the system, the clinic’s average first-response time was 47 minutes. This was not because coordinators were slow, it was because coordinators had to be physically present and logged in to respond, and the Monday-Friday, 9-to-6 operational window left a significant volume of leads arriving outside those hours unattended. A German patient who sends a WhatsApp inquiry on Friday at 7:00 PM, which is a common pattern, since German patients research in evenings after work, was waiting until Monday morning for a response, if they got one at all.

The EKSENAI system deploys an automated first-response via n8n and Evolution API that fires within 90 seconds of any incoming message, 24 hours a day. The automated response acknowledges the inquiry, requests the relevant clinical information (photos for hair/cosmetic assessment), and sets a timeline expectation for human follow-up. The patient knows they have been heard. The lead is logged. The coordinator receives a notification and queues the follow-up for their next working window.

The average first-response time across the system is now 3 minutes 20 seconds. The effective first-contact is instant. This change alone accounts for a measurable increase in consultation-to-lead conversion, because patients who receive an immediate acknowledgment are significantly more likely to still be engaged when the coordinator follows up.

2. Management Now Has a Revenue Conversation, Not a Headcount Conversation

Before the system, Kerem’s lever for improving intake performance was hiring. If leads were being missed, the answer was another coordinator. If follow-up was falling behind, the answer was another coordinator. He had no visibility into whether the problem was volume or efficiency, whether he needed more people or whether his existing people needed a better process.

After the system, Kerem can distinguish between a volume problem and an efficiency problem. When the dashboard shows 110 leads in a week with a 91% first-response rate and a 38% consultation conversion, the question is “where are the 62% that didn’t reach consultation and why?”, which is a pipeline design question. When the dashboard shows 140 leads with a 71% first-response rate and a 28% consultation conversion, the question is “do we have a capacity problem or a process problem?”, which is a resource question. These are different questions requiring different answers, and before the system, Kerem could not distinguish between them.

3. Coordinator Accountability Became Operational, Not Personal

The most unexpected change Kerem described was what happened to the coordinator team culture. Initially, the prospect of management visibility into conversation-level activity created anxiety. Coordinators were concerned about being monitored. In practice, the monitoring function was less significant than the accountability structure it created, and that structure turned out to benefit coordinators as much as management.

Before, when a patient claimed they never received a follow-up, there was no way to verify. Coordinators were sometimes blamed for failures that weren’t theirs. A lead that had been lost in the Coordinator Black Box before the system was installed would be attributed to coordinator negligence even if the coordinator had responded, the response just wasn’t logged, so management had no evidence either way.

After the system, every interaction is timestamped and logged. A coordinator who responded promptly has proof. A lead that was missed has a clear record of when it arrived and when (or whether) it was addressed. The accountability works in both directions, which is why coordinator adoption of the system, after initial resistance, became genuine rather than grudging.

What Is the Underlying Principle?

The underlying principle is that an intake system is not a productivity tool, it is the management layer of the business. Before EKSENAI, Kerem was managing a clinic whose core revenue function, converting leads into bookings, was entirely invisible to him. He was making decisions about hiring, marketing spend, coordinator performance, and operational priorities based on information that was partial, delayed, and self-reported by the people it described.

After EKSENAI, he is managing with data. Not perfect data, every system has gaps and the team is still calibrating, but data that is independently generated, timestamped, and queryable. The system does not make decisions for Kerem. It gives him the information he needs to make decisions himself. That is the standard EKSENAI builds toward in every partner clinic deployment.

---

Frequently Asked Questions