Most businesses we meet have already tried to build a “digital front door.” A customer portal. An app. A chatbot on the website that nobody scrolls down to. The pattern is familiar: a few months of effort, a launch email, and then usage that quietly settles at a fraction of what the business case assumed.
The problem was never the software. It was the ask. You were asking a customer to download something, remember a password, and learn a new interface — for a task that takes eleven seconds. Meanwhile the app they actually keep open all day is WhatsApp.
That’s the thinking behind our newest service: WhatsApp Business Integration. Not a chatbot bolted onto a marketing number, but your actual business data — orders, stock, dues, appointments, service history — made answerable inside the one app your customers never uninstall.
The mechanic most people miss: the 24-hour service window
Here is the detail that changes the economics, and it’s worth understanding properly because a lot of vendors gloss over it.
WhatsApp charges businesses for conversations, not for individual messages, and it treats the two directions very differently. When you start a conversation — a promotion, a reminder, an OTP — you must use a pre-approved template and you pay for it, at a rate that varies by country and message category. But when the customer messages you first, a 24-hour customer service window opens, and inside that window you can reply freely, as many times as the conversation needs, without per-message charges.
So a customer sending a single “Hi” is not a trivial event. It is the cheapest, highest-intent support session your business will ever get. One tap, and you have a full day to resolve whatever they came for at effectively no messaging cost. Put a “Chat with us” link on your website, your invoices, your packaging, your Google Business profile — and you’ve turned an expensive outbound channel into an inbound one.
What this means in practice
- Customer-initiated chats: free replies for 24 hours — the workhorse of support, order status, bookings and internal lookups.
- Business-initiated messages: billed per conversation, template-approved — worth using deliberately, for reminders and confirmations that genuinely earn their cost.
- Design consequence: build for pull, not push. Make it effortless for customers to start the chat, and most of your volume lands in the free lane.
One caveat we always state plainly: WhatsApp revises its pricing and category rules periodically, so treat any number you read online — including ours — as a starting point to verify, not gospel. The structural advantage of the customer-initiated window has held steady, and that’s what the design should lean on.
Tapping, not typing
The second design decision matters as much as the pricing one. Most WhatsApp bots fail because they open with a blinking cursor and an implicit instruction: guess what I understand. Customers type a paragraph, get a “Sorry, I didn’t catch that,” and never come back.
We build flows the other way round. Every step offers a small set of clear choices, so the customer is selecting rather than composing. It sounds less impressive than free-form AI. It performs dramatically better, for three unglamorous reasons: there’s nothing to misunderstand, the path is auditable, and it works for a customer typing with one thumb on a bus.
Language understanding still has a role — recognising intent when someone does type freely, pulling an order number out of a sentence, handling “where is my stuff” alongside “track order.” But it sits behind the flow as a safety net, not in front of it as the interface.
Connected to your data, or it’s just a brochure
An automation that can only recite your FAQ page saves nobody any time. The value appears the moment the chat can answer questions only your systems know: Is size 9 in stock at the Prahlad Nagar store? What’s my outstanding balance? Has the shipment cleared? When is my policy renewal?
That means integration work, and it’s usually less dramatic than people fear. In our projects the connected sources are almost always things the business already has:
Typical sources we connect
- SQL databases and ERP tables — orders, inventory, ledgers, dispatch status
- Spreadsheets that quietly run a department — price lists, schedules, allocations
- Document sets — catalogues, policy PDFs, SOPs, product specs
- CRMs and ticketing tools, so a chat becomes a real record rather than a dead end
- Internal applications your staff already use — surfaced in chat so nobody learns a new screen
Where documents are involved, we ground answers in retrieval rather than letting a model improvise — the same discipline we described in our piece on production RAG. If the source doesn’t support the answer, the flow says so and offers a human instead of inventing something confident and wrong.
The internal use case nobody asks for and everybody loves
Customer-facing automation is the obvious pitch. The surprise, repeatedly, is what happens when you point the same channel inward.
Field staff don’t want a VPN and a dashboard. A technician standing in a warehouse wants to know whether part number 4482 is in stock, and a sales rep in a client’s lobby wants last quarter’s numbers for that account. Both already have WhatsApp open. Give them a role-restricted chat that reads from the same systems and you’ve delivered mobile access to internal data without building a mobile app — with permissions enforced server-side, so people see only what their role allows.
What it looks like across sectors
The flows differ, the pattern doesn’t: a high-frequency question, a system that already knows the answer, and a customer who’d rather not call.
Retail and e-commerce — order tracking, returns, size and stock checks, catalogue browsing, abandoned-cart nudges. Healthcare and clinics — appointment booking and rescheduling, prep instructions, report-ready notifications. Real estate — inventory by budget and locality, site-visit scheduling, document checklists, payment milestones. Manufacturing and distribution — dealer stock queries, order placement, dispatch status, price lists. Education — admission enquiries, fee status, timetables, results. Financial services — balances and statements, KYC status, renewal reminders, EMI schedules.
In each case the win isn’t novelty. It’s deflection: a large share of repetitive contacts resolved without a human, so your team spends its day on the conversations that actually need judgement.
Where these projects go wrong
We’d rather set expectations honestly than sell a frictionless story.
Automating everything. There must be an obvious, one-tap path to a human, and it must work during business hours. Trapping a frustrated customer in a menu costs more goodwill than the automation saves.
Treating the free window as a marketing loophole. Blast promotional messages and users block or report you; quality ratings drop and messaging limits follow. The channel rewards restraint.
Skipping the handover. If a chat escalates, the agent needs the full transcript and the customer’s record already on screen. Anything less and the customer repeats themselves — the exact experience they were escaping.
Ignoring consent and data rules. Opt-in has to be real and revocable, retention deliberate, and personal data handled to the same standard as the rest of your stack. Under India’s DPDP Act and comparable regimes elsewhere, “it’s just WhatsApp” is not a defence.
Launching with no measurement. Instrument it from day one: containment rate, median time to answer, drop-off point per flow, escalation reasons, conversations per resolved query. Without those you can’t tell a successful flow from a popular one.
How we roll it out
A first release doesn’t need to cover everything. It needs to cover the two or three journeys that generate the most repetitive contact.
Practically: we start from your contact logs to find what people actually ask; set up the WhatsApp Business Platform account and business verification; design the selection-driven flows and get templates approved; connect the data sources those flows depend on; then pilot with a slice of traffic before opening the tap. Most focused first releases go live in three to six weeks. Broader programmes — many flows, several systems, multi-agent routing — take longer, and we’d rather phase them than pretend otherwise.
Common questions
Is WhatsApp Business messaging really free?
Replies inside the 24-hour window that opens when a customer messages you first aren’t charged per message. Business-initiated conversations using approved templates are billed, with rates varying by country and category. Design for inbound and most of your volume sits in the free lane.
Do we need the API, or is the free WhatsApp Business app enough?
The free app is fine for one person replying by hand. Automation, database and CRM connections, multiple agents on one number, and real reporting all require the WhatsApp Business Platform with a verified account.
Can it answer from our own systems?
That’s the point of the service. SQL, spreadsheets, documents, CRMs and internal apps all connect, so answers reflect live business data rather than a static script.
What about our existing website chat or CRM?
They stay. WhatsApp becomes another front end onto the same systems, with conversations logged where your team already works.
The short version
You probably don’t need another app. You need the systems you already own to be answerable in the place your customers already are — with the conversation starting on their side, where it’s free, immediate, and high intent.
One “Hi” is a lower barrier than any download, login, or IVR menu you will ever build. The work is making sure what comes back is genuinely useful.
Radiant Code & Connect designs and ships WhatsApp Business integrations — selection-driven flows, live data connections, internal access for staff, and the compliance and measurement layer around them. Try the interactive demo or talk to us about your use case.