Guide · WhatsApp

WhatsApp Business API Guide for Indian Businesses

The free WhatsApp Business app handles one phone and one person. When your team grows, the API takes over: multiple agents, automated messages, CRM integration, and conversations that convert. Here is how to set it up properly in India.

By Shreyas Bagal Published 22 August 2026 Updated 22 August 2026 Read ~10 min Topic WhatsApp · Leads

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 works well if you are on the free app. This one picks up where it left off. If your business has outgrown a single phone, if two people are fighting over one device to reply to leads, or if you need to send hundreds of order updates automatically, the WhatsApp Business API is the next step. I have set it up for clinics, D2C brands, and coaching centres across Pune, and the pattern is consistent. The API is not complicated, but it is easy to waste money on a BSP you do not need or build flows nobody uses. Here is the practical version.

When to move from the free app to the API

The WhatsApp Business app is enough for a single person replying from one phone. You get a business profile, catalog, quick replies, labels, greeting messages, and away messages. It works. The limit is scale. The API makes sense when any of these are true:

  • Multiple agents need the same number. Two salespeople, a receptionist, and a manager all replying from one WhatsApp number without stepping on each other.
  • You send more than 50 order updates or reminders a day. Typing each one is not viable.
  • You want WhatsApp connected to your CRM. Leads logged automatically, follow-ups triggered without manual effort.
  • You run click-to-WhatsApp ads. The volume of inbound chats from Meta ads needs a proper queue, not a personal phone buzzing nonstop.

If none of these apply, stay on the free app. The API costs money and adds complexity. Do not let someone upsell you before you actually need it.

Setting up WhatsApp Business API in India

There are two routes in 2026. The first is the Cloud API directly from Meta through the Meta Business Platform. You sign up at business.facebook.com, verify your business, add a phone number, and start building. No third party needed. You handle the webhook integration yourself, which means you need a developer or a tool like n8n or Make to catch incoming messages and send replies.

The second route is through a BSP (Business Solution Provider) like Wati, Interakt, AiSensy, or Gallabox. These give you a dashboard, a chatbot builder, template management, and analytics out of the box. You pay a monthly platform fee on top of WhatsApp's per-conversation charges. For a non-technical team, this is usually the right call.

Step-by-step setup (BSP route)

  1. Pick a BSP. Compare pricing, chatbot features, and CRM integrations. For most Pune small businesses, Interakt or AiSensy at the lower tier is plenty.
  2. Sign up and connect your Meta Business account. The BSP guides you through Facebook Business Verification, which takes 2 to 7 business days.
  3. Add your phone number. Use a new number or port your existing WhatsApp Business app number. If you port, you lose the app's chat history, so export it first.
  4. Set up your business profile: name, description, address, category, website, logo.
  5. Create and submit your first template messages for approval. WhatsApp reviews templates within 24 hours.
  6. Build your first automation flow: greeting, away message, and a basic lead qualification sequence.

The whole process takes about a week, with most of the waiting spent on business verification.

Understanding the 24-hour messaging window

This is the rule that shapes everything on the API. When a customer messages you, a 24-hour service window opens. During that window, you can reply freely with any message. Once the window closes, you can only reach that customer using a pre-approved template message. Templates are how you send appointment reminders, order updates, shipping notifications, and promotional offers outside the service window. Each template-initiated conversation carries a small cost (roughly 0.47 INR for a business-initiated conversation in India as of mid-2026). User-initiated conversations where the customer messages you first are free for the first 1,000 each month.

The practical takeaway: reply fast. If a lead messages you at 2 PM and nobody replies until the next morning, the window is closed. Now you need an approved template just to follow up, which costs money and feels less natural. Speed is not just good service. It is cheaper.

Template messages that get approved

WhatsApp reviews every template before you can use it. Templates that read like spam get rejected. Templates that sound like a helpful human text get approved quickly. A few rules I follow:

  • Keep it short. Two to three sentences. Nobody reads a paragraph from a business number.
  • Be specific. "Your appointment with Dr. Patil is confirmed for Tuesday at 4 PM" beats "Reminder: you have an upcoming appointment."
  • Use variables. Template variables like {{1}} for the customer's name and {{2}} for the date make messages personal without being creepy.
  • Match the category. WhatsApp categorises templates as utility (order updates, reminders), authentication (OTPs), or marketing (offers, re-engagement). Pick the right one. Mislabelling a promo as utility gets it rejected.
  • Include a clear opt-out. "Reply STOP to unsubscribe" at the end of marketing templates.

