WhatsApp Business API for Contact Centers: The Complete Guide (2026)
Prashanth Kancherla
Jun 5, 2026 | 15 mins read
What Is WhatsApp Business API for Contact Centers?
WhatsApp Business API lets medium and large businesses connect WhatsApp to their contact center, CRM, and chatbot systems to handle customer conversations at scale. Unlike the standard WhatsApp Business App, it supports multi-agent workflows, automation, and full CRM integration — making it the only viable option for contact centers managing more than a handful of daily conversations.
This guide covers: what WABA is, how it differs from the basic app, why contact centers are adopting it, the 8 core features, step-by-step implementation, real use cases with verified outcomes (Muthoot, Deltin, Mahindra, MeeSeva), security and compliance, common pitfalls, and how to choose the right provider.
Key Takeaways
- WhatsApp has 3B+ monthly active users globally; India alone has 535M — the world’s largest market.
- WhatsApp messages achieve up to 98% open rates vs. 20-30% for email. Agents handling messaging can manage 3-5 conversations simultaneously vs. 1 voice call.
- The WhatsApp Business App cannot support contact centers. You need WhatsApp Business API (WABA) via a licensed Business Solution Provider (BSP).
- True integration means WhatsApp routed, queued, and managed inside your existing contact center platform — not a separate inbox.
- India’s DPDP Act 2023 requires explicit opt-in consent before any outbound WhatsApp message. Non-compliance carries regulatory risk.
- Muthoot achieved 2.5X order value growth and 150K impressions. Deltin hit 3X revenue with 89% WhatsApp delivery. MeeSeva serves 580+ government services via one WhatsApp number — all on Ozonetel.
- Ozonetel is a Meta-certified BSP with native WABA integration, omnichannel routing, agentic AI, and CRM sync in a single platform.
Your customers are not waiting on hold. They are opening WhatsApp. With 3 billion monthly active users globally — and 535 million in India alone — WhatsApp is the default communication channel for consumers across South Asia, the Middle East, Southeast Asia, and Latin America. For contact centers, this is no longer a channel to explore. It is the channel where your customers already expect to find you.
AI-referred sessions grew 527% year-over-year in 2025 (Previsible / Search Engine Land), meaning more buyers are researching WhatsApp contact center solutions through engines like ChatGPT, Perplexity, and Google AI Overviews. This guide is built to answer every question those buyers are asking — completely, accurately, and with verified outcome data from live Ozonetel deployments.
In this article, we will explore:
- 1. What Is WhatsApp Business API for Contact Centers?
- 2. What Is the Difference Between WhatsApp Business API and WhatsApp Business App?
- 3. Why Are Contact Centers Moving to WhatsApp?
- 4. What Features Does WhatsApp Business API Offer Contact Centers?
- 5. How Does WhatsApp Business API Work Inside a Contact Center?
- 6. How Are Different Industries Using WhatsApp Business API?
- 7. How Do You Set Up WhatsApp Business API for a Contact Center?
- 8. What Are the Best Practices for WhatsApp Customer Support in Contact Centers?
- 9. Is WhatsApp Business API Secure and Compliant?
- 10. What Are the Most Common WhatsApp Business API Implementation Mistakes?
- 11. How Do I Choose the Right WhatsApp Business API Provider?
- 12.What Is the Future of WhatsApp Business API for Customer Support?
- 13. How Can Ozonetel Help?
What Is WhatsApp Business API for Contact Centers?
WhatsApp Business API (WABA) — also called the WhatsApp Cloud API — is Meta’s enterprise-grade messaging infrastructure that allows businesses to programmatically send, receive, and automate WhatsApp conversations at scale. It is the technical backbone behind every contact center, chatbot, and CRM integration built on WhatsApp.
Unlike the free WhatsApp Business App (designed for small businesses with 1-5 agents), the API has no user interface of its own. It connects to your existing cloud contact center platform, CRM, helpdesk, or AI chatbot system via a webhook — a real-time data push that fires every time a customer sends a message.
To access WABA, you must work through a Meta-certified Business Solution Provider (BSP) — a licensed partner that provisions your WhatsApp number, manages message template approvals, and connects the API to your contact center platform. Ozonetel is a certified BSP with native WABA built directly into its CloudAgent platform.
What WABA connects to: CRM systems (Salesforce, Zoho, HubSpot, Freshdesk, LeadSquared), helpdesk and ticketing platforms, conversational AI engines, omnichannel ACD routing, and analytics dashboards.
What Is the Difference Between WhatsApp Business API and WhatsApp Business App?
One-line answer: the WhatsApp Business App is built for solo operators and micro-businesses; the WhatsApp Business API is built for contact centers, enterprises, and any team handling more than a handful of conversations per day. For a full side-by-side breakdown, see WhatsApp API vs. WhatsApp Business App.
| Message Category | What It Covers |
|---|---|
| Utility | Transactional messages such as order confirmations, payment receipts, shipping notifications, appointment reminders, and OTPs. |
| Authentication | Account verification messages including login OTPs, two-factor authentication (2FA) codes, password resets, and identity verification. |
| Marketing | Promotions, discounts, product launches, abandoned-cart reminders, customer re-engagement campaigns, and other revenue-generating communications. |
| Service | Any message sent within 24 hours of a customer-initiated conversation. These messages are generally free in most markets during the active customer service window. |
When the App is enough: businesses with fewer than 5 agents, no CRM integration requirement, and under 50 WhatsApp conversations per day. Every other scenario requires the API.
Cost model: Meta moved to per-message pricing in 2025. Messages are categorised as utility, authentication, marketing, or service — each with different per-message rates. Service messages (replies within a 24-hour customer-initiated window) are generally free in most markets.
Why Are Contact Centers Moving to WhatsApp?
| Channel | Open Rate | Agent Capacity | Customer Preference (India) |
|---|---|---|---|
| Up to 98% | 3–5 concurrent conversations per agent | Primary customer channel for 535M+ WhatsApp users | |
| 20–30% | Queue-based, asynchronous handling | Declining preference for support-related queries | |
| SMS | ~82% | Primarily outbound communication at scale | Increasingly replaced by WhatsApp for rich interactions |
| Voice (Phone) | N/A — Pickup Rate Based | 1 call per agent at a time | Preferred mainly for complex issues and escalations |
Four data points that explain the shift:
- WhatsApp messages achieve up to 98% open rates 20-30% for email (Wapikit Business Statistics, 2025)
- Agents handling messaging conversations can manage 3-5 simultaneous conversations 1 voice call — a direct operational efficiency gain
- Businesses implementing WhatsApp support alongside AI-powered automation report 25-40% reduction in inbound call volume as customers self-serve
- 69% of consumers are more likely to buy from a business on WhatsApp; 56% abandon a purchase when response times are slow (Dragapp, 2025)
What Features Does WhatsApp Business API Offer Contact Centers?
Each feature below is defined as implemented in an enterprise contact center context — not as described in Meta’s consumer documentation.
Multi-Agent Inbox with Conversation Assignment
A multi-agent inbox allows unlimited agents to access a shared WhatsApp queue simultaneously. Conversations are assigned to specific agents or skill groups, locked to prevent duplicate responses, and transferable without losing message history. This is architecturally impossible with the WhatsApp Business App, which ties conversations to a single device.
AI Chatbot and Automation Workflows
The API supports full WhatsApp chatbot deployment — NLP-driven bots that handle Tier 1 queries (FAQs, status checks, account lookups), collect structured data, and route to live agents based on configurable escalation triggers. Bot-to-human handoff must pass the full conversation context to the agent.
Rich Media Messaging
Beyond text, WABA supports inbound and outbound: images, PDFs, videos, voice notes, location pins, product catalogs, and interactive buttons and list menus. This enables document collection (ID verification, claim photos), product showcasing (jewelry catalogs, property listings), and structured self-service — all within the WhatsApp thread.
Message Templates (HSMs — Highly Structured Messages)
Outbound business-initiated messages must use pre-approved message templates (HSMs). These are submitted to Meta for approval (typically 24-72 hours). Templates are categorised as: utility (order confirmations, shipping updates), authentication (OTPs, 2FA codes), and marketing (promotions, re-engagement). The 24-hour session window applies after a customer initiates contact — within that window, agents can send free-form messages without template restrictions.
CRM and Helpdesk Integration
Every WhatsApp conversation should be visible in your CRM against the customer’s record. Ozonetel’s agent assist surfaces CRM data (contact history, account status, previous interactions) to the agent before they type a word. Native integrations cover Salesforce, Zoho CRM, HubSpot, Freshdesk, Zendesk, and LeadSquared.
End-to-End Encryption (E2EE)
WhatsApp applies E2EE (Signal protocol) to all messages in transit. What E2EE covers: message content in transit. What it does not cover: metadata, transcripts stored in your CRM or contact center platform, or cloud backups on the customer’s device.
Analytics and Reporting Dashboards
WhatsApp-specific metrics to track: first response time, average handling time, bot containment rate, CSAT per conversation, and message volume by hour. Ozonetel’s Voice of Customer layer extends analytics across WhatsApp and voice — surfacing sentiment, intent, and resolution quality in a single dashboard.
WhatsApp Flows
WhatsApp Flows — launched by Meta, expanding through 2025-26 — are structured, interactive forms that run inside the WhatsApp conversation. Customers complete multi-step actions (book an appointment, submit a claim, verify identity, apply for a loan) without leaving the app.
How Does WhatsApp Business API Work Inside a Contact Center?
A customer sends a WhatsApp message to your business number; the API delivers it to your contact center platform in real time, where it enters the routing engine, is handled by a bot or agent, and the response returns through the same API connection — within the same chat thread the customer already has open.
Step-by-step message flow:
1.Customer sends a WhatsApp message to your business number.
2.Meta’s WhatsApp Cloud API receives the message and fires a webhook to your BSP (Ozonetel) in real time.
3.Ozonetel’s platform checks for an active open conversation. If one exists, the message is appended. If not, a new conversation is created and enters the queue.
4.The AI chatbot layer handles first interaction — greeting, query classification, authentication — and resolves Tier 1 queries autonomously.
5.Complex queries enter the omnichannel ACD queue, distributed to the right agent skill group alongside voice calls.
6.The agent receives the conversation on a unified desktop — full WhatsApp history, CRM data, and bot-collected context visible before they type a word.
7.On resolution, the conversation closes, the transcript logs to the CRM, and a CSAT message fires automatically.
How Are Different Industries Using WhatsApp Business API?
The highest-ROI WhatsApp use cases differ by vertical. Below are the primary applications — each anchored to a verified Ozonetel customer outcome.
NBFC and Financial Services — Muthoot Gold Bullion Corporation
Use cases: product catalog distribution, customer engagement, EMI payment reminders, loan account updates, digital KYC initiation.
Case Study: Muthoot Gold Bullion Corporation
2.5X Average Order Value Growth 150K WhatsApp Impressions in 9 Months
Muthoot launched Indivara — a zero-inventory gold jewelry vertical — using Ozonetel’s WhatsApp platform to create a phygital model: customers viewed products via WhatsApp catalogs, then purchased at the nearest branch.
- WhatsApp chatbot deployed digital jewelry catalogs to Muthoot’s 5M+ customer base instantly — no retail stores, no printed catalogs
- Average order value grew from Rs.20,000 to Rs.50,000 (2.5X) through data-driven WhatsApp campaigns
- 150,000 WhatsApp impressions in 9 months of launch
- Voice bot: 43,500 automated EMI reminder calls in 5 months, Rs.2,00,000 in agent cost savings, 5-8% improvement in EMI collection
- ERP synced with WhatsApp catalog for single-step inventory updates across all centers
“Since we follow a zero inventory, phygital model for the jewellery vertical we are indebted to Ozonetel for quickly deploying these tech for our Go To Market strategy.” — Haridas P.C., AGM, Muthoot Gold Bullion Corp
Entertainment and Hospitality — Deltin
Case Study: Deltin — Star Weekend Campaign
3X Revenue Increase 89% WhatsApp Delivery Rate
Deltin used Ozonetel’s WhatsApp platform for a hyper-personalized, AI-driven loyalty campaign — deploying celebrity-led video messages to targeted customer segments for their Star Weekend event.
- 89% WhatsApp delivery rate — 3X higher than traditional channels
- 70% open rate for WhatsApp video messages — 5X improvement over prior campaigns
- 16% of dormant customers reactivated through personalized WhatsApp outreach
- 100% event bookings achieved within two weeks of campaign launch
- 7,800 footfalls at the event — a record for Deltin
- 3X revenue increase attributed to wider reach and hyper-personalized WhatsApp engagement
Agriculture and Rural Markets — Mahindra Farm Machinery (#KisanBot)
Case Study: Mahindra Farm Machinery — #KisanBot
Tier-3 Rural Market Penetration 24/7 AI-Powered Farmer Support
Mahindra partnered with Ozonetel to deploy #KisanBot — an AI-engineered WhatsApp chatbot built for Tier-3 farmers aged 28-65 — enabling secure, real-time, bilingual (Hindi/regional language) communication across the full customer journey.
- Farmers connect with Mahindra directly via WhatsApp from anywhere — no branch visit required
- Bulk WhatsApp campaigns drove product awareness in markets previously unreachable through traditional channels
- AI chatbot categorized query patterns (product, service, dealer, complaint) for faster, more relevant routing
- Sales teams received pre-qualified leads with full conversation context, reducing response time significantly
- End-to-end encryption ensured trust for rural users unfamiliar with digital business communication
Government and Public Services — MeeSeva, Government of Telangana
Case Study: MeeSeva — Government of Telangana
580+ Government Services via WhatsApp 24/7 Availability — No Queues, No Forms
The Government of Telangana deployed MeeSeva services on WhatsApp (Nov 2025), powered by Ozonetel’s agentic AI — enabling citizens to access 580+ services through a single WhatsApp number, without visiting a physical center.
- Agentic AI (multiple autonomous agents) executes end-to-end government service journeys — no human required for most transactions
- Supports English and Telugu; understands intent, validates eligibility, triggers payments, delivers certificates on WhatsApp
- Services: bill payments, certificate applications, registration slot booking, exam hall ticket downloads, crop price queries
- Significant reduction in physical MeeSeva centre footfall — lower cost per transaction through intelligent automation
- Repeatable model being adapted for additional public services across Telangana
How Do You Set Up WhatsApp Business API for a Contact Center?
- Choose a Meta-certified BSP: Look for native contact center integration (not a third-party connector), a no-code chatbot builder, and CRM connectors for your existing stack. Verify Meta partner status at business.whatsapp.com.
- Complete Meta Business Verification: Submit business registration documents (GST certificate, PAN, incorporation documents for Indian businesses). Timeline: 3-5 business days.
- Register and provision your WhatsApp number: The number must be dedicated, capable of receiving SMS/voice for verification, and recognisable to your customers. Timeline: 1-2 business days.
- Integrate with your contact center platform: Your BSP connects the API to your ACD routing engine, CRM, and helpdesk. For Ozonetel deployments, this is native — no middleware required.
- Build chatbot flows and automation: Configure greeting messages, FAQ bot flows, intent-based routing rules, and escalation triggers. Define bot containment targets (typically 60-80% for Tier 1) before launch.
- Create and submit message templates (HSMs): Plan for a 3-7 day Meta review cycle per template. Common rejection reasons: promotional language in utility templates, missing opt-out instructions in marketing templates.
- Train support agents: Messaging differs from voice in tone, pace, and multitasking. Pair agent training with Agent Assist to accelerate ramp time.
- Go-live checklist: Test all bot flows, validate CRM auto-logging, configure SLA alerts, confirm opt-in consent flows are live, verify opt-out processing is automated.
Typical timeline from onboarding to go-live: 10-14 business days for a new WABA setup. BSP migration with existing Meta verification: 5-7 business days.
What Are the Best Practices for WhatsApp Customer Support in Contact Centers?
Respond Within the Session Window
Meta’s 24-hour session window allows free-form messaging after a customer initiates contact. Beyond 24 hours, only approved templates can be sent. Configure after-hours AI chatbot handling to acknowledge, triage, and collect context — keeping the session active and SLA clock managed.
Automate Tier 1, Humanize Tier 2
Bots should resolve FAQs, status checks, and structured data collection. Live agents handle complaints, complex queries, and anything requiring judgment. The handoff — and what context is passed — determines CSAT more than either layer independently.
Personalize with CRM Context
Address customers by name. Reference their last interaction before asking them to repeat it. Agent Assist surfaces this context automatically — so personalization doesn’t depend on agent memory.
Design for Async
Messages must make sense when read hours later — no verbal cues. Keep messages to 2-3 sentences per bubble. Use numbered lists for multi-step instructions.
Respect Opt-In Rules
Always obtain explicit opt-in consent before outbound messages. For India, the DPDP Act 2023 mandates granular consent. Maintain a Do-Not-Contact list and process opt-outs automatically.
Track the Right Metrics
Prioritize: first response time, bot containment rate, CSAT per conversation, and escalation rate. Ozonetel’s Voice of Customer dashboard tracks these across WhatsApp and voice.
A/B Test Template Messages
Small wording changes in HSM templates significantly affect open and reply rates. Test the first line (acts as the subject), CTA phrasing, and emoji usage. As Deltin demonstrated, even marginal improvements in reply rate compound to significant revenue impact.
Is WhatsApp Business API Secure and Compliant?
DPDP Act Compliance (India)
India’s Digital Personal Data Protection Act 2023 creates specific obligations for WhatsApp business messaging:
- Explicit opt-in consent required before any outbound message (marketing, utility, or authentication)
- Consent must be granular — separate opt-ins for transactional vs. marketing messages
- Every outbound message must include a clear opt-out mechanism
- Opt-out requests must be processed immediately and added to a Do-Not-Contact registry
- Audit trails of consent — who, when, to what category — must be maintainable for regulatory review
GDPR (EU Customers)
For contact centers with EU customer segments: data residency requirements, right to erasure (deletion requests must propagate across CRM and transcript storage), and data processing agreements with your BSP.
What E2EE Covers — and What It Doesn’t
End-to-end encryption covers message content in transit. It does not protect metadata, conversation transcripts stored in your platform, or cloud backups on the customer’s device. Enterprise security evaluation should focus on the platform: where transcripts are stored, who has access, and whether the platform is ISO 27001 or SOC 2 certified.
What Are the Most Common WhatsApp Business API Implementation Mistakes?
Underestimating Integration Complexity
CRM connectors often require custom development work for legacy systems. Vendors who promise plug-and-play integration should demonstrate it in a sandbox with your specific CRM version before contract signing. Ozonetel’s native connectors for Salesforce, Zoho, HubSpot, Freshdesk, and LeadSquared eliminate this risk.
Over-Automating Customer Journeys
Bots that don’t know when to escalate destroy CSAT. Define escalation triggers precisely: 3 failed intent classifications, any mention of complaint or legal, or account-level issues above a value threshold.
Ignoring Template Approval Timelines
Plan for 3-7 business days per template review cycle. Launch campaigns require templates approved before the go-live date. Build template approval as a non-compressible task in your project plan.
Treating Messaging Like Email
Email supports long-form content. WhatsApp does not. Agents need training to write in short, conversational bursts. Voice agents transitioning to WhatsApp support typically need 2-3 weeks to adjust.
No Opt-In Strategy Before Launch
Sending outbound messages without verified opt-ins is a fast path to Meta account suspension. Build your opt-in collection flow before your WABA goes live. Have consent data in the CRM before the first campaign fires.
Poor Escalation Design — Customers Repeat Themselves
When a bot hands off to an agent, the agent must see everything the bot collected. Ozonetel’s omnichannel routing carries the full conversation context through escalation. If the agent asks questions the bot already asked, CSAT drops immediately.
How Do I Choose the Right WhatsApp Business API Provider?
A BSP provisions your WABA number, manages your Meta relationship, and — if they are also a contact center platform provider like Ozonetel — integrates WhatsApp directly into routing, automation, and reporting infrastructure.
BSP Evaluation Checklist — 8 Criteria
1. Official Meta partner status — verify at business.whatsapp.com/partners
2. Native contact center integration — WhatsApp in the same routing engine as voice, not a separate tool
3. Native CRM connectors — Salesforce, Zoho, HubSpot, Freshdesk (not middleware-dependent)
4. Built-in no-code chatbot builder — operations teams configure bots without developer dependency
5. Analytics depth — WhatsApp-specific: first response time, bot containment, CSAT, escalation rate
6. Pricing model clarity — see Meta’s official per-message pricing + ask for BSP fee itemised separately
7. Data residency options — India-based storage for DPDP Act compliance; EU-compliant for GDPR
8. Onboarding SLA and dedicated implementation support
5 questions to ask vendors in evaluation calls:
- “Can you demonstrate WhatsApp and voice in the same routing queue — live, in your platform?”
- “Show me what the agent desktop looks like handling a WhatsApp conversation alongside a voice call.”
- “How does your platform handle DPDP Act opt-in requirement at scale?”
- “What is your SLA for template approval support when Meta rejects a submission?”
- “Can you provide reference contacts from customers in our industry who went live in the last 12 months?”
What Is the Future of WhatsApp Business API for Customer Support?
Agentic AI — End-to-End Autonomous Resolution
The next evolution beyond chatbots: agentic AI systems where multiple autonomous AI agents work together to understand intent, validate eligibility, trigger actions, and determine when a human is actually needed. Ozonetel’s MeeSeva deployment — 580+ government services resolved end-to-end on WhatsApp — is a live production example of agentic AI at scale.
WhatsApp Flows — In-Chat Application Journeys
Flows allow businesses to build structured, multi-step forms running inside the WhatsApp conversation — loan applications, insurance claims, KYC, appointment booking. For contact centers, Flows eliminate the redirect to web forms, reducing drop-off and improving completion rates.
Conversational Commerce
In-chat product discovery, catalog browsing, and checkout — without leaving WhatsApp. For D2C brands, this means the full purchase journey (discover → inquire → buy → track) contained in one thread. Muthoot’s Rs.50,000 average order value on a WhatsApp catalog is an early-stage benchmark for what conversational commerce looks like in practice.
Omnichannel Unification
WhatsApp, voice, email, SMS, and social in a single agent queue — with unified customer identity across channels. The convergence of omnichannel routing and WhatsApp’s API capabilities is the direction all enterprise contact center platforms are moving.
How Can Ozonetel Help?
Ozonetel is a Meta-certified WhatsApp Business Solution Provider and AI-powered cloud contact center platform. WhatsApp is not a bolt-on: it is a first-class channel within the same routing, automation, analytics, and agent desktop infrastructure as voice, email, and chat.
| Capability | What Ozonetel Delivers |
|---|---|
| WABA Access | Meta-certified BSP providing number provisioning, template approvals, and WhatsApp Cloud API connectivity. |
| Omnichannel Routing | WhatsApp conversations routed through the same ACD queue as voice interactions, using shared routing rules, SLAs, and agent pools. |
| Agent Desktop | Unified workspace combining WhatsApp, voice, and email interactions, with Agent Assist displaying CRM data before the first response. |
| Chatbot Builder | No-code Voice AI Agent builder for FAQs, lead qualification, workflow automation, and WhatsApp Flows. |
| Agentic AI | Multi-agent autonomous systems capable of handling complete service journeys end-to-end, as demonstrated in the MeeSeva Telangana deployment. |
| CRM Integration | Native integrations with Salesforce, Zoho, HubSpot, Freshdesk, Zendesk, and LeadSquared without requiring middleware. |
| Analytics | Voice of Customer analytics, Quality Audits, conversation insights, and performance reporting across WhatsApp and voice channels. |
| Compliance | DPDP Act compliance support including opt-in/opt-out automation, consent management, audit trails, and India-based data residency. |
| Deployment | 10–14 business days for a new WhatsApp Business Account (WABA) deployment and 5–7 business days for migration from another BSP. |
Trusted by 3,500+ businesses including Muthoot, Mahindra, Deltin, and the Government of Telangana. See Ozonetel’s WhatsApp Business Solution for the full platform overview.
Conclusion
Messaging is now a core contact center channel, not a nice-to-have. WhatsApp Business API delivers three things email and voice cannot provide simultaneously: faster resolution through async messaging and bot automation, lower cost per interaction through agent multitasking and bot containment, and better customer experience through the channel customers already prefer.
The businesses that moved first — Muthoot in NBFC jewelry, Deltin in entertainment loyalty, Mahindra in rural agriculture, and the Government of Telangana in public services — have built engagement infrastructure that competitors will struggle to replicate quickly.
Frequently Asked Questions
WABA enables outbound marketing campaigns to opted-in customers via approved HSM templates — including images, videos, product catalogs, and interactive buttons. Campaign messages achieve up to 98% open rates and 70%+ engagement vs. 20-30% for email. The Deltin case above demonstrates 3X revenue and 89% delivery from a single WhatsApp campaign.
Yes. Ozonetel has native integrations with Salesforce, Zoho CRM, HubSpot, Freshdesk, Zendesk, and LeadSquared — conversations auto-log to contact records, tickets are created or updated, and CRM data surfaces via Agent Assist before the agent types a word. No middleware required.
Both operate within the same WhatsApp thread, visible to the customer as the same business number. A WhatsApp chatbot handles Tier 1 queries autonomously. A live agent takes over for complex or escalation-flagged conversations. The critical design element is the handoff: the agent must receive full context before responding.
Process: (1) complete Meta Business Verification with business registration documents, (2) work with a certified BSP to provision a dedicated phone number, (3) create and submit a WhatsApp Business Profile. Common delays: business name mismatches between Meta and government registration documents. Timeline: 5-10 business days end-to-end.
Unlimited. Unlike the WhatsApp Business App (1 device), WABA supports any number of concurrent agents — all working from a shared omnichannel inbox, with conversation assignment and locking preventing duplicate responses.
Configure an after-hours AI chatbot to acknowledge receipt, collect query type and contact details, and set a resolution expectation — keeping the 24-hour session window active. If the session expires before an agent responds, only approved templates can be sent.
Yes — India is the world’s largest WhatsApp market with 535 million users. WABA is widely adopted across NBFC, D2C, real estate, healthcare, and government verticals in India.
Yes, with consent. Outbound marketing messages require: explicit opt-in from each recipient, an approved marketing HSM template, and an opt-out mechanism in every message. When executed correctly — as Deltin demonstrated — WhatsApp marketing campaigns outperform email on every engagement metric.
