
AI Voice CRM for Lead Qualification: An Enterprise Case Study
Enterprise client, name withheld under NDA.
Read article
WhatsApp Automation
Step-by-step guide to building a WhatsApp AI bot in India: Meta Business API access, Business Manager verification, automation layer, first conversation flow, CRM integration, and pricing.
By QuensultingAI 7 min read

Key takeaway: Building a WhatsApp AI bot in India is not a chatbot plugin install. It requires Meta Business API access, a verified Business Manager, an approved phone number, and an automation layer that connects conversations to your CRM. This guide walks through each step in order.
The WhatsApp consumer app and WhatsApp Business app are not the same as the WhatsApp Business Platform (Cloud API). Production AI bots in India run on the Business Platform, which provides:
You cannot scale a real AI bot on the free Business app alone. You need API access through Meta or an approved Business Solution Provider (BSP).
Our WhatsApp AI bot implementations always start with API readiness, not prompt design.
Create Business Manager
Go to business.facebook.com and create a Business Manager account with your legal business name matching your GST registration or incorporation documents. Mismatched names delay verification.
Add business details
Start business verification
Meta reviews documents to confirm the business is real. For Indian companies, typical documents include:
Verification can take a few days to several weeks. Start this before you build conversation logic.
Assign roles
Give your implementation partner or internal admin Developer and Business Admin roles as needed. Do not share personal Facebook passwords; use role-based access.
Add WhatsApp product
Inside Business Manager, add the WhatsApp product and create a WhatsApp Business Account (WABA).
Phone number selection
You can use:
The number must receive SMS or voice OTP for verification. VoIP numbers often fail verification.
Display name approval
Your public WhatsApp business display name must match your brand and Meta commerce policies. Rejected names block go-live.
Connect Cloud API
Meta Cloud API hosts the webhook endpoint configuration. Register callback URL and verify token for inbound message events.
Message templates
Outbound messages outside an active 24-hour customer service window require pre-approved templates. Plan templates early for:
Template approval adds lead time. Factor it into launch schedules.
The API delivers messages. Something else must decide replies. Common choices for Indian businesses:
| Layer | Best for | India notes |
|---|---|---|
| n8n | Custom flows, CRM integration, voice handoff | Self-hosted or cloud; cost-effective at scale |
| Make | Visual automation, mid-complexity | Per-operation pricing adds up at volume |
| Zapier | Simple triggers, fast prototypes | Higher per-task cost for high message volume |
| Custom backend | Full control, large engineering team | Highest build and maintenance burden |
We recommend n8n for most Indian SMEs connecting WhatsApp to HubSpot, Zoho, voice callbacks on Retell or Vapi, and internal databases. See our AI automation approach for hub-and-spoke design.
Voice plus WhatsApp is a common pattern: AI voice call for urgent qualification, WhatsApp for documents, links, and async follow-up.
Start with one high-volume intent, not a general-purpose bot.
Example: lead capture after ad click
AI reply layer
Connect an LLM with strict system prompt boundaries:
Session window rules
Free-form AI replies are allowed inside the 24-hour customer service window after user message. Outside that window, use approved templates only.
Log every inbound and outbound message ID for billing reconciliation and support debugging.
WhatsApp without CRM sync creates another silo. Minimum integration requirements:
HubSpot, Zoho CRM, and Salesforce all integrate via n8n. Our CRM integration patterns apply directly to WhatsApp events.
Bidirectional sync prevents automation from overwriting manual rep updates without rules.
WhatsApp Business Platform billing is conversation-based, not per-message in the traditional SMS sense. Meta groups messages into 24-hour conversation windows by category:
Rates vary by country and category. India pricing is published on Meta's rate cards and changes periodically. Budget for:
A bot that blasts marketing templates without session discipline gets expensive quickly. Design flows to maximise service and utility categories where appropriate.
Mistake 1: Starting with the chatbot UI before verification
Fix: Complete Business Manager verification and number registration first.
Mistake 2: No template strategy for outbound
Fix: Submit core templates during build phase, not launch week.
Mistake 3: Unbounded LLM replies on regulated topics
Fix: Scope knowledge base, add guardrails, require human escalation on sensitive intents.
Mistake 4: Ignoring opt-out and data retention
Fix: Document consent, honour stop requests, align storage with DPDPA.
Mistake 5: WhatsApp silo with no CRM write-back
Fix: Every qualified conversation creates or updates CRM within seconds.
Mistake 6: Using personal WhatsApp for business scale
Fix: Migrate to API before volume makes migration painful.
More on
Tags: WhatsApp AI Bot · Meta Business API · India WhatsApp · n8n Automation · CRM Integration · Chatbot Setup
FAQ
Verification is the long pole: 1 to 4 weeks. Technical integration for a first flow: 2 to 3 weeks after API access.
Many SMEs use Meta Cloud API direct with n8n. BSPs help when you want managed onboarding or combined invoicing.
Yes. Prompt and model tuning for Hinglish improves quality. Test with real user messages.
Yes. Common pattern: WhatsApp capture, voice callback on Retell, Vapi, or Dograh, CRM update via n8n. ## Related on this site - [WhatsApp AI bot solutions](/solutions/whatsapp-ai-bot) - [CRM integration](/solutions/crm-integration) - [India market](/markets/india) - [Contact our team](/#contact)
Keep reading

Enterprise client, name withheld under NDA.
Read article

Deploying a Retell AI voice agent is a genuine competitive advantage.
Read article

Why Indian SMEs adopt n8n over Zapier and Make, self-hosted vs cloud options, and five workflows we deploy most: WhatsApp lead capture, voice-to-CRM, form qualification, order notifications, and onboarding triggers.
Read article
Talk to a partner about your calls, channels and systems. 30 minutes, no slides, an honest view of where to start.
Talk to a partnerPrefer email? sales@quensultingai.com