Checklist · WhatsApp Business Platform · India · updated 2 November 2026

The WhatsApp Business API setup checklist for India

In order: pick a number that is not on the WhatsApp app; verify the business in Meta Business Manager with a GST certificate, PAN and address proof whose names match exactly; choose Meta’s Cloud API directly or a Business Solution Provider; register the number and a display name that matches the business; build the opt-in and keep the consent record; write utility templates first and submit them; learn the 24-hour window; expect a starting messaging limit of a few hundred new conversations a day that rises with verification and quality; connect the webhook to the agent with logging; budget per delivered template message (India rates reported by providers at under a rupee for marketing and a fraction of that for utility, plus GST, with replies inside the window free); then run the red-flag, opt-out and off-switch tests before the number goes live. DLT registration is for SMS, not WhatsApp. Business verification is not the blue badge.

Every WhatsApp agent we build starts with the same two weeks of paperwork, and most of the delay is avoidable: a number still registered on the app, a GST certificate with a different spelling of the business name, a marketing template submitted where a utility one would do. This page is the order to do it in, what each step needs, what Meta charges in India and what it does not, and the three confusions that cost Indian businesses the most time. Figures are marked where they come from providers rather than Meta.

Which WhatsApp you need

There are two products with the same name. The WhatsApp Business app is a phone app for one person at a time: free, fine for a shop, no API, no agent. The WhatsApp Business Platform (everyone still says "the API") is what an agent, a shared inbox or a reminder system runs on: a number registered to a Meta business portfolio, messages sent and received through Meta’s Cloud API or a provider built on it, templates approved by Meta for anything you send first, and a per-message fee for those templates.

A phone number can be on one or the other, not both. The commonest first-week delay is the clinic’s existing WhatsApp number: it has to be removed from the app (back up the chats first; they do not come across) before it can be registered on the Platform. The alternative is a new number for the agent and a forwarding line in the app’s away message, which is often the better choice for the first month because the old number keeps working while the new one is tested.

A landline works. The Platform verifies the number by SMS or by a voice call, so a clinic’s advertised landline can become its WhatsApp number, which is usually what patients already have saved.

The checklist, in order

