When Doctors Start Referring Other Doctors, Something Real Is Happening | Care Beyond Clinic - Slincas
Founder Notes
When Doctors Start Referring Other Doctors, Something Real Is Happening
Sl
Posted by
Slincas Team
Posted onApril 19, 2026
6 min read
I've spent the past several years trying to understand one deceptively simple question: why is communication inside healthcare still so broken?
Not the clinical side — diagnosis, treatment, outcomes. Those workflows have been refined over decades. I mean the human side. The message at 10pm from a patient who just needs reassurance. The staff member who can't find which WhatsApp conversation holds the image the doctor needs. The front desk coordinator managing three platforms at once, none of them designed for a clinical environment.
I've been a dentist for over 25 years. I've lived inside these workflows. And what I've come to understand is that the problem isn't a lack of technology. It's that the technology being used was never designed for healthcare in the first place.
This week, two conversations made that clearer than ever.
A Referral Nobody Asked For
The first came unexpectedly.
A doctor I'd been speaking with — someone who had shared with me, in detail, the communication chaos inside her clinic — called me out of the blue. Not to ask a question. Not to follow up. She called to refer a colleague.
"I told him about what you're building," she said. "He needs this."
I want to be precise about what that moment meant — because it wasn't a sales win. In medicine, a referral is something specific. It's a transfer of trust. When a clinician puts their professional name behind a recommendation to a peer, they are staking their credibility on it. That is not done lightly.
This was a doctor saying: I believe in this enough to attach my reputation to it.
When I started building Ekko, I knew the problem was real because I had lived it. But there is a difference between knowing a problem exists and watching clinicians validate it independently, peer-to-peer, without any prompting. That kind of signal doesn't come from a survey or a focus group. It comes from trust that has already been earned.
When doctors start quietly referring other doctors, something real is happening in the market.
The WhatsApp Bot Meeting
The second conversation was different in character — but equally instructive.
I have a meeting scheduled this week with a clinic that didn't wait for someone to solve their communication problem. They built something themselves. WhatsApp bots. Automated flows. Scripted responses to handle inbound patient messages.
I haven't seen the demo yet. I genuinely don't know whether what they built is working beautifully or showing cracks. That's exactly what I'm going to find out — and I'm going in curious, not assuming.
What I already know is this: they felt the problem sharply enough to engineer a response to it. That is not a failure story. That is a team that takes patient communication seriously. And the work happening at the intersection of healthcare and technology in India right now — quietly, with genuine clinical intent — makes me proud.
But it also surfaces an important question worth thinking through carefully.
The Difference Between Solving a Symptom and Solving a Problem
WhatsApp bots are a logical response to a very real pain: the volume of inbound messages that clinic staff simply cannot keep up with. If a bot can handle appointment confirmations, reminders, and basic FAQs, that frees staff to focus on higher-value interactions.
That logic is sound.
The challenge is that WhatsApp itself — regardless of what you build on top of it — was designed for personal, informal, unbounded communication. There is no audit trail. Patient images can be screenshotted and forwarded. Staff personal numbers remain exposed to patients. Conversations scatter across individual phones rather than a shared clinical inbox. A bot can make the platform faster. It cannot make it structured.
In clinical environments, structure isn't a feature — it's a compliance requirement and a safety mechanism.
The platform problem doesn't disappear when you automate the responses. It just becomes quieter.
What Clinics Actually Need
Ekko was built on a straightforward premise: patients, staff, and clinicians all have legitimate but different needs from the same communication system.
Patients need connection — a way to reach their clinic quickly, with confidence that their information is secure.
Staff need clarity — a structured inbox with role-appropriate visibility, not an infinite scroll of personal-feeling messages across a platform with no off switch.
Clinicians need oversight — the ability to see what's being communicated on behalf of their practice, with a permanent, timestamped record they can trust.
WhatsApp, for all its convenience, cannot satisfy all three simultaneously. Its architecture works against it.
That's the structural gap Ekko exists to fill. Not another tool layered on top of a broken foundation — but a purpose-built communication layer designed specifically for the clinical context.
Why This Week Matters
Two conversations. Two very different places in their journey. Both pointing to the same underlying reality: the market knows something is wrong, and it's actively searching for answers.
The referral told me trust is forming. The WhatsApp bot meeting told me urgency is real.
We're still early. But the clearest signal that you're building something necessary is when the people who understand the problem best — clinicians, clinic owners, healthcare teams — start finding each other and pointing toward you.
That's what happened this week.
And it reminded me exactly why we built Ekko.
Ekko Medical is a secure patient communication platform designed for clinics across Singapore and Asia. Available on iOS and Android. Learn more at ekkomedical.com or book a free 15-minute demo.