Setting up the WhatsApp Business API in India typically takes 1 to 3 working days when your GST or other business documents and a dedicated phone number are ready, and needs no DLT registration. After setup Meta charges per delivered message, ₹0.8631 for marketing and ₹0.115 for utility or authentication in India, with the first 1,000 service replies per number each month free; your provider's fee comes on top (₹0.10 per message on RichAutomate Client Pay, ₹0 setup).
Disclosure: this guide is published by RichAutomate, a WhatsApp Business API platform; the RichAutomate steps and prices mentioned are our own, and third-party prices were checked on their public pages on 30 October 2026.
The official path runs through Meta Business Manager verification, document upload, phone number registration, display name review, embedded signup via a BSP, template submission, and finally the first broadcast. Crucially, WhatsApp Business API requires no DLT registration in India — unlike SMS — which removes the longest delay vector in any Indian messaging rollout.
Direct answer — how to set up WhatsApp Business API in India
Verify your Meta Business Manager, upload your GST certificate plus CIN or Udyam document, attach a dedicated phone number (mobile or landline, not on the consumer WhatsApp app), submit your display name for approval, complete embedded signup through a Meta-authorised BSP like RichAutomate, submit your first utility template (approves in minutes), and broadcast. Total elapsed time is typically 1 to 3 working days. No DLT registration is required, and setup itself is free on RichAutomate.
Timeline at a glance
Every step below has a typical duration so you can plan a launch sprint backwards from your go-live date. Meta controls the review steps, so treat these as typical ranges rather than guarantees:
| Step | What happens | Time | Blocker risk |
|---|---|---|---|
| 1. Business Manager verify | Create or claim Meta Business account | 30 minutes | Low |
| 2. GST + CIN upload | Submit legal entity proof to Meta | Same day to 48 hours | Medium — name mismatches re-review |
| 3. Dedicated phone | Number not on consumer WhatsApp | 15 minutes | Low |
| 4. Display name | Meta-side trade-name review | 1 to 24 hours | Medium — generic names rejected |
| 5. Embedded signup | BSP link + Cloud API provisioning | Under 30 minutes | Low |
| 6. First template | Utility → minutes; Marketing → 1 to 2 days | 10 minutes to 2 days | Low for utility, medium for marketing |
| 7. First broadcast | Send to opted-in audience | Immediate | None |
The DLT bypass — why this matters
An Indian SMS rollout under TRAI TCCCPR 2018 needs DLT registration on Jio, Airtel, Vi or BSNL portals first (principal entity, header, content templates, consent templates), which can take days to weeks. WhatsApp Business API runs on Meta Cloud API infrastructure and skips DLT entirely. This single difference makes WhatsApp the fastest legitimate path to ship transactional messaging in India.
Step 1 — Verify Meta Business Manager
Open business.facebook.com, create or claim your Meta Business account, then navigate to Business Settings → Security Centre → Start Verification. Match your business name exactly to your GST certificate.
Meta Business Manager is the parent account that holds your WhatsApp Business Account (WABA), Facebook page, Instagram account, and Meta Ads access. If you already run Meta Ads or manage a Facebook page, you have a Business Manager — just confirm you have admin access. If not, create one with the email you use for billing — this will become the long-term root account, so avoid personal Gmail in favour of a company-domain email.
The verification process kicks off inside Security Centre. Meta will ask for your legal business name and country (India). The business name you enter here must match your GST certificate, your Certificate of Incorporation, and your bank account name. A trailing "Pvt Ltd" versus "Private Limited" mismatch will not block you, but a different word order will. Many Indian businesses get rejected on the first pass because the marketing-facing brand name ("Acme") was entered instead of the legal name ("Acme Retail Private Limited"). Match the GST exactly.
Step 2 — Upload GST and CIN documents
Upload your GST registration certificate (the most commonly used document for Indian businesses), or a Certificate of Incorporation, Udyam certificate, or Shop and Establishment certificate. Add a recent utility bill in the company name as address proof.
Documents Indian businesses commonly submit include the GST registration certificate, Certificate of Incorporation under the Companies Act 2013, LLP agreement with MCA stamp, Udyam registration (for MSMEs), Shop and Establishment certificate (state-level), and partnership deed for traditional partnerships. The single document that closes verification fastest is the GST certificate paired with a recent utility bill — electricity, water, or telecom in the company name. Meta's exact list can change, so follow what the verification screen asks for.
Common failure modes in Indian business verifications:
- Address mismatch. GST shows the registered office, utility bill shows the operating office. Resolve by uploading a rental agreement that bridges the two, or a board resolution naming the operational address.
- Old utility bills. Use a recent bill; old documents often trigger re-review.
- Personal-name utility bills. An electricity bill in a director's name does not work — it must be in the company name.
- Partial GST certificate uploads. Upload all pages, not just the first.
Reference the official Meta document policy at the Meta Cloud API documentation and the MeitY DPDP framework for the underlying data-handling obligations on any business processing Indian consumer data.
Step 3 — Attach a dedicated phone number
Use a phone number — mobile or Indian landline — that is not active on the WhatsApp consumer app or WhatsApp Business app. The number must be able to receive a one-time OTP via call or SMS during verification.
The "dedicated" requirement is the single most-misunderstood part of API setup. The number does not need to be a brand-new SIM; it just cannot be currently active on the consumer apps. If you already use the number on consumer WhatsApp, you must deregister it first (Settings → Account → Delete account) and wait 30 minutes before adding it to the API.
For regulated industries — BFSI, healthcare, education, real estate — landline numbers map cleanly to fixed branch infrastructure and pass internal audit easier than mobile. Virtual numbers from cloud telephony providers like Knowlarity, Exotel, MyOperator, Servetel, and Tata Tele Business Services also work, provided the number can receive the verification OTP. Toll-free 1800 numbers often cannot receive the verification SMS or call, so confirm that before choosing one.
After verification, this number becomes the visible WhatsApp identity of your business. Customers see this number in their WhatsApp contact list. Plan it as a long-term decision, not a quick-start one.
Step 4 — Submit display name for Meta review
Your display name should match your legal business name or a registered trade name listed on your GST certificate. Avoid generic terms like "Support" or "Sales". Meta typically approves within 1 to 24 hours.
The display name is what customers see when they receive your messages. Meta reviews it against three rules: it must match the legal entity or a clearly-related trade name, it must not contain generic functional words alone ("Help", "Support", "Sales" as the entire name), and it must not impersonate any other business. Acceptable examples include "Acme Retail", "Acme Care", or "Acme Bookings" if those are visible on your registered branding. Unacceptable examples are "Customer Support", "Order Help", or "Sales Team".
If Meta rejects your first attempt, revise toward the exact legal name on the GST certificate and resubmit. A resubmitted name that matches the GST certificate verbatim is the most reliable fix.
Step 5 — Complete embedded signup via RichAutomate
Inside the RichAutomate dashboard, open WhatsApp → Connect and follow Meta's embedded signup popup: it links your Business Manager, creates or selects the WhatsApp Business Account, and registers your phone number on the Cloud API, usually in under 30 minutes, with no access tokens or Graph API calls to handle by hand.
Embedded signup is Meta's official onboarding flow for Cloud API accounts through a provider. Meta retired the self-hosted On-Premises API, so new accounts run on the Cloud API, and embedded signup is the standard way to connect one through a BSP or Tech Provider. The flow opens a Meta-hosted popup inside the provider's console, asks you to grant the provider access to the WABA, and provisions the Cloud API in the background, so you never copy tokens by hand.
Inside RichAutomate the entry point is the WhatsApp → Connect screen. Meta's popup walks you through the business, the WhatsApp Business Account, the phone number and the display name; if something is missing, such as an unverified business or a number still on the consumer app, it tells you what to fix. Once everything is in place, the number is usually ready within minutes.
If you prefer to evaluate BSPs before committing, our India WhatsApp Business API pillar ranks the top 7 providers on flat platform markup, feature depth, and onboarding speed.
Step 6 — Submit your first template for approval
Start with a utility template (order confirmation, appointment reminder, OTP). Utility templates approve in minutes. Marketing templates take 1 to 2 working days. Authentication templates approve in minutes using Meta's authentication template syntax.
Templates are pre-approved message structures with variable slots. You cannot send a freeform message to a customer outside the 24-hour customer service window — every business-initiated message must use a template. Meta prices messages in four categories, three of them template categories (utility, authentication, marketing) plus non-template service replies:
The conversation window cost calculator shows how the 24-hour window changes your per-conversation spend.
| Category | Use case | Approval time | India rate (Meta, October 2026) |
|---|---|---|---|
| Utility | Order updates, appointments, receipts | Minutes | ₹0.115 |
| Authentication | OTP, login verification | Minutes | ₹0.115 |
| Marketing | Promotions, offers, reactivation | 1 to 2 working days | ₹0.8631 |
| Service | Freeform reply inside 24h window | No template needed | First 1,000 a month per number free, then ₹0.115 (since 1 Oct 2026) |
Ship a utility template first — it approves fast and gives you a working broadcast within hours of completing embedded signup. Once that ships, queue marketing templates. The full categorisation playbook is in our utility vs marketing guide, and our rate hike playbook covers how to legitimately re-categorise traffic.
Get the India 2026 WhatsApp BSP price comparison
Wati vs AiSensy vs Interakt vs RichAutomate: Meta rates, platform fees and hidden costs, side by side. We send it to your WhatsApp in a minute.
Step 7 — Send your first broadcast
Once your template is approved, broadcast immediately to an opted-in audience using the RichAutomate campaign tool. There is no DLT registration, no TRAI peak-hour windowing, and no sender-ID approval. Templates ship 24x7 from the minute of approval.
The first broadcast is anti-climactic — that is the point. Open the Campaigns tab, select the approved template, upload a CSV of opted-in numbers (or pick a saved segment), schedule for "Now", and send. Delivery starts within seconds. Status callbacks (sent → delivered → read) come back via Meta webhooks and surface in your dashboard in real time.
The one operational rule that matters here: opted-in. Under the DPDP Act 2023 and its Rules, you need verifiable consent before sending business-initiated messages to any Indian consumer. RichAutomate keeps a per-contact consent log and handles opt-in and opt-out keywords (including your own words in Hindi or Gujarati), so you can show when and how each customer agreed. If you are not capturing opt-ins systematically yet, see our India regulation pillar for the DPDP plus TRAI plus Meta consent stack.
What it costs after setup: a worked month
Setup is free on RichAutomate; the bill starts with your first messages. Take a small Indian business that sends 6,000 marketing templates and 4,000 utility templates in a month and answers customer questions within the 1,000 free service replies. Using Meta's India rates, before GST:
| Line | Calculation | Amount |
|---|---|---|
| Meta marketing | 6,000 × ₹0.8631 | ₹5,178.60 |
| Meta utility | 4,000 × ₹0.115 | ₹460.00 |
| Meta service replies | Within 1,000 free | ₹0 |
| RichAutomate Client Pay fee | 10,000 × ₹0.10 | ₹1,000.00 |
| Total on Client Pay | Meta billed to you directly + RichAutomate fee | ₹6,638.60 |
| Total on SaaS Pay | 6,000 × ₹1.50 + 4,000 × ₹0.50, Meta included | ₹11,000.00 |
Client Pay is cheaper per message but needs a payment method on your Meta account; SaaS Pay costs more but gives one rupee invoice. Optional plans (₹499, ₹899 or ₹1,199 a month) add features and are not needed to send. Other providers price differently, some with a monthly subscription, some with a lower per-message fee (Gupshup's self-serve WhatsApp fee is listed at US$0.001, about ₹0.088, per message plus Meta). Compare them in our WhatsApp API pricing comparison for India and the cheapest WhatsApp Business API in India guide, see every RichAutomate line on the pricing page, or start the 14-day trial with 100 message credits.
What setup looks like across BSPs — comparison table
The setup process above is identical across every Meta-authorised BSP in India because Meta owns the verification, approval, and Cloud API provisioning steps. What varies is onboarding help, template categorisation assistance, consent tooling, and how the provider bills. Competitor details change often, so check each provider's own pricing page. Comparison as of October 2026:
| Provider | Embedded signup | DPDP consent UX | RBI/IRDAI playbooks | Platform pricing |
|---|---|---|---|---|
| RichAutomate | Yes | Built-in consent log + opt-out keywords | Sector guides on our blog | ₹0.10/msg + Meta (Client Pay) or ₹1.50 / ₹0.50 all-in (SaaS Pay); ₹0 setup |
| AiSensy | Yes | See their docs | See their docs | Subscription plans; see their pricing page |
| Interakt | Yes | See their docs | See their docs | Subscription plans; see their pricing page |
| Wati | Yes | See their docs | See their docs | Subscription plans; see their pricing page |
| Gupshup | Yes | See their docs | See their docs | Self-serve WhatsApp US$0.001/msg + Meta (checked 30 Oct 2026); enterprise on quote |
Deep dives in our comparison hub: RichAutomate vs AiSensy, RichAutomate vs Interakt, RichAutomate vs Wati, RichAutomate vs Gupshup, and the DoubleTick alternative breakdown.
Regulatory snapshot — DPDP, TRAI, Meta as of October 2026
WhatsApp Business API in India sits at the intersection of three regimes: Meta's own policy (template categories, opt-in requirements, prohibited content), TRAI under TCCCPR 2018 (which carves WhatsApp out of DLT but still expects consent), and the DPDP Act 2023 with its Rules (which govern all personal data processing). The relevant authority links:
- MeitY — DPDP Act 2023 and Rules
- TRAI — Telecom Commercial Communications Customer Preference Regulations
- Meta Cloud API v24.0 — official documentation
- RBI — circulars for BFSI WhatsApp use
- IRDAI — insurance digital communication guidelines
For sector-specific runbooks see our vertical playbooks pillar and the SEBI investment-adviser compliance guide for capital-markets nuance.
Common setup failures and how to fix them
- Business name mismatch between Meta and GST. Symptom: Business verification stuck for over 72 hours. Fix: re-enter the business name verbatim from the GST certificate, including legal form ("Private Limited", "LLP").
- Phone number still on consumer WhatsApp. Symptom: embedded signup fails at the number-registration step. Fix: delete account from consumer app, wait 30 minutes, retry.
- Generic display name rejection. Symptom: display name pending over 48 hours. Fix: change to legal entity name or registered trade name on GST.
- Template rejected or recategorised on first submission. Symptom: a template filed as utility is rejected or moved to marketing because it contains promotional wording. Fix: re-submit under marketing category, or rewrite to remove promotional language if utility is the right fit.
- First broadcast undelivered. Symptom: status stuck at "sent" never reaching "delivered". Fix: confirm the recipient has WhatsApp installed and that their number has the country code (+91) in international format.
What to ship in week one after go-live
Setup is the easy part. The first week post-go-live decides whether WhatsApp becomes a real channel or a forgotten one. Our standard tenant week-one ship list:
- Day 1. First utility broadcast to a 500-contact sample of opted-in customers. Measure the delivery rate and check failed numbers for missing +91 prefixes or numbers not on WhatsApp.
- Day 2. Wire up a basic auto-reply flow for inbound messages. Each customer message opens a 24-hour customer service window; your replies inside it are service messages, free for the first 1,000 a month per number.
- Day 3. Launch one CTWA ad campaign with the Free Entry Point benefit so new inbound conversations start free.
- Day 4. Submit two more marketing templates so your campaign queue has variety.
- Day 5. Configure DPDP consent capture on your website and at point-of-sale.
- Day 6. Set up a flow in our visual flow builder for one common customer journey (booking, support escalation, order tracking).
- Day 7. Review week-one billing dashboard and confirm Meta per-message charges match expectation.
Further reading
- Meta India WhatsApp rate hike — cost playbook
- Switching BSPs without breaking the business
- DPDP consent manager — November 2026 checklist
- India regulation pillar (DPDP, TRAI, RBI, IRDAI)
- Best WhatsApp Business API in India — 2026 ranking
- Industry use-cases — verticalised WhatsApp playbooks
Onboard with RichAutomate this week
We walk through the seven-step setup with you on a 30-minute screen-share: embedded signup, your first utility template submitted, and a test broadcast as soon as Meta approves it (business verification itself can take Meta a day or two). Pricing is flat and public: ₹0 setup and no required monthly plan (optional plans from ₹499/month) — Client Pay at ₹0.10 per message with Meta's per-message charges billed direct, or SaaS Pay at ₹1.50 marketing / ₹0.50 utility and authentication all-in, with a 14-day free trial and 100 credits.
Start your 14-day free trial → · Book a 30-minute onboarding call · WhatsApp us at +91 81603 11319 · See full pricing
That covers submitting the display name for the first time. If the name is already live and wrong - a legacy brand, an agency default, or a rejection you never chased - see how to change a WhatsApp display name and read its actual status, including the two Graph fields that tell you whether a change is pending or was quietly declined.
A number can clear approval and still be unusable if the Cloud API registration call never ran — see why a WhatsApp API number shows as not registered.
Saving the callback URL is only half the webhook step — the app still has to be subscribed to the WABA. See webhook verified but not receiving messages.
Sending your first image is where most setups hit their second wall. See WhatsApp API media upload failures and fixes.
Before you submit, check the common reasons WhatsApp display names get rejected in India so your approval isn't delayed by an avoidable naming mistake.