Twelve steps. The first four are paperwork and can run in parallel with writing the rulebook; the last three are the agent itself.

  1. Step 1 · Day 1

    Decide the number and who owns the Meta account

    Choose the number (existing, migrated off the app, or new) and the person whose Meta Business Manager will own the portfolio. It should be the owner or a partner, never the developer or the agency: the portfolio is where the number, the templates, the billing and the verification live, and it is the thing that is hardest to move later.

    Means for you: Owner creates the Business Manager, adds the developer as an admin with a named login, and keeps the two-factor device. One hour.

    Source
  2. Step 2 · Days 1–7

    Business verification with documents whose names match

    Meta verifies the legal entity, not the brand. The documents providers report as accepted in India are the GST registration certificate, the business PAN, the certificate of incorporation or Udyam registration, and an address proof such as a utility bill or bank statement. The legal name, the address and the spelling have to be identical across them and on the Business Manager; the typical rejection is a GST certificate that says "Pvt. Ltd." where the PAN says "Private Limited". Reported turnaround is two to seven working days.

    Means for you: Collect the four documents on day one and check the names against each other before uploading. Unverified portfolios start at the lowest messaging limit, so this step gates volume as well as trust.

    Source
  3. Step 3 · Day 2

    Choose: Meta’s Cloud API directly, or a provider

    The Cloud API is hosted by Meta, costs nothing beyond per-message fees, and gives the developer a raw webhook and send endpoint: the right choice when an agent is the product, because the agent is the inbox. A Business Solution Provider (BSP) wraps the same API in a shared inbox, template manager, broadcast tools and billing in rupees, for a monthly fee: the right choice when humans will also work the number from a screen. Both end at the same Meta number and the same templates; the agent can sit behind either. Meta’s self-hosted On-Premises API has been retired for new setups; anything you read about it is history.

    Means for you: Agent only: Cloud API, with the provider decision deferred. Agent plus a desk that reads and replies: a BSP, with the agent connected through its API or a shared webhook. The table below lists the ones we meet in Indian setups.

    Source
  4. Step 4 · Day 2–3

    Register the number and the display name

    The display name is what patients see and Meta reviews it against the business: it should be the business’s real name or a brand it demonstrably uses, not a generic phrase ("Clinic Bookings"), not a person’s name alone, not a competitor’s. Capitalisation and punctuation have rules too. A rejected display name is a day lost, and a name that does not match the verification documents is the usual reason.

    Means for you: Use the name on the signboard, in the same case. Add the profile fields (address, hours, website, description) the same day; the agent will be asked about them and the profile is the first place a patient checks that the number is real.

    Source
  5. Step 5 · Before any outbound message

    Build the opt-in and keep the record

    Meta’s policy is that a business may only send a template to someone who has opted in to receive messages from it on WhatsApp, with the opt-in obtained through a clear, separate action: a message to the number, a ticked (not pre-ticked) box on a form, a click-to-chat link or QR code, a verbal or written consent at the desk that is recorded. India’s DPDP Act adds the legal layer: the consent has to be specific, informed and withdrawable, and you have to be able to show it. Marketing opt-in is separate from service opt-in; reminders about an appointment the patient booked are not marketing, but a festive offer to the same number is.

    Means for you: One consent line on the intake form and the website, a QR card at the desk, a column in the patient record saying when and how consent was given, and a STOP that works. The wording templates are at the end of this page.

    Source
  6. Step 6 · Days 3–5

    Write the utility templates first and submit them

    Anything the business sends first, or outside the 24-hour window, is a template Meta has approved, in one of three categories: utility (a specific, requested transaction: confirmation, reminder, document request), authentication (one-time codes) and marketing (everything else, including anything with an offer). Utility is far cheaper and approves faster; a template that mixes a reminder with a promotion is classified as marketing, and Meta can reclassify a template after approval if its content drifts. Submit with the variables as numbered placeholders and a sample for each.

    Means for you: Five templates cover a first agent: appointment confirmation, reminder, recall or follow-up, document request, and the opt-in confirmation. The five we use, written to pass as utility where the category allows, are in the template library.

    Source
  7. Step 7 · Design time

    Learn the 24-hour window, because the agent lives in it

    When a customer messages the number, a 24-hour customer service window opens in which the business can send free-form messages, which is what an agent’s replies are. Every new inbound message resets the clock. Outside the window the business can only send approved templates. So an agent’s conversational replies are free and unrestricted while the patient is talking; the reminder it sends the evening before is a template with a fee; and a follow-up a week later is a template that also needs the marketing or utility opt-in to match.

    Means for you: The rulebook’s "may do alone" list should say which messages are in-window replies and which are templates, because the second kind costs money and needs consent of the right category.

    Source
  8. Step 8 · Weeks 1–6

    Expect a messaging limit, and let it grow

    Meta caps how many unique customers a business can start conversations with in a rolling 24 hours. The cap is now set for the whole business portfolio rather than per number, starts in the low hundreds for an unverified business, and rises in steps (providers report 1,000 or 2,000, then 10,000, then 100,000, then unlimited; the exact steps have changed and Meta’s page no longer lists them) as verification completes and the number sends enough good-quality volume. Meta reviews eligibility automatically, reportedly every few hours. Replies inside the window do not count against it.

    Means for you: A clinic sending sixty reminders a day will never notice the cap. A franchise sending ten thousand recall messages in one morning will. Plan the first broadcast as a trickle.

    Source
  9. Step 9 · Ongoing

    Protect the quality rating

    Each number carries a quality rating (green, yellow, red) driven by how recipients react: blocks, reports and whether they reply. A falling rating can pause templates and, at worst, restrict the number. The causes are predictable: marketing to people who did not opt in, templates sent at night, no working opt-out, and messages that read like broadcasts rather than service.

    Means for you: The agent’s guardrails are the quality rating’s guardrails: STOP honoured within the same conversation, no templates between 9 pm and 8 am, nothing promotional from a number patients saved for bookings.

    Source
  10. Step 10 · Build week

    Connect the webhook to the agent, with logging

    Inbound messages arrive at a webhook URL you register, as JSON with the sender, the text or media and a message id; the agent reads them from a queue and sends through the messages endpoint. Delivery and read receipts arrive on the same webhook. The things that go wrong are mundane: a webhook that returns slowly and gets retried, media that has to be fetched by id within a time limit, and a token that expires because it was a temporary one from the developer console rather than a system-user token.

    Means for you: Every inbound message, every agent decision and every outbound send logged with the WhatsApp message id, in a sheet or table the practice manager can read. A permanent system-user token, stored as a secret, with a calendar reminder for its expiry if it has one.

    Source
  11. Step 11 · Budget

    Know what you pay, and what is free

    Meta charges per delivered template message by category and by the recipient’s country; replies inside the 24-hour window are free, and utility templates sent inside an open window are free too. For India, providers reported marketing templates at about ₹0.86 each from January 2026 and utility and authentication at about ₹0.12 each, with volume discounts on utility and authentication only; those figures are from provider rate cards rather than from Meta’s page, which lists the changes but not the rupee amounts, so verify before budgeting. GST applies on top. A BSP adds its own subscription, and some add a markup per message, which is the first thing to ask them.

    Means for you: A clinic sending 60 reminders a day pays Meta in the low hundreds of rupees a month. A coaching institute sending 5,000 marketing messages a month pays in the low thousands. The agent’s conversational replies cost nothing on WhatsApp; the model usage is the cost, and the cost estimator prices that.

    Source
  12. Step 12 · Before go-live

    Run the tests the rulebook asks for

    With a test number: the red-flag set (sixty real-shaped messages, every one escalated), the opt-out (STOP in three phrasings, all honoured and logged), the off switch (traffic goes to the desk), a template with a wrong variable (the send fails loudly, not silently), a media message (a photo of a prescription escalates rather than being read), and a message at 2 am (reply in-window, no template until morning).

    Means for you: An afternoon, with the practice manager watching. The clinic rulebook template has the go-live checklist with these ten lines on it.

    Source

