WhatsApp Business API Guide for Indian Businesses

I wrote a broader piece on WhatsApp marketing for Indian businesses earlier this year covering the basics: profiles, catalogs, broadcast lists, opt-in rules. That guide is where to start if you are still deciding whether WhatsApp fits your funnel at all. This one picks up exactly where it left off. It is the technical and setup guide: the actual mechanics of moving from the free app to the Business API, what access looks like through Meta, what a conversation actually costs, which integration path fits a small Pune business versus a larger operation, and the mistakes that get a number restricted right when you need it most. I have set this up for clinics, D2C brands and coaching centres across Pune, and the pattern repeats regardless of industry: the API itself is not complicated, but it is easy to pay for a BSP you do not need or build a chatbot flow nobody finishes. Here is the version I would hand a client on day one.

WhatsApp Business app vs Business API: who actually needs which

The free WhatsApp Business app covers a single person replying from a single phone. It gives you a business profile, a catalog, quick replies, labels, and basic greeting and away message automation. For a solo founder, a boutique clinic, or a small shop where one person genuinely handles every chat, it is enough, and I tell people this directly instead of letting anyone upsell them onto the API before they need it.

The WhatsApp Business API, officially the WhatsApp Business Platform now, has no chat screen of its own. It connects through a CRM, a helpdesk, or a chatbot platform, and it is built for scale rather than for one person's phone. Move to it when any of these are genuinely true for your business: multiple agents need to share one number without stepping on each other's replies; you are sending more than roughly 50 order updates, reminders, or confirmations a day, which stops being typeable by hand; you want WhatsApp conversations logged automatically into a CRM instead of living only in someone's chat history; or you are running click-to-WhatsApp ads at a volume where a personal phone buzzing nonstop is no longer a workable queue.

If none of those four apply yet, stay on the free app. The API adds a monthly cost and real technical surface area, webhooks, template management, a BSP relationship or a direct Cloud API integration, and none of that is worth taking on before your actual message volume needs it. I have seen businesses migrate to the API on a salesperson's suggestion, then use maybe 10 percent of what they are paying for. Wait for the four signals above, not for someone else's sales pitch.

How access actually works: verification, BSP vs Cloud API, and phone number rules

Every path onto the WhatsApp Business API starts with Meta Business verification, done through Meta Business Manager. You submit your business name, address, and a supporting document, a GST certificate, a business PAN, or incorporation paperwork, and Meta checks that it matches what you have entered. In my experience this takes 2 to 7 business days for an Indian business when the documents match cleanly, and considerably longer when there is a mismatch between your registered name and what you type into the form. Start this step first, before you commit to a launch date, because it is the one part of the process you cannot speed up by paying more.

From there, you choose between two access routes. Going direct through the Cloud API means Meta hosts the messaging infrastructure and you, or your developer, build the integration yourself using a tool like n8n, Make, or custom code to catch incoming messages and send replies through webhooks. There is no monthly platform fee beyond WhatsApp's own conversation charges, but you own the technical build and its maintenance. Going through a BSP, a Business Solution Provider, like Wati, Interakt, AiSensy, or Gallabox, gets you a dashboard, a chatbot builder, template management, and analytics without writing integration code, in exchange for a recurring monthly fee on top of Meta's own charges. For a non-technical small business, the BSP route is usually the right call. For a business with an in-house developer or an existing n8n workflow, the direct route saves the recurring fee.

Phone number rules trip people up more than anything else in this step. A number already active on the free WhatsApp Business app can move to the API, but you lose its local chat history in the process, so export anything you want to keep before you start the migration. A number must be able to receive an SMS or a voice call to complete verification, which matters if you are trying to register a landline, since those can only verify by voice call, not SMS. And a number tied to a personal or existing WhatsApp Business app account has to be properly released from that app before the same number verifies cleanly on the API side, attempting to run both at once on the same number is a common setup failure I see people hit in their first week.

What a WhatsApp API conversation actually costs

