WhatsApp is the interface

Every product we ship has a WhatsApp surface. Healthixio's front desk can be run from it. Pathixio sends every authorised report through it. Biznixio's follow-ups go out on it. This is not because WhatsApp is fashionable. It is because, for the people our customers serve, WhatsApp is the only app that is reliably installed, open and understood.

The app that is already open

A patient in a district town will not install a hospital's app to see one lab report. They will open a WhatsApp message from a number they recognise. A gym member will not check a portal for their renewal date; they will read a reminder. Designing around this is not lowering the bar. It is meeting people where they are, which is the whole job.

What we built on it

• Healthixio's WhatsApp agent: a receptionist scans a QR code and can book an OPD appointment by typing a name and a time, or dictate a discharge summary as a voice note that comes back as structured text for the doctor to approve.
• Pathixio report delivery: the moment a pathologist signs a report, a PDF on the lab's letterhead goes to the patient and, if the lab wants, to the referring doctor.
• Biznixio follow-ups: templated messages for demos, renewals and dues, with the reply landing back in the CRM against the right party.
• A WhatsApp inbox we built for a client: bulk campaigns from a spreadsheet, an AI auto-reply with a human handover, and per-message cost tracking.

The rules the platform imposes

The WhatsApp Cloud API is not a free-for-all, and software that pretends otherwise will get the business's number blocked. Three rules shape every design.

1. The 24-hour window. A business can send free-form messages only within 24 hours of the customer's last message. Outside it, only pre-approved templates are allowed. Good software shows the countdown and swaps the composer for a template picker when the window closes.
2. Templates are reviewed. Every outbound template goes through Meta's approval, with variables like {{1}} for the patient's name. Writing templates that pass review, and that do not read like spam, is a skill.
3. Every message costs money. Conversations are billed by category and country. A campaign of ten thousand messages should show its cost before the send button is pressed.

Where WhatsApp is the wrong tool

WhatsApp is a channel, not a database. The record of a patient, a sale or a member lives in the system, and the message is a copy of it. Anything that needs an audit trail, a signature, or a consent artefact goes through the system first and reaches WhatsApp second. And some things should not go through it at all: a lab result that needs a doctor's explanation is better delivered by a phone call, and the software should make the call easy rather than the message automatic.

Design rules we follow

• The message is a copy; the system is the record.
• Show the 24-hour window and never let a user send something that will be rejected.
• Show the cost before the send.
• Every automated reply has a way to reach a human in one message.
• Consent to be messaged is captured at registration, and opting out is one word.

If you are building something that should live on WhatsApp, we can help.