Ask a business in Kochi, Dubai or Mumbai where its enquiries come from and WhatsApp is usually near the top of the list. Then ask where those conversations are recorded. The answer is often a handful of staff phones. When someone leaves, their chats leave with them, and nobody can say how many enquiries turned into sales.
WhatsApp Business API integration fixes that by connecting WhatsApp to the software you already run: a CRM, a booking system, an order platform or your own app. We are a product engineering team at Infopark in Kochi, and we build these connections into CRMs and business applications for clients in India and the UAE. This guide explains how it works and what to decide first.
The short answer
The WhatsApp Business API, which Meta now calls the WhatsApp Business Platform, lets your software send and receive WhatsApp messages on a business number. It has no screen of its own. You connect it to a shared inbox, a CRM or a custom application, and that software becomes where your team works. Meta charges per delivered message, by category and by the customer's country. Messages your customers send you are free. Business-initiated messages must use templates that Meta approves, and you need the customer's permission to send them.
The Business app and the API are different products
Many businesses start with the free WhatsApp Business app on a phone. It is a good tool for a small team. It has a business profile, quick replies, labels and a catalogue. Its limits appear as the business grows: a few devices per number, no proper connection to other software, and conversations that live on individual phones.
| WhatsApp Business app | WhatsApp Business Platform (API) | |
|---|---|---|
| Where the team works | The app on a phone, plus linked devices. | A shared inbox, CRM or your own software. |
| Number of agents | A small number of devices. | As many as your software supports. |
| Connection to other systems | None in practice. | Built for it: CRM, orders, bookings, payments. |
| Automated messages | Greeting, away and quick replies. | Order updates, reminders, OTPs and bots driven by your data. |
| Cost | Free. | Charged per delivered message, plus any software or provider fees. |
| Conversation history | On the phones. | Stored against the customer record in your system. |
If two people answer every message and nothing needs to flow into another system, the app may be enough. Once several people share the work, or the messages need to update records, the API is the right tool.
What an integration actually does
The value is not WhatsApp itself. It is that WhatsApp stops being a separate island. These are the jobs we see most often.
Leads into the CRM. A new enquiry creates or updates a customer record, tagged with the ad or page it came from, and is assigned to a salesperson.
Shared inbox with history. Any team member can pick up a conversation and see what was said before, including when the original person is on leave.
Transactional updates. Order confirmations, dispatch notices, appointment reminders and payment receipts sent automatically when the record changes.
Sign-in codes. One-time passwords for an app or customer portal delivered on WhatsApp instead of, or as well as, SMS.
Self-service. A customer checks an order status, books a slot or downloads an invoice without waiting for a person.
Hand-off to a person. A bot answers the routine questions and passes anything else to a named staff member with the context attached.
Each of these is a small piece of system integration: an event in one system triggers an action in another. The work is in mapping those events properly, not in sending the message.
How the pieces connect
Meta's Cloud API
Meta hosts the API itself. The older on-premises version, which businesses ran on their own servers, reached its final shutdown in October 2025, so new projects use the Cloud API. Your software sends messages to Meta over HTTPS, and Meta calls your server, through a webhook, whenever a customer replies or a message is delivered or read.
Direct, or through a provider
You can connect to Meta directly, or through a Business Solution Provider. A provider adds a ready-made inbox, campaign tools and support, and usually charges a fee on top of Meta's rates. Connecting directly avoids that fee but means your own software must do everything a provider's dashboard would. For a business with a custom CRM or app, connecting directly is often the cleaner choice. For a business that only needs a shared inbox, a provider is often faster.
Your software in the middle
Whichever route you take, something has to receive the webhooks, match each phone number to a customer, store the conversation, decide who handles it and send the replies. That is the part we build. It sits in your CRM or mobile app back end, so WhatsApp becomes one more channel on the customer record rather than a separate tool.
How Meta charges for WhatsApp messages
Meta bills per delivered message. The price depends on two things: the category of the message and the country code of the person receiving it. Messages from customers to you are not charged. Rates differ widely between countries, so a business messaging customers in India and the UAE pays different rates for the same message. Meta publishes its current rate card on its developer site, and that is the figure to use when you budget.
| Category | What it is for | When it can be sent |
|---|---|---|
| Marketing | Offers, announcements, re-engagement. | Any time, as an approved template, to customers who opted in. |
| Utility | Updates on something the customer did: an order, a booking, a payment. | Any time, as an approved template. |
| Authentication | One-time passwords and sign-in codes. | Any time, as an approved template. |
| Service | Free-form replies to a customer. | Only within 24 hours of the customer's last message. |
The 24-hour window
When a customer messages or calls your business number, a 24-hour customer service window opens, and each new message from them restarts it. Inside the window your team can reply freely. Outside it, you can only send approved templates. This rule shapes how a sales team works: a lead who went quiet two days ago can be contacted only with a template.
What changed on 1 October 2026
Until this autumn, service replies were free and utility templates sent inside the window were free. According to Meta's pricing documentation, from 1 October 2026 each business phone number gets 1,000 free service messages a month, and service messages beyond that are charged. Utility templates sent inside the window are now charged at the normal rate. Meta also asked businesses to add a payment method by the end of September, because service messages could stop being delivered without one.
For a busy support team this is a real cost change. It is also a reason to design flows carefully: one useful message costs less than three short ones.
Billing in rupees for Indian businesses
Meta's documentation says eligible business portfolios in India must have their messaging accounts migrated to Indian rupees by 31 December 2026, and that from 1 January 2027 it will stop delivering messages from eligible accounts that have not moved. If your WhatsApp account was set up in dollars, check its status now with whoever manages it.
Click-to-WhatsApp ads
When a customer starts a chat from a Click to WhatsApp ad on Facebook or Instagram, and your business replies, Meta opens a free entry point window that can last up to seven days, during which most messages to that customer are not charged. For businesses that buy leads through Meta ads, connecting that traffic straight into the CRM is often the first integration worth building.
The rules that shape what you can build
Opt-in. You need the customer's permission before you send business-initiated messages. Record when and how it was given. In India, the DPDP Act adds its own duties around consent and the data you store.
Template approval. Every template is reviewed by Meta, and the category you choose must match the content. A promotional message filed as utility is likely to be rejected or reclassified.
Business verification and display name. Your business is verified in Meta Business Manager, and the name customers see is checked against it.
Messaging limits. A new number can start conversations with only a limited number of customers in a day. The limit rises as you use the number and keep message quality high. Plan a large launch around it.
Quality. Customers can block or report a business. Too many of those lower the number's quality rating and can restrict what it can send.
AI assistants. Since 15 January 2026, Meta's terms bar general-purpose AI chatbots from the Business Platform. A bot that handles support, bookings or orders for your own business is still allowed. Our guide to AI chatbots for business covers what such a bot can sensibly do.
Language matters, in Kerala and in the Gulf
Templates can be written in many languages, and Meta's supported list includes Malayalam, Hindi, Tamil and Arabic, with regional Arabic variants for markets such as the UAE and Qatar. A clinic in Kerala can send appointment reminders in Malayalam and English. A distributor in the UAE can send order updates in Arabic and English. Each language version of a template is its own piece of text, so budget time for writing and approval.
If your inbox or app shows Arabic, it must lay out right to left properly. That is a design and testing task, not a translation task, and it is easy to underestimate.
What to decide before you build
Which number. Use a number your customers already know if you can, and plan the move off the phone app carefully. Keep the account in your company's name, not a staff member's or a supplier's.
Who answers what. Map enquiry types to teams and set rules for assignment, hand-off and escalation before anyone writes code.
Which events trigger messages. List each automated message, the record change that sends it, and its category. This list is also your cost estimate.
Where conversations are stored. Decide which system keeps the history, for how long, and who can see it.
Provider or direct. Compare a provider's monthly fees with the cost of building the inbox features into your own software.
How you will measure it. Response time, enquiries per source and enquiries that became sales are the figures most owners want to see.
If you are still choosing a CRM, this list belongs in that decision. Our comparison of custom and off-the-shelf CRMs covers where WhatsApp support differs between the two.
Mistakes we see
Treating WhatsApp as a broadcast channel. Bulk promotions to people who did not ask for them get the number blocked and reported, and its quality rating falls.
Splitting one message into several. Under per-message billing each one is charged. Put the order number, status and link in a single update.
A bot with no way out. Customers who cannot reach a person stop using the channel. Always offer a hand-off.
Account ownership with the vendor. If the provider or developer owns the Business Manager account, changing supplier becomes difficult.
No plan for the window. Sales teams expect to follow up whenever they like. Build approved follow-up templates before launch, not after the first complaint.
Frequently asked questions
Is the WhatsApp Business API free?
No. Customers messaging you is free, and each number gets a monthly allowance of free service messages, but templates and service messages beyond the allowance are charged per delivery. Provider and software fees are separate.
Can I connect WhatsApp to Zoho, HubSpot or another CRM I already use?
Usually yes, through the CRM's own WhatsApp feature, a provider's connector or a custom integration. A custom build makes sense when you need behaviour the connector does not offer, such as your own assignment rules or links to an order system.
Can I use AI to answer WhatsApp messages?
Yes, for your own business: answering questions about your products, taking bookings, checking orders. Meta's terms no longer allow a general-purpose assistant whose main purpose is open-ended chat.
How long does an integration take?
It depends on what it connects to. Meta's business verification and template approvals add waiting time that sits outside the development work, so start them early.
Can my app send OTPs on WhatsApp?
Yes. Authentication templates exist for this. Many apps offer WhatsApp and SMS together so that a customer without WhatsApp can still sign in.
Conclusion
WhatsApp Business API integration is worth doing when WhatsApp is where your customers already talk to you and the conversations need to reach the rest of the business. Understand the 24-hour window and per-message billing, keep the account in your name, design each automated message on purpose, and treat the connection to your CRM or app as the real project.
If your enquiries are scattered across staff phones, or you want order updates and reminders to go out on WhatsApp from your own system, our team in Kochi can look at how you work today and suggest the smallest useful first step. Tell us what you need and we will start from there.
Human. Digital. Future.