WhatsApp prices API messaging by conversation category rather than one flat rate, and every conversation you send or receive outside the free app falls into one of four buckets. Marketing conversations cover promotional templates, offers, and re-engagement messages, and Meta prices these the highest of the four because they are the most commercially valuable to the business sending them. Utility conversations cover order updates, appointment reminders, and shipping notifications, priced lower than marketing since they are transactional rather than promotional. Authentication conversations cover OTPs and login verification codes, usually the cheapest paid category. Service conversations are the replies you send within the 24-hour window after a customer messages you first, and these are typically free or bundled, since the customer initiated contact.

I am deliberately not printing an exact rupee figure for each category here, and that is not an oversight. Meta has changed its WhatsApp pricing model more than once in the past two years, moving between conversation-based and per-message pricing in different rollouts, and the actual numbers shift by category and by quarter. Any specific figure written today could be wrong by the time you read this. What stays reliably true is the ranking: marketing costs more than utility, which costs more than authentication, and service conversations are the cheapest or free. Before you commit to a BSP plan or budget a monthly WhatsApp spend, check Meta's current pricing page directly through Meta Business Manager or your BSP's live rate card, not a number from an old blog post, including possibly this one a year from now.

The practical lesson that does not change with the rate card: reply fast. If a lead messages you and nobody responds until the next morning, the free service window has closed, and reaching them again now costs a paid template message instead of a free reply. Speed is not just good service here, it is the cheaper option every time.

Template messages that get approved

WhatsApp reviews every template before you can send it, typically within 24 hours, and the rejection pattern is consistent: templates that read like spam get rejected, templates that read like a specific, helpful text from a real person get approved. A few rules I follow on every template I write for a client:

• Keep it to two or three sentences. Nobody reads a paragraph from a business number, and neither does Meta's reviewer look favourably on one.
• Be specific, not generic. "Your appointment with Dr. Patil is confirmed for Tuesday at 4 PM" clears review faster than "Reminder: you have an upcoming appointment."
• Use variables correctly. Template placeholders like a customer's name or a date make a message personal without sounding scripted, but every variable needs a realistic sample value submitted with the template.
• Match the category honestly. Utility, authentication, or marketing, pick the one that actually describes the message. Labelling a promotional offer as utility to dodge marketing review is the single fastest way to get a template rejected or your account flagged.
• Include a clear opt-out on marketing templates. "Reply STOP to unsubscribe" at the end protects your quality rating as much as it protects the recipient.

I have seen a client submit five versions of the same template before one passed, usually because the first few read like an advertisement rather than a text. Write it the way you would message a friend about their own order, and approval comes faster and holds up better over time.

Opt-in rules and the basics of DPDP compliance

Consent on WhatsApp is not just a platform rule Meta enforces, it now sits alongside India's Digital Personal Data Protection Act, 2023 (DPDP Act), which governs how any Indian business collects and uses a person's phone number and the data attached to a conversation with them. I am not a lawyer and this is not legal advice, but the practical basics are worth building into your WhatsApp setup from day one rather than retrofitting later.

Consent under DPDP needs to be informed and specific, not buried in fine print. When someone opts in through a website chat button, a click-to-WhatsApp ad, or a QR code at your counter, that action is the consent itself, but you still need to be clear about what they are signing up for: order updates, appointment reminders, occasional offers, and how to stop. Keep a basic record of when and how each contact opted in, since being able to show that a number consented, rather than was bought or scraped, is your actual protection if a complaint ever comes in. Honour opt-outs immediately and completely: if someone replies "stop" or asks to be removed, that request covers the DPDP right to withdraw consent, not just a WhatsApp policy nicety, and ignoring it is both a platform risk and a compliance risk.

Do not share a customer's WhatsApp number or conversation data with a third party, another vendor, a marketing partner, a data broker, without a separate, specific consent for that sharing. A BSP handling your messages on your behalf is generally fine, since they are processing data to deliver the service you asked for, but selling or handing off your contact list to an unrelated business is a different matter entirely and not something to risk without proper legal advice specific to your situation. For most small businesses, the practical checklist is short: only message people who opted in, keep a simple record of that opt-in, honour every opt-out immediately, and never hand your contact list to anyone outside the tools directly running your messaging.