I have seen businesses submit five versions of the same template before it passes. Write it like a text you would send a friend about their order, not a billboard. The approval comes faster.

WhatsApp catalog on the API

The catalog feature works on the API the same way it does on the free app, but with more control. You manage your product catalog through Meta Commerce Manager, and it syncs to your WhatsApp Business number. Customers browse products inside the chat, add items to a cart, and send the order as a message. For D2C brands and retail shops, this turns WhatsApp into a lightweight storefront without building an app.

A few things I set up for every catalog:

  • Real photos, not stock images. A phone photo of the actual product converts better than a polished render.
  • Prices visible. "DM for price" kills momentum. Put the number there.
  • Short, clear descriptions. "Handmade leather wallet, brown, fits 6 cards" is enough.
  • Categories if you have more than 10 items. Group them so browsing is fast.

Automated messages and chatbot flows

Automation on the API is where the real leverage sits. At minimum, set up these three:

  1. Greeting flow. When someone messages for the first time, send a welcome message with two or three quick-reply buttons: "View catalog," "Book appointment," "Talk to a person." This routes the conversation without a human touching it.
  2. Away message. Outside business hours, acknowledge the message and set expectations: "We're available 10 AM to 7 PM. We will reply first thing tomorrow."
  3. Lead qualification sequence. After the greeting, ask one or two qualifying questions: "Which service are you interested in?" and "What is your preferred date?" Collect the answers, tag the lead, and route to the right person.

Beyond basics, I build flows using n8n to connect WhatsApp to Google Sheets, CRMs, and calendars. A new lead comes in, the bot qualifies them, logs the data in a sheet, creates a follow-up task, and notifies the sales team on a group. The human steps in only when the conversation needs judgement. This is the kind of automation that pays for the API cost within the first month.

Broadcast lists and bulk messaging

On the API, broadcasting works through template messages sent to a list of opted-in contacts. Unlike the free app's broadcast list (which only reaches people who have saved your number), API broadcasts reach anyone who has opted in, regardless of whether they saved you. That is a significant difference for reach.

The rules still apply. Only message people who consented. Segment your lists by interest, purchase history, or location. A Pune gym sending a "New year offer" to its entire list of 5,000 contacts gets lower engagement than sending "Morning batch slots open" to the 800 people who enquired about morning timings. Relevance protects your sender quality rating, and your quality rating determines how many messages WhatsApp lets you send per day.

CRM integration: connecting WhatsApp to your sales pipeline

This is where the API becomes a serious lead generation tool instead of just a chat app. When WhatsApp connects to your CRM, every conversation creates or updates a contact record. You see the full history: what they asked, what they bought, when they last messaged. Your sales funnel stops having a gap between "lead messaged on WhatsApp" and "we somehow lost track."

Common integrations I set up for clients:

  • Google Sheets + n8n. The simplest version. Every new WhatsApp lead gets a row with name, phone, enquiry, timestamp, and status. Good for businesses with under 50 leads a month.
  • HubSpot or Zoho CRM. Leads flow in automatically, get assigned to a salesperson, and trigger follow-up sequences. For businesses running paid ads with higher volume.
  • Google Calendar. When a lead books an appointment through WhatsApp, a calendar event is created for the relevant team member. Clinics and salons love this.

The key is not the tool. It is ensuring that no lead falls through the cracks because someone forgot to check WhatsApp. Lead tracking should be automatic, not a discipline exercise.

Click-to-WhatsApp ads: turning Meta Ads into conversations

Click-to-WhatsApp (CTWA) ads are the highest-converting lead generation format I run for local businesses. The ad appears on Instagram or Facebook. The user taps it and lands directly in a WhatsApp chat with a pre-filled message. No form, no landing page, no friction. The conversation starts immediately.

Why they work so well in India: people trust WhatsApp. Filling a form on an unknown website feels risky. Sending a WhatsApp message feels normal. I have run CTWA campaigns for a Pune dental clinic where cost per qualified lead was 40% lower than the same budget on lead form ads. The leads were also warmer because they had already engaged in a real conversation.

