# WhatsApp automation for diagnostic labs

A diagnostic lab should automate the home-collection confirmation, the phlebotomist’s arrival window, the authorised-report notification and the doctor’s referral copy. Reports travel as expiring links rather than attachments, and nothing is sent before a pathologist has signed the result off.

> Source: MyFloww, a software studio in Bengaluru, India. Canonical page: https://myfloww.in/for/diagnostic-labs/whatsapp-automation/. Last reviewed 2026-09-04 by Neel.

## How diagnostic labs in India actually operate

A diagnostic lab in India sells turnaround time and trust, not tests. The operating shape is hub and spoke — collection centres and home phlebotomists feeding a central processing lab — so the same result survives several handoffs before it reaches a patient, and every handoff is somewhere the sample or its identity can be lost. Two customers exist at once: the patient who paid, and the referring doctor whose repeat referrals are the volume.

## The workflow we build around

1. **Booking, increasingly for home collection** — A patient books a test or a package by phone, on WhatsApp, through an aggregator or at a collection centre. Home collection has moved from a premium add-on to an expectation in metros, which puts a phlebotomist’s route at the front of the operation.
2. **Collection and barcoding** — The sample is drawn and labelled, and this is the moment identity is either locked to the sample or lost. A barcode generated at collection and scanned at every later step is the difference between a traceable result and a repeat draw.
3. **Transport to the processing lab** — Samples travel from centres and home visits in batches, some temperature-sensitive with real stability windows. The promised turnaround starts here, and this is the part of the chain with the least visibility.
4. **Processing and pathologist authorisation** — Analysers produce results into the lab information system, and a qualified pathologist reviews and authorises before anything is released. This step is not optional and not automatable, and it is the single most important constraint on anything built around a lab.
5. **Delivery to the patient and back to the referring doctor** — The authorised report goes to the patient, usually as a link or PDF, and separately to the doctor who referred them. The doctor’s copy generates the next referral, and it is the one most often forgotten.

## Integrations that matter for WhatsApp Business API automation here

**The authorisation event in the lab information system**
: The one trigger that matters is a pathologist signing off a result, not an analyser finishing a run. Wiring the message to authorisation is what makes fast delivery safe; wiring it to the analyser makes an unreviewed number a patient’s problem. Everything else in a lab’s WhatsApp build is scheduling by comparison.

**The phlebotomist’s route and live status**
: The most-asked question in a home-collection service is when somebody is arriving, and it is asked by phone, one patient at a time, to a coordinator who is guessing. An arrival window pushed from the actual route turns the busiest interruption of the day into a message, and a delayed visit into a notification rather than a complaint.

**Expiring, access-controlled report links**
: A report PDF in a chat thread is sensitive health data on whatever device that account is next opened on, and phone numbers get mistyped and reassigned. A link that expires and verifies the recipient delivers the same result with a revocation path, which is the defensible position rather than merely the cautious one.

**Payment links against the booking**
: Home collection means money changes hands in the field, and cash reconciles worst. A link sent with the confirmation and settled before the phlebotomist arrives removes cash from the visit entirely and attaches the payment to the order rather than to a day.

## Constraints that change the build

- **No result leaves the lab before a pathologist authorises it.** An analyser producing a value is not a result. Release requires review and sign-off, so any delivery automation is triggered by the authorisation event and never by the analyser. A system that can be configured to auto-release is a system that eventually will be.
- **NABL accreditation demands end-to-end traceability.** Accreditation requires every result to be traceable through who collected the sample, when, which analyser ran it, which calibration was current and who authorised release. That makes the audit trail structural rather than a feature, and rules out any step done outside the system.
- **Reports are sensitive health data on consumer channels.** A report sent to a phone number is a diagnosis on a device that may be shared, and a wrong number is a disclosure. Under the DPDP Act this is sensitive personal data, so expiring links that verify the recipient are the defensible pattern rather than attachments that live in a chat forever.

## What it costs

| Scope | Price (INR) | Typical timeline |
| --- | --- | --- |
| Booking confirmations, arrival windows and authorised-report notification | ₹1,40,000 – ₹3,00,000 setup, plus API message costs | 3 – 5 weeks |
| Two-way flows with rescheduling, payment and doctor referral copies | ₹3,00,000 – ₹6,00,000 setup, plus API message costs | 5 – 10 weeks |

These are bands MyFloww would honour, not indicative ranges. Every project is quoted
individually after scoping.

## A worked example

**Context.** A lab with a growing home-collection service was absorbing the same two calls all day: when is the phlebotomist coming, and is my report ready. Both were answerable from data the lab already held, and both were being answered by a person reading a screen aloud.