Integration options compared: n8n, Zapier, and Indian BSPs

Once your number is verified, you need something to actually catch and route the messages, and the honest answer is that no single option is right for every business. Here is how I compare the main three with clients, without pretending one is universally best.

Option	Pricing shape	Lock-in and notes
Indian BSPs (Interakt, Wati, AiSensy)	Monthly platform fee, roughly a few hundred to a few thousand rupees depending on tier, on top of Meta's own conversation charges.	Fastest to launch, visual chatbot builders, no code needed. Switching BSPs later means rebuilding your flows on the new dashboard, so there is real lock-in at the workflow level even though the number itself can port.
n8n	Free if self-hosted; a modest monthly fee on their cloud plan. You still pay Meta's conversation charges separately.	Full control over logic, connects to almost any CRM, sheet, or calendar. Needs someone comfortable building and maintaining flows. Lowest platform lock-in of the three, since workflows are portable and the tool is open source.
Zapier	Free tier is limited; paid tiers scale with the number of tasks run monthly and get expensive fast at real WhatsApp volume.	Easiest no-code option if you already use Zapier for other tools. Fewer WhatsApp-specific building blocks than n8n or a dedicated BSP, and cost climbs quickly once message volume grows.

My rule of thumb: a business that wants a chatbot running this week, with no developer involved, goes to a BSP first. A business that already has some automation in place, or expects to connect WhatsApp to several other tools over time, gets more long-term value from learning n8n, since the flows built there are not locked to a single vendor's dashboard. Zapier earns its place only when a business is already deep in the Zapier ecosystem for other tools and the WhatsApp piece is small enough that the per-task pricing does not bite yet. I build a fair amount of the n8n route myself, connecting WhatsApp to Google Sheets, CRMs, and calendars, because it is the option that keeps working the same way regardless of which BSP pricing changes next quarter.

Setting up WhatsApp Business API in 7 steps

This is the order I actually run through with a new client, regardless of whether they end up on a BSP or the direct Cloud API.

Step 1: Decide Cloud API direct or a BSP

Match the decision to your technical resources, not to whichever option a salesperson pitched you first. No developer or n8n experience in-house points to a BSP. An existing developer or automation workflow points to the direct Cloud API and its lower ongoing cost.

Step 2: Complete Meta Business verification

Submit your business documents through Meta Business Manager, a GST certificate, business PAN, or incorporation paperwork, matching exactly what you enter in the form. Start this first, since it is the step most likely to take longer than expected.

Step 3: Add and verify your phone number

Use a new number or migrate your existing WhatsApp Business app number, exporting any chat history you want to keep first. Verify by SMS, or by voice call if you are registering a landline.

Step 4: Build your business profile and catalog

Fill in your name, category, description, address, hours, and logo, then add a catalog entry for every product or service with a real photo and a visible price rather than "DM for price".

Step 5: Submit your first templates for approval

Draft your greeting message, a confirmation or reminder template, and any marketing template you need at launch. Submit all of them early, since review takes up to 24 hours and a rejected first draft needs a resubmission.

Step 6: Connect your integration

Set up your BSP dashboard, or build your first n8n or custom webhook flow, connecting incoming messages to wherever your team actually works: a CRM, a shared inbox, or a Google Sheet.

Step 7: Test, launch, and watch your quality rating

Send test messages to your own number first, then launch to a small warm segment before your full contact list. Check your quality rating in Meta Business Manager weekly for the first month, since that number, not your ad budget, decides how many people you can message next.

Mistakes that get numbers restricted

After setting up the API for more than a dozen clients, the same handful of mistakes keep showing up, and each one is avoidable once you know to watch for it.