Three confusions that cost Indian businesses the most time

DLT is for SMS, not WhatsApp. TRAI’s distributed-ledger registration (entity, headers, consent templates) governs commercial SMS and voice sent through telecom operators. WhatsApp is not an operator channel; it has its own template approval and its own opt-in rule, run by Meta. A provider that asks for a DLT entity id to send WhatsApp messages is either bundling SMS or confused, and either way it is worth asking which. You will still need DLT for the SMS fallback the agent sends when a number is not on WhatsApp.

Business verification is not the badge. Verification is the document check in Step 2 and it is what raises the messaging limit and shows the business name instead of the bare number. The verified badge beside the name (long called the green tick, and since 2025 folded into Meta Verified for business, where it shows as blue) is a separate thing, granted on notability or bought as a subscription depending on the region and the account, and most small businesses never need it. Do not let a vendor sell verification and the badge as one service.

The agent has to say it is an agent. Meta’s business policy already requires that automated conversations make it clear when a person is not involved and offer a way to reach one; India’s DPDP rules and the direction of the IT rules on synthetically generated content point the same way. The first message of every conversation says it is automated and how to reach the desk; that line is in the rulebook, not in the prompt, so it survives model changes.

Providers seen in Indian setups

All of them sit on the same Meta API and the same per-message fees; the difference is the inbox, the tooling, the markup and who you call when a template is rejected. Prices are described, not quoted, because every one of them changes in a given year; check the pricing page on the day.

ToolGood atWhere it stopsPriceFit
Meta Cloud API, directly No subscription and no markup: Meta’s per-message fees and nothing else. The raw webhook and send endpoint an agent wants, template management in Meta Business Manager, and the whole setup owned by the business’s own portfolio.No inbox for humans and no broadcast tool; whatever the desk uses to read and reply has to be built or bought. Billing is to a card on the Meta account, in USD unless the account is set up for INR.Per delivered template message only; no platform feeAgent-first setups where the agent is the inbox and a developer owns the webhook, which is every agent we build.
Interakt (Haptik) An India-first shared inbox and campaign tool on the Cloud API, with catalogues, click-to-WhatsApp ad hooks, Shopify and payment integrations, and an API for sending from your own systems.Built around marketing and commerce teams; an agent sits beside its automation rather than replacing it, so the two need a clear rule about who answers first.Monthly plans in INR plus Meta’s per-message fees; described on its pricing pageBusinesses that will run broadcasts and a human inbox as well as an agent.
Wati Shared team inbox, no-code chatbot builder, broadcast and CRM-style contact fields, with an API and webhooks for custom flows; widely used by Indian SMBs and agencies.Plans are priced per user and by feature tier, and some tiers add a per-message markup over Meta’s fee, which is the thing to check before comparing.Monthly plans by seats and tier plus Meta’s fees, with a markup on some plans; described on its pricing pageA desk of two to ten people who want an inbox today and an agent behind it later.
AiSensy Low-cost Indian platform aimed at broadcasts, click-to-WhatsApp ads and simple flows, with free-tier style onboarding and INR billing.The product is marketing-led; service and agent work is possible through its API but is not what it is built around.Low monthly plans in INR plus Meta’s fees; described on its pricing pageCoaching institutes and D2C brands whose main use is campaigns, with reminders as a side benefit.
Gupshup One of the original Indian BSPs, with WhatsApp alongside SMS, RCS and voice on one platform, so the SMS fallback and its DLT registration can sit in the same account.Enterprise-shaped: the console and contracts assume volume, and small businesses can find the onboarding heavier than the India-first SMB tools.Usage-based across channels plus Meta’s fees; quoteFranchises and larger practices that need WhatsApp and SMS together at volume.
Twilio The developer-first option: the same API shape as its SMS product, excellent documentation, a sandbox for testing before the number is approved, and SMS fallback in the same account.USD billing and a per-message platform fee on top of Meta’s; no inbox for humans without a separate product.Meta’s fees plus a small per-message Twilio fee, billed in USD; described on its pricing pageTeams whose developers already use Twilio, or who want the sandbox for a quick proof before paperwork completes.

