Chennai · WhatsApp automation
WhatsApp automation in Chennai.
Delivered remotely from BengaluruReviewed 2026-09-22Read as markdown
Where we actually are
We do not have an office in Chennai.
MyFloww does not have an office in Chennai. The studio is in Bengaluru and this work is delivered remotely, which is how every project outside Bengaluru runs. Said here because a page that implies a local presence it does not have is worth less than no page.
Prices on this page are national. MyFloww quotes on scope, not on postcode, so this is the same number it would be anywhere else in India — how pricing works.
The market
What Chennai commissions, and why.
Chennai runs on manufacturing and on medicine, and both of its software markets are shaped by customers who are not in Chennai. The Sriperumbudur and Oragadam belt builds vehicles and electronics largely for export and for national distribution, so its systems answer to foreign parent companies and global quality processes. Its hospitals draw patients from West Asia, Africa and South Asia, so their digital presence has to work for somebody planning a journey months ahead in a language and currency that are not local. Underneath both sits a domestic market that is genuinely Tamil-first — which is the single most commonly underestimated fact about selling anything online in this city.
What it has to account for
WhatsApp automation, here specifically.
- Long-running conversations that survive staff changes
- A treatment-travel enquiry can run for months. If it lives on one coordinator’s phone, a resignation mid-journey loses the entire history at the worst possible point for the patient and the hospital.
- Controlled report exchange rather than files in a thread
- Patients send scans and reports and expect estimates back. Those are health records crossing borders, and an expiring, access-controlled link keeps them under the hospital’s control instead of permanently resident in a chat.
- Tamil and English templates for the domestic side
- Local appointment, admission and follow-up messaging lands better in Tamil, and template approval has to be planned for both languages rather than discovered after the English set is live.
- Timezone-aware scheduling of outbound messages
- An automated reminder that arrives at 4am in Dubai or Lagos is worse than none. Sending against the recipient’s local time is a small build decision with a large effect on whether the channel stays welcome.
On the ground
What is actually true of doing this in Chennai.
- The coordinator’s phone is the single point of failure
- In most Chennai hospitals running international patient work, the entire relationship sits in one person’s WhatsApp. It is invisible to management, unrecoverable on resignation, and it contains health records the hospital is responsible for. This is usually the argument that funds the project.
- Template review in two languages takes longer than teams plan for
- Bilingual template sets go through review as separate items, and health-adjacent wording attracts more scrutiny. Planning for both from the start avoids a launch that goes live in English and waits weeks for its Tamil half.
Constraints
What changes any build in Chennai.
- Tamil Nadu has its own clinical establishments Act
- Clinical establishments in Tamil Nadu are governed by the state’s own 1997 Act rather than by the central Clinical Establishments Act, 2010, which the state has not adopted. The registration identifiers, renewal process and obligations therefore differ from Telangana or Rajasthan, and practice software that models one national registration scheme describes none of them correctly.
- Tamil script is the market, not an accessibility feature
- A large share of consumer search in this city happens in Tamil script. That has practical build consequences — font subsetting and loading for a script with a large glyph set, input validation that accepts Tamil names, URL and slug decisions, and search that matches across both scripts. Treating it as a late-stage translation produces a site that is slow and broken in the language most of its customers use.
- International patients need estimates before they need appointments
- A family deciding whether to travel for treatment needs an indicative cost, a duration, a visa-support position and a view on accommodation — in that order, and long before booking. Hospital sites built around a local outpatient booking flow answer none of it, and the enquiry goes to a facilitator who takes a commission instead.
- Foreign parent companies set the standards their Indian plants build to
- A Sriperumbudur plant owned from Korea, Japan or Taiwan inherits its parent’s data, quality and security expectations. Those are frequently stricter than local norms and they are non-negotiable, so they belong in the specification rather than in a change request after the security review.
Cost
What it costs, and how long it takes.
| Scope | Price (INR) | Typical timeline |
|---|---|---|
| Business API with bilingual templates, takeover and controlled file exchange | ₹90,000 – ₹1,80,000 | 3 – 6 weeks |
| Tied into the hospital system with estimate tracking and journey stages | ₹2,00,000 – ₹3,80,000 | 6 – 11 weeks |
What goes wrong
The mistakes we see in Chennai.
- Running international patient coordination on personal numbers. The records are the hospital’s responsibility and the history disappears with the employee.
- Accepting and returning reports as files in the chat thread. They are permanent, forwardable health records outside any consent framework the hospital can honour.
- Sending automated reminders on Indian office hours to patients abroad. It reads as careless at exactly the point the family is deciding whether to trust you with surgery.
- Launching English templates first and treating Tamil as a later phase. The domestic patients are the volume, and they get the worse experience for months.
Questions
What Chennai businesses ask.
Why move international patient coordination onto the Business API?
Because the relationship currently lives on a coordinator’s personal phone, along with the patient’s reports. The API makes it a hospital record with continuity across staff changes and controlled handling of the health data, which is both an operational and a responsibility question.
Can reports be exchanged safely this way?
As access-controlled links that expire, not as files attached to the thread. A PDF in a chat is permanent and forwardable and cannot be withdrawn; a link can be revoked and its access logged, which is what the hospital needs to be able to show.
Will messages go out in Tamil as well as English?
Yes, and both template sets are planned together because they are reviewed separately and health-adjacent wording attracts scrutiny. Launching English first and leaving Tamil for later gives the majority of your patients the worse experience.
What does this cost and how long does it take?
₹90,000 to ₹1,80,000 for bilingual setup with takeover and controlled file exchange, in three to six weeks. ₹2,00,000 to ₹3,80,000 tied into the hospital system with estimate tracking and journey stages, over six to eleven weeks.
This page is also available as clean markdown with no navigation or styling, for anything that would rather read it that way. Last reviewed 2026-09-22 by Neel.
Where to next
- WhatsApp automation, in general
How MyFloww approaches WhatsApp Business API automation for any business in India, not only in Chennai.
- Everything we build for Chennai
The city hub: the market, the sectors, the constraints and the other services we publish for it.
- WhatsApp automation in Hyderabad
The same service in a nearby market, where the constraints differ.
- WhatsApp automation in Pune
The same service in a nearby market, where the constraints differ.
- Website development in Chennai
Hand-written Next.js sites with no theme or page builder, built to rank in Google and be quoted by AI answer engines.
- SEO services in Chennai
Ongoing search work — technical fixes, query-led content, internal linking, structured data — plus the answer-engine work that gets you cited rather than crawled past.
- Software development in Chennai
Customer apps for Android, iOS and web, and the internal web application a business runs on — bookings, payments, inventory, staff, custom CRM and ERP.
- AI chatbot development in Chennai
AI chatbots trained on your own content, and agents that carry out the multi-step work behind the conversation, with an explicit hand-over point to a person.
Building WhatsApp Business API automation for a business in Chennai?
Tell us what you are trying to do and we will come back with a scope and a number. Reminders, confirmations, payment updates, follow-ups and review requests on the WhatsApp Business API, with human takeover at any point.
Or message us on WhatsApp · connect@myfloww.in