• Buying or scraping a contact list. Messaging people who never opted in is the fastest way to get a brand-new number restricted, often within the first week.
• Ignoring opt-outs. One ignored "stop" reply is frequently the exact report that tips a borderline number into restriction.
• Mislabelling a marketing template as utility. This gets the individual template rejected at best, and the whole account flagged at worst, since Meta treats it as an attempt to dodge review.
• Over-automating the greeting flow. A seven-question chatbot before a customer reaches a human loses most people by question three. Keep automated qualification to two or three questions.
• Sudden high volume from a new number. Blasting a full contact list on day one, even a genuinely opted-in one, reads as spam to WhatsApp's own systems. Ramp volume up over the first couple of weeks instead.
• No follow-up system behind the number. Leads arrive, someone replies once, and the thread goes cold with no CRM logging the conversation or triggering a follow-up. At that point the API is an expensive chat app, not a lead generation tool. My guide on tracking marketing leads covers the follow-up discipline that actually closes this gap.

Restraint protects your number's quality rating far more than message frequency ever helps it. WhatsApp watches the ratio of people who block or report you against how many you message, and that ratio decides your sending limits next week, not your budget or your follower count.

Frequently asked questions

Do I need a developer to set up WhatsApp Business API?

Not if you go through a BSP like Interakt, Wati, or AiSensy, since their dashboards handle the technical integration for you and you configure everything through a normal web interface. You need a developer, or comfort with a tool like n8n, only if you choose the direct Cloud API route without a BSP, because then you are responsible for the webhook setup, message handling, and template management yourself. For most small businesses in India, the BSP route avoids needing custom development at all.

Can I keep my existing WhatsApp number when I move to the API?

Yes, but it needs a proper migration. If the number is currently active on the free WhatsApp Business app, export any chat history you want to keep first, since moving to the API removes that history from the app. The number then gets verified again through Meta Business Manager as part of the WhatsApp Business Account setup. Most BSPs walk you through this migration step by step, and it typically completes within a few hours once your business verification is already done.

How long does WhatsApp Business verification take in India?

Meta Business verification typically takes 2 to 7 business days, though it can run longer if your business documents do not clearly match your registered business name. Keep your GST certificate, business PAN, or incorporation documents ready and matching exactly what you enter into Meta Business Manager, since mismatches are the most common reason verification stalls. Submit this step early, before you need the number live, so a slow review does not block your launch date.

What happens if my WhatsApp quality rating drops?

A dropping quality rating, shown as yellow or red in Meta Business Manager, means WhatsApp has detected enough blocks or reports on your number to restrict your messaging limits. At yellow, you can usually still send at your current tier but should reduce volume and review recent template content immediately. At red, WhatsApp caps how many new, unique customers you can message in a rolling 24-hour period, which can genuinely stall a business that depends on the number for daily orders. Recovery means pausing broad broadcasts, messaging only engaged and recently active contacts, and letting the rating rebuild over one to two weeks.

Is n8n or a BSP dashboard better for WhatsApp automation?

It depends on how much technical control you want against how fast you need to launch. A BSP dashboard, Wati, Interakt, or AiSensy, gets a chatbot and template flow running within days through a visual builder and no code, at the cost of a recurring monthly fee and some flexibility. n8n gives full control over the logic, connects to almost any CRM, sheet, or calendar, and avoids paying a BSP purely for chatbot features, but it needs someone comfortable building flows and maintaining the webhook connection. Many of my clients start on a BSP for speed and move logic into n8n later, once their automation needs outgrow the dashboard's built-in flows.

Related guides

• WhatsApp Broadcast vs Group vs Community vs Channel
• Click-to-WhatsApp Ads: Setup, Cost and Lead Quality in India
• WhatsApp marketing for Indian businesses: the broader playbook, opt-in channels, broadcast strategy, and message types that get replies.
• Facebook lead ads guide: how a native Meta lead form compares with click-to-WhatsApp for cost per lead.
• How to track marketing leads: the CRM and tracking setup that makes WhatsApp leads countable.
• Email list building for small business: pairing WhatsApp opt-in with an email channel instead of relying on one alone.
• What is a lead magnet?: giving people a reason to opt in before you ever message them.
• How small businesses get clients online: where WhatsApp fits in the wider acquisition picture.
• Email automation for small business: the same automation thinking applied to a second channel.
• Facebook Pixel guide: tracking the ad spend that feeds your click-to-WhatsApp campaigns.