The vocabulary a provider will use

WABA (WhatsApp Business Account)
The account inside a Meta business portfolio that holds the business’s WhatsApp numbers, templates and quality ratings. One portfolio can hold several.
BSP (Business Solution Provider)
A company Meta has approved to onboard businesses onto the Platform and sell tooling on top of it. Using one is optional; the Cloud API is open to any business directly.
Cloud API
Meta’s hosted version of the Platform: Meta runs the servers, you call an HTTPS API and receive a webhook. The self-hosted On-Premises API has been retired for new setups.
Template
A pre-approved message with numbered placeholders, required for anything the business sends first or outside the 24-hour window. Categorised as utility, authentication or marketing, which sets the price.Five templates written to pass
Customer service window
The 24 hours after a customer’s latest message, during which the business can send free-form replies at no charge. An agent’s conversation lives here.
Messaging limit
The number of unique customers a business portfolio may start conversations with in a rolling 24 hours. Rises with verification and quality; replies inside the window do not count.
Quality rating
Green, yellow or red, from how recipients respond to the number’s messages. Blocks and reports lower it; a low rating can pause templates.
Official Business Account / Meta Verified
The badge beside a business name. Separate from business verification; granted on notability or sold as a subscription depending on region. Not needed to run an agent.
Click-to-WhatsApp
A link, QR code or ad that opens a chat with the number, optionally with a pre-filled first message. Each one is an opt-in event, which is why ads that land on WhatsApp are cheap to follow up.Measure the reply time those leads get
Flows
Meta’s in-chat forms: structured screens for a booking, an intake or a survey inside WhatsApp. Useful for the intake step; not a substitute for the agent’s conversation.
System user token
The permanent access token the agent’s backend uses to call the API, issued to a system user in the business portfolio. The temporary token from the developer console expires in a day and is the commonest reason a pilot stops sending at 3 pm on a Tuesday.

Opt-in wording to copy

Three places consent is collected. Fill the brackets, keep a record of which one was used and when; the DPDP notice line is deliberately plain.

Website or intake-form checkbox

Any form that collects a phone number. Unticked by default.

[ ] Send me appointment confirmations, reminders and replies to my messages on WhatsApp at this number. [Business name] will use my number for this and nothing else unless I agree separately. I can reply STOP at any time. See [privacy notice link].

A second, separate box is needed for anything promotional. Do not merge them.

Desk card or QR poster

At reception, on the bill, on the appointment slip.

Message us on WhatsApp: [number] / scan to chat
By messaging this number you agree to receive replies and appointment messages from [Business name] on WhatsApp. Reply STOP at any time. Automated assistant; type HUMAN to reach the desk.

The inbound message itself is the opt-in event for service messages; the card makes the terms visible before it is sent.

The first message the agent sends

Start of every new conversation, and after any STOP is lifted.

Hi, this is [Business name]’s automated booking assistant. I can book, change or remind you about appointments and answer questions about hours, fees and directions. For anything about symptoms or treatment, or to reach a person, type HUMAN at any time. Reply STOP to stop messages from this number.

Keep the disclosure in the first message even when the patient opened the chat from a QR code; it is the line that keeps the quality rating green.

Read Meta’s pages before a provider’s

Everything on this page that is a rule comes from one of these; everything that is a rupee figure comes from providers and is marked so.

  1. 1
    WhatsApp Business Platform pricingMeta

    The per-message model, category definitions, what is free inside the window, and the dated list of rate changes by country. Rate cards are linked from it.

  2. 2
    Messaging limitsMeta

    How the limit is set at portfolio level and raised automatically. The tier numbers quoted by providers are not on this page; treat them as reported.

  3. 3
    Message template guidelinesMeta

    What gets a template rejected or reclassified, with examples per category.

  4. 4
    WhatsApp Business Messaging PolicyMeta

    The opt-in rule, the automation disclosure, prohibited content and the enforcement ladder.

  5. 5
    Business verification in Meta Business ManagerMeta

    The document types Meta accepts and the matching-name rule, straight from the source.

  6. 6
    Cloud API: get startedMeta

    The developer walkthrough from test number to first webhook; the fastest way to see whether the direct route suits your team.

  7. 7
    Digital Personal Data Protection frameworkMeitY, Government of India

    The Act and Rules the consent record has to satisfy. Our regulation tracker lists the dates.

Cite this page: SigmaticAI, "WhatsApp Business API setup checklist for India", appsigmaticai.com/library/whatsapp-business-api-setup-checklist-india, updated 2 November 2026.

Link to it rather than copying the table; the numbers are refreshed here and the sources are one click away.