For most Indian customers, WhatsApp is not just another channel - it is the channel. They would rather send a WhatsApp message than fill in a form, and they read WhatsApp notifications long before they open email. That is why so many businesses start with the free WhatsApp Business app on a single phone.
Then they grow. Three salespeople need to answer the same number. Order updates need to go out automatically. Leads from the website need to land in the CRM with the chat history attached. At that point, the phone app cannot keep up, and it is time to look at the WhatsApp Business Platform, commonly called the WhatsApp Business API.
This guide explains how it works, what you need, and how to integrate it without getting your number restricted.
App vs platform: which one do you need?
| | WhatsApp Business app | WhatsApp Business Platform (API) |
|---|---|---|
| Who uses it | One person or a small team | Software plus any number of agents |
| Interface | WhatsApp app on phone or desktop | Your CRM, help desk or a provider's dashboard |
| Automation | Quick replies, greeting and away messages | Full automation, chatbots, triggered notifications |
| Integration | None with your systems | Connects to website, CRM, store, ERP |
| Business-initiated messages | Manual | Approved templates, sent programmatically |
| Typical fit | Shops and solo professionals | Growing sales, support and e-commerce teams |
If one person can comfortably handle your WhatsApp chats and you do not need automation, stay with the app. If you need multiple agents, automation or integration, you need the platform.
How the WhatsApp Business Platform works
Meta provides the platform mainly as the Cloud API, hosted by Meta. Your system sends requests to the API to deliver messages, and Meta sends webhooks back to your system for incoming messages and delivery status updates such as sent, delivered and read.
You can connect in two ways:
- Directly with Meta's Cloud API. Your developers integrate with the API themselves. You get maximum control and no middle layer.
- Through a Business Solution Provider (BSP). Providers offer a ready dashboard, shared inbox, broadcast tools and chatbot builders on top of the API, and many offer their own APIs and CRM connectors too.
Neither is "right" for everyone. Direct integration suits businesses with custom software and in-house or agency developers, while a BSP suits teams that want a ready inbox quickly. Many businesses use a BSP dashboard for agents while their CRM integrates through the BSP's or Meta's API.
The rules you must understand first
The platform is built to protect users from spam. Respecting these rules is what keeps your number healthy.
The customer service window
When a customer messages you, a 24-hour customer service window opens. Within that window, you can reply with normal free-form messages. Outside it, you can only start a conversation using an approved message template.
Message templates
Templates are pre-written messages, with placeholders for details like name or order number, that Meta reviews before you can use them. They fall into categories:
- Utility - order confirmations, shipping updates, appointment reminders, payment receipts
- Authentication - one-time passwords and login codes
- Marketing - offers, announcements, re-engagement messages
Meta charges for some message categories, and the charging model has changed over time, so check Meta's current WhatsApp pricing information when you plan volumes. Write templates clearly and match each to the right category; mis-categorised templates may be rejected or re-classified.
Opt-in
You must have the customer's permission to message them on WhatsApp. Collect it clearly - for example, a checkbox on your website form saying "Send me order updates on WhatsApp", or a click-to-chat button the customer taps themselves. Keep a record of when and how each person opted in. This also aligns with the consent principles of India's DPDP Act 2023.
Quality rating and messaging limits
Each phone number has a quality rating based on how recipients react - blocks and reports pull it down. New numbers start with a limit on how many unique customers they can message in a rolling 24-hour period; limits rise as you send good-quality messages and complete business verification. Blasting a purchased list is the fastest way to get restricted.
What you need to get started
- A Meta business portfolio (previously called Business Manager) for your company.
- Business verification with your company documents - recommended, and needed to unlock higher messaging limits.
- A phone number for the account. Typically this should not be in active use on the regular WhatsApp app; if you want to use your existing business number, check Meta's current migration and coexistence options first.
- A display name that clearly relates to your business and follows Meta's naming guidelines.
- A server or provider to receive webhooks and send API requests.
- Approved templates for the notifications you plan to send.
High-value integrations for Indian businesses
Website and lead forms
- When a visitor submits an enquiry, send an instant WhatsApp acknowledgement with your brochure or next steps.
- Create the lead in your CRM and assign it to a salesperson, with the WhatsApp conversation linked.
E-commerce order journey
- Order confirmation after a successful Razorpay or PayU payment
- Shipping update with AWB and tracking link when the courier picks up
- Delivery confirmation and a polite review request
- Cash-on-delivery confirmation messages to reduce fake orders and failed deliveries
Appointments and services
- Booking confirmations and reminders for clinics, salons, coaching classes and service technicians
- Rescheduling with interactive buttons instead of phone tag
Payments and collections
- Payment links and polite reminders for pending invoices
- Receipts once payment is captured, triggered by the gateway's webhook
Support
- A shared inbox where several agents handle one number
- A simple menu-driven bot that answers common questions - timings, location, order status - and hands over to a human for anything else
A sensible integration architecture
For a typical business, the cleanest setup looks like this:
- Your CRM or backend is the source of truth for customers, leads and every order.
- Events trigger messages - a new lead, a paid order, a shipped parcel.
- A small integration service picks the right template, fills in the details and calls the API.
- Webhooks come back with delivery status and customer replies, which are stored against the customer record.
- Agents reply from the CRM or the provider's inbox, with full history visible.
- Logs and alerts flag failed messages, rejected templates and drops in quality rating.
If you are building or upgrading a CRM, plan WhatsApp in from the start - it is much easier than bolting it on later. Our CRM development team often designs both together.
Mistakes we see often
- Sending marketing to people who never opted in. Blocks follow, the quality rating drops and limits shrink.
- Using marketing language in utility templates. Templates get re-classified or rejected.
- No human handover. Bots that trap customers in loops damage trust.
- Ignoring status webhooks. Without them, you do not know which messages failed.
- Storing access tokens in website code. Tokens belong on the server, rotated if exposed.
- Long, unformatted templates. Short, clear messages with one action perform best on a phone screen.
Measuring whether it works
Once the integration is live, review a few simple signals regularly:
- Delivery and read status for each template - low delivery can point to wrong numbers or opt-in problems.
- Quality rating of your number in WhatsApp Manager - act quickly if it drops.
- Reply and conversion - how many people who receive a message reply, book or pay.
- Opt-outs and blocks - a rise usually means messages are too frequent or not relevant.
- Response time - how quickly agents answer incoming chats, both during and outside business hours, and whether the bot hands over smoothly.
Use these signals to refine templates, timing and audiences rather than simply sending more messages.
Key takeaways
- The WhatsApp Business app suits small teams; the platform (API) suits automation, multiple agents and integrations.
- Free-form replies are allowed within the 24-hour customer service window; outside it, use approved templates.
- Opt-in, good templates and a healthy quality rating are what keep your number working.
- Connect WhatsApp to the systems that already hold the truth - your CRM, store and payment gateway.
- Monitor delivery status, failures and quality from day one.
Plan your WhatsApp integration with us
MetaFox Technologies is a Jaipur-based team of 25+ in-house specialists with 6+ years of experience and 1,500+ projects delivered. We connect the WhatsApp Business Platform to websites, CRMs, online stores and payment gateways for businesses across India. Book a free consultation to map your messaging journey, or explore our API integration and automation services. If you want WhatsApp to support campaigns as well, our digital marketing team can help. A written scope and quote follow the call.