**What was built.** Confirmations and arrival windows pushed from the route, and report notifications triggered by the pathologist’s authorisation rather than by processing completing. Reports moved from attachments to expiring links, and the referring doctor’s copy went on the same trigger instead of being compiled later.

**What changed.** The two questions largely stopped arriving, freeing the coordinator for calls that needed judgement. The unplanned effect was on referrals: doctors who had been chasing the lab started receiving reports automatically, which changed how easy the lab was to work with more than any patient-facing message did.

## What goes wrong with WhatsApp Business API automation for diagnostic labs

- Sending the report PDF as an attachment because it is one step fewer for the patient. It is a permanent copy of a diagnosis on a device the lab knows nothing about, with no way to withdraw it after a mistyped number.
- Triggering "your report is ready" when processing finishes rather than when a pathologist authorises. The gap between those two events is where the clinical safety of a lab’s reporting sits, and shaving hours off a statistic is not a reason to close it.
- Promising a home-collection slot as a fixed time rather than a window. Traffic and preceding draws make a precise time a promise the phlebotomist cannot keep, on a service whose whole proposition is not having to leave the house.

## Questions

### Is it safe to send diagnostic reports over WhatsApp in India?

It is defensible as a notification channel and questionable as a delivery channel. Send a message announcing the report and a link that expires and verifies the recipient, rather than the PDF itself. A report is sensitive personal data under the DPDP Act, numbers get mistyped and reassigned, and an attachment cannot be withdrawn once it has reached the wrong person.

### Can the report notification be sent as soon as processing finishes?

No. It waits for the pathologist’s authorisation, because an analyser value is not a result. Built correctly the patient hears within moments of sign-off, which is faster than any manual dispatch, and nothing leaves the lab that a qualified person has not reviewed. Any system offering auto-release on processing is offering a shortcut nobody should take.

### What is the most valuable message for a lab to automate first?

The phlebotomist arrival window, where home collection is a real part of the business. It is the highest-volume inbound question, answerable from data the lab already has, and it is the moment the service either feels reliable or does not. Report notification is close behind and easier to justify, but replaces fewer phone calls.

### Should the referring doctor get a copy over WhatsApp too?

Yes, and it is the message most often left out. Referrals are the volume in this business, and a doctor who receives their patients’ authorised reports without chasing is a doctor who refers again. Send it on the same authorisation trigger, to a verified number, with the same expiring-link treatment.

### Does a lab need the WhatsApp Business API for this?

Yes. Every message described here is triggered by something happening in another system — a route starting, a result being authorised — and only the API sends template messages on an external trigger. Meta bills per conversation at its own published rates on top of the build, and utility conversations are priced differently from marketing ones.

## About diagnostic labs generally

### Why is turnaround time the product for a diagnostic lab?

Because the test itself is a commodity — the same panel on the same analyser gives the same number anywhere. What a patient and a referring doctor choose between is how fast the authorised report arrives and how reliably. A lab that can state turnaround per stage, and hold to it, is selling something its competitors cannot describe.

### Who is the real customer, the patient or the referring doctor?

Both, and they want the same result delivered completely differently. The patient wants their report on their phone the moment it is signed off. The doctor wants a consolidated view of everyone they referred and the turnaround they experienced. Referrals are the volume, so the doctor’s view is a revenue channel rather than a courtesy.

### What does NABL accreditation actually require from software?

That every result is traceable end to end: who collected the sample and when, which analyser ran it, which calibration was current, and who authorised release. If every handoff is a scan and every release is an authorisation event with a named person against it, the evidence an assessor asks for already exists rather than being assembled beforehand.

### Is home collection worth building for?

In metros it is no longer optional. It changes the operation more than it looks: money moves in the field, barcodes have to be printed at a kitchen table, routes have to respect sample stability windows rather than only distance, and the busiest inbound question becomes when somebody is arriving.

### Should a lab replace its LIS?

Almost never. The lab information system holds analyser interfaces, validation rules and the accreditation evidence trail, and replacing it means re-earning all of that for functionality that already works. The gaps worth commissioning sit outside it — home collection, payment in the field, multi-centre reconciliation and the doctor’s view.

## Related

- Industry hub: https://myfloww.in/for/diagnostic-labs/
- WhatsApp automation in general: https://myfloww.in/whatsapp-automation/
- Nearest industry: https://myfloww.in/for/dental-clinics/
- Nearest industry: https://myfloww.in/for/physiotherapy-clinics/

---

MyFloww · software studio · Bengaluru, India · connect@myfloww.in · https://myfloww.in