Feature
PlannedEmail works. SMS is one registration away. WhatsApp is not built.
The honest state of the messaging channel, because a page claiming otherwise would be found out in the first week.
Patient communication in a clinic is mostly transactional: a one-time code, an appointment confirmation, a report that is ready. In India each channel has its own regulatory gate, and the gate, rather than the software, is usually what delays it.
Where each channel stands
One communication service sits behind all of them, so adding a channel is a provider rather than a rewrite. What differs is regulatory readiness.
- Transactional email, sending
- SMS, built and waiting on the last step of India’s DLT template registration(planned)
- WhatsApp Business, not started(planned)
- Automated appointment reminders(planned)
- Report and prescription dispatch to the patient(planned)
- Recall and preventive-care campaigns(planned)
How it is built
A frontend never talks to a messaging provider. Every message goes through one service on the server, which owns the provider credentials, the template identifiers and the delivery record. That is what makes adding WhatsApp a provider rather than a project, and it is also why no page in the Portal can leak a provider key.
What this does not do
Today the product sends email. It does not send SMS in production, it does not send WhatsApp at all, and it does not send appointment reminders. If patient messaging is the reason you are buying, this is not ready for you yet, and we would rather you knew that from a web page than from a support ticket.
Questions we are asked
Why is SMS not live if it is built?
India requires every transactional SMS template to be registered under the TRAI DLT framework before it can send. Our sender header is approved and the one-time-code template is approved; the remaining step is provider-side wiring and funding. Every other message text needs its own registered template before it can send.
When will WhatsApp be available?
It is planned and it needs a Business Solution Provider account, a verified Meta business profile and per-template approval, the same shape of external dependency DLT turned out to be. We are starting that before the build rather than during it.
Can we send reports to patients?
Through the patient portal, yes. By message, not yet.
Will you charge us for messages?
The provider’s charges are passed through at cost and itemized. We do not mark up your own message traffic.
Other features
Hospital Billing Software
BuiltConsultation, pharmacy and laboratory charges on a single bill, from a fee schedule that varies the way a real tariff varies, printed on your letterhead.
Hospital Appointment Scheduling Software
BuiltWeekly provider schedules define the slots, booking respects them, and a cancelled slot goes back into circulation.
OPD Queue and Token Management
BuiltToken numbers issued at check-in, an arrivals board the front desk watches, and vitals taken wherever your hospital takes them.
Paperless Clinic and Hospital Software
BuiltDigital registration, a digital consultation record, printed documents that carry your branding, and files attached to the patient they belong to.
Hospital Reports and Analytics
BuiltCollections, end of day, and what is still pending, plus a dashboard whose tiles are only clickable when there is somewhere useful to go.
IPD and Bed Management Software
BuiltAdmit a patient to a bed, run their stay, and discharge them: the estate, the bed census, ward tariffs, transfers, the nursing chart and an inpatient bill, all real and in pre-release verification.
See it running with your own workflows.
Book a walkthrough and we will map your clinic or hospital onto the platform, module by module.