Setup tips from campaigns I have run:

  • Use the Messages objective in Meta Ads Manager, not traffic or engagement.
  • Set the targeting to a 10 to 15 km radius around your location for local businesses.
  • Write a clear pre-filled message: "Hi, I saw your ad about [service]. I would like to know more." This gives your team context instantly.
  • Have the greeting flow ready on WhatsApp so the lead gets an immediate response, even after hours.
  • Track CTWA leads separately in your CRM to measure cost per conversation and cost per conversion.

Lead qualification via WhatsApp

Not every WhatsApp message is a serious lead. The API lets you qualify automatically. A simple flow I use for a Pune real-estate client goes like this:

  1. Lead sends a message (from a CTWA ad or website button).
  2. Bot replies: "Thanks for reaching out. Are you looking for a 1 BHK, 2 BHK, or 3 BHK?"
  3. Lead picks an option (quick-reply buttons).
  4. Bot asks: "What is your budget range?" with three options.
  5. Bot confirms: "Great, a site visit can be arranged. Would you prefer weekday or weekend?"
  6. Lead's answers are logged in Google Sheets. A notification goes to the sales team with the qualified details.

Three questions, under 30 seconds, and the sales team gets a lead with budget, preference, and availability instead of just a phone number. This is the same qualification logic you would use in a sales funnel, just happening inside a chat.

Measuring WhatsApp API performance

The metrics that matter:

  • Message delivery rate. If messages are not landing, your number quality is flagged or your contact list is stale.
  • Reply rate. The real signal. If people read but do not reply, your templates or opening messages need work.
  • Cost per conversation. Track this monthly. Compare business-initiated vs user-initiated costs.
  • Lead-to-conversion rate. How many WhatsApp conversations turn into bookings, orders, or payments? This is the number that justifies the spend.
  • First response time. For leads from CTWA ads, the gap between when the lead messages and when a human (or bot) replies. Under 5 minutes is good. Under 1 minute is where conversion rates jump.

Most BSP dashboards show delivery and read rates. For conversion tracking, you need the CRM integration so you can follow a lead from first message to closed sale.

Common mistakes I see businesses make

After setting up WhatsApp API for over a dozen clients, the same problems keep appearing:

  • Over-automating. A seven-step chatbot that asks for name, email, phone, city, budget, timeline, and preferred colour before connecting to a human. Nobody finishes it. Keep qualification to two or three questions.
  • Ignoring the quality rating. WhatsApp assigns a quality rating to your number based on user reports and blocks. If it drops to red, your messaging limits shrink. Monitor it weekly in the Meta Business Manager.
  • Using one template for everything. A "Happy Diwali" promo and an appointment reminder need different templates. Sending marketing content through a utility template gets it rejected or reported.
  • No follow-up system. Leads come in, someone replies once, and the thread dies. Without a CRM logging conversations and triggering follow-ups, the API is just an expensive chat app.

Frequently asked questions

How much does WhatsApp Business API cost in India?

WhatsApp charges per conversation, not per message. In India, a business-initiated conversation costs roughly 0.47 INR and a user-initiated service conversation is free for the first 1,000 each month. On top of that, your BSP (Business Solution Provider) charges a platform fee, typically 500 to 5,000 INR per month depending on volume and features. For most small businesses doing under 2,000 conversations a month, total cost stays under 3,000 INR monthly.

Can I use WhatsApp Business API without a BSP?

Yes. Meta now offers the Cloud API directly through the Meta Business Platform, so you can set it up yourself without a third-party BSP. The trade-off is that you handle the technical integration, webhook setup, and template management on your own. If you are comfortable with APIs or have a developer, the direct route saves the BSP's monthly fee. If you want a ready-made dashboard with chatbot builders and analytics, a BSP like Wati, Interakt, or AiSensy is simpler.

What is the difference between WhatsApp Business app and WhatsApp Business API?

The WhatsApp Business app is a free download for one phone. It gives you a business profile, catalog, quick replies, and basic automation. The API has no chat screen of its own. It connects through a CRM, helpdesk, or chatbot platform, allowing multiple agents on one number, thousands of automated messages, and deep integrations. Move to the API when your team outgrows one phone or you need to send order updates and reminders at scale.

Related guides

Work with Shreyas → ← Back to blog