Three polite messages, an empty room
The patient read none of them. The slot sat empty, nobody was told, and the money was simply gone. The plugin’s job ended when the reminder was delivered — and that is where the whole problem starts.
Kavita’s story
Built in a clinic that was losing money every morning.
Not a market study. A physiotherapy practice, a diary full of holes, and a number the owner could name to the rupee every month.
Kavita exists because the software that practice had already paid for did nothing about the one thing costing it money. Every feature here was tested on a live site taking real payments from real patients, where being wrong meant somebody’s afternoon was wasted and somebody’s money was actually missing.
The problem nobody was solving
Every plugin sends reminders. None of them can hear the answer.
11:00 Friday just freed up
Kabir N. — offered 09:12expires in 48 min
Priya M.next, if Kabir declines
Sana I.third
One offer at a time, never everybody at once — and it says plainly that the slot is not held.✓ auto-refilled
Amelia’s own documentation
“WhatsApp messages do not support two-way communication. If a customer replies to the message, the reply will not appear in Amelia.”
That is not an oversight, it is architecture. Receiving a reply means a webhook, a conversation state per phone number, a session window that respects Meta’s rules, and an intent parser careful enough to be trusted with the word cancel. None of that is a checkbox somebody forgot.
Which is exactly why it took building a plugin rather than filing a feature request — and why it is the one thing on this site a competitor cannot answer with a point release.
The bug that shaped the product
Money authorised, and never captured.
We shipped it. We found it on a live clinic. The patient’s card showed a charge, the dashboard showed nothing, and it would have surfaced weeks later when the authorisations expired — or when somebody phoned to complain.
What changed
Capture is verified before a booking is ever marked paid. Gateway webhooks reconcile anything the browser missed, and a released slot is re-taken rather than lost. Thirteen gateways, one behaviour.
Why it is still on this page
Because software that touches somebody’s livelihood earns trust by what it does when it is wrong, and hiding the worst bug we ever shipped would be the wrong lesson to have learned from it.
What it made permanent
The payment path is the most defended code in the product. The server recomputes every amount; the client only ever names a coupon or a card, never a price.
What we refuse to build
No symptom triage. Not ever.
An agent reading “sharp pain down the left leg” and flagging red flags sounds valuable, demos beautifully, and is a regulatory tar pit that ends with software practising medicine. Clinical advice is refused everywhere in this product, and it does not come back in through a side door because a customer asked nicely.
“A cheaper plan that can double-book is not a cheaper product. It is a broken one — and the patient who arrives to an occupied room did not choose your tier.” The rule that decided what would never go behind a paywall
Honesty
What is not true of Kavita, today.
Everything else on this site is an argument from source code. This is the part the argument does not cover. When a line here stops being true it comes off the page, with the date it changed.
Written
64 capabilities
Tested against a mock
1,338 checks
Run in production
one clinic, one plugin ago
Fifty-five dated releases, and almost none of it has run in anger.
- No gateway has taken a real payment. Thirteen integrations, every signature scheme pinned by a known-answer vector — which tests the cryptography, not the integration.
- Neither AI agent has called a real provider. A hundred and three checks, all against a mock.
- No importer has read a real installation, and no WhatsApp template has been submitted to Meta for approval.
- Nobody has seen this product on a screen. No screenshot exists, which is why every image on this site is drawn rather than captured. Mobile is a first pass never checked on a device.
- The owner’s app does not exist. It is badged In build everywhere it appears, and the day that badge comes off without the app existing, this page starts lying.
- Nobody can buy it yet. No store, no update channel, no licence ever issued.
Where it is now
Sixty-four capabilities, and a free plan to check them on.
One practitioner, no card, no clock. Install it beside whatever you run today and import your data in a dry run that writes nothing.