AppMatic Tech integrates the WhatsApp Business Platform Cloud API into SaaS, ERP, and procurement systems built with Laravel, React, and Next.js, including a vendor bidding platform for an Indian pharmaceutical manufacturer with over ₹1,000 crore in annual revenue. AppMatic Tech is based in Ahmedabad, India, with 330+ products shipped since 2017.
In India, the Gulf, Latin America, and much of Africa and Europe, WhatsApp is where vendors, customers, and site teams actually answer. An email asking a supplier to submit a bid waits in an inbox; a WhatsApp message with a link gets opened. That makes the WhatsApp Business API one of the highest-return integrations a business system can add. It is also an integration with strict rules: approved templates, a 24-hour reply window, messaging limits, and a pricing model Meta changed again on October 1, 2026. This guide covers the architecture AppMatic Tech uses and the rules that shape it.
Key takeaways
A WhatsApp integration is a messaging system with rules, not just an API call.
| Point | Detail |
|---|---|
| One official API | Meta's Cloud API, after the On-Premises API ended in October 2025 |
| Templates outside the window | Business-initiated messages need approved templates and user opt-in. |
| 24-hour window | Free-form replies are allowed only for 24 hours after the user's last message. |
| Per-message pricing | Charged per delivered message by category and country since July 1, 2025 |
| October 2026 change | Service messages beyond 1,000 a month, and utility messages in the window, are now charged. |
| Limits start at 250 | Unique users per 24 hours outside the window, shared across the business portfolio |
What can a business system do with the WhatsApp Business API?
The WhatsApp Business API lets software send and receive WhatsApp messages programmatically from a business phone number. Common integrations:
| Use case | Message type | Example |
|---|---|---|
| Vendor and procurement workflows | Utility templates | New enquiry alerts, bid deadline reminders, selection outcomes |
| Order and delivery updates | Utility templates | Order confirmed, out for delivery, delivered |
| Appointment reminders | Utility templates | Clinic or service visit reminders with a reschedule link |
| Sign-in codes | Authentication templates | One-time passwords for login or payment confirmation |
| Customer support | Service messages | Replies inside the 24-hour window, handed between a bot and an agent |
| Promotions | Marketing templates | Offers and re-engagement, only to opted-in users |
| Field reporting | Inbound messages | Site teams send photos that the system files against the right project |
Field reporting is a special case. WhatsApp groups are poor record systems, as explained in why construction teams lose site photos in WhatsApp groups. Routing WhatsApp messages into a structured system fixes the record problem while keeping the channel people already use.
How do templates and the 24-hour window work?
Two rules govern every WhatsApp integration.
- The customer service window
- A 24-hour timer starts when a user messages or calls the business, and each new user message resets the timer. Inside the window, the business can send free-form messages, called service messages.
- Template messages
- Outside the window, a business can send only pre-approved template messages, and only to users who have opted in. Templates belong to one of three categories: marketing, utility, or authentication.
- Free entry point window
- When a user starts a conversation from a Click to WhatsApp ad, a free entry point window opens for up to 7 days, during which marketing, utility, authentication, and service messages are free.
Template design is an engineering task, not only a copywriting one. Each template has fixed text with numbered variables, and the system must fill those variables from its own data, track approval status, and stop sending if Meta pauses a template for low quality.
How does WhatsApp Business API pricing work after October 2026?
Meta moved from per-conversation pricing to per-message pricing on July 1, 2025. Only delivered messages from the business are charged; messages from users to businesses are free.
| Message type | When it can be sent | Charge from October 1, 2026 |
|---|---|---|
| Marketing template | Any time, to opted-in users | Charged per delivered message, by recipient country |
| Utility template | Any time, to opted-in users | Charged, including inside the customer service window |
| Authentication template | Any time, to opted-in users | Charged per delivered message, by recipient country |
| Service message | Only inside the customer service window | First 1,000 per month per business phone number free; charged after that |
| Any message in a free entry point window | Up to 7 days after a Click to WhatsApp ad conversation starts | Free |
Three details matter for budgeting:
- Utility in the window is no longer free. From July 1, 2025 to September 30, 2026, utility templates sent inside an open window were free. Since October 1, 2026, they are charged.
- Volume tiers apply to utility and authentication. Rates fall as monthly volume rises, tracked per market and category, and reset monthly.
- Payment method required. Businesses without a payment method on file may find service messages stop delivering once the free tier is used. Eligible government and non-profit organisations remain exempt through December 31, 2027.
Rates differ by country and change periodically, so AppMatic Tech reads them from Meta's current rate cards at build time rather than hard-coding them.
What are the WhatsApp messaging limits?
Messaging limits cap how many unique WhatsApp users a business can message outside a customer service window in a moving 24-hour period. The limit is set at the business portfolio level and shared by every phone number in the portfolio.
| Tier | Unique users per 24 hours | How to reach it |
|---|---|---|
| Starting tier | 250 | Default for new portfolios |
| Tier 2 | 2,000 | Business verification, partner verification, or 2,000 delivered messages to unique users in 30 days with high-quality templates |
| Tier 3 | 10,000 | Automatic, with high-quality messaging and at least half the current limit used in the last 7 days |
| Tier 4 | 100,000 | Automatic, under the same conditions |
| Unlimited | No cap | Automatic, under the same conditions |
Automatic increases apply within 6 hours once the conditions are met. The limits shape launch plans: a system that needs to notify 5,000 vendors on day one needs business verification and a ramp, not just working code.
Should a business integrate directly or use a Business Solution Provider?
| Factor | Direct Cloud API integration | Business Solution Provider (BSP) |
|---|---|---|
| Best for | WhatsApp inside a company's own software | Marketing and support teams needing a ready tool |
| Data | Messages and statuses stored in the company's own database | Stored in the provider's platform, synced by API |
| Workflow | Fully custom, tied to ERP, CRM, or procurement logic | Provider's inbox, campaign, and bot builders |
| Cost | Meta's message charges plus engineering | Meta's charges plus the provider's fees |
| Time to start | Weeks of engineering | Days of configuration |
Meta ended the On-Premises API in October 2025, so new integrations use the Cloud API either directly or through a provider. AppMatic Tech integrates the Cloud API directly when WhatsApp is part of a system's core workflow, such as procurement, and recommends a provider when a marketing team mainly needs a shared inbox.
What does a production WhatsApp integration architecture look like?
AppMatic Tech builds WhatsApp integrations with eight components:
- Account setup. A Meta app, a WhatsApp Business Account, a verified business, and a registered phone number.
- Template registry. Templates stored in the application with their category, language, variables, and Meta approval status, synced by API.
- Opt-in ledger. A record of when and how each user opted in, checked before every business-initiated message.
- Window tracker. The time of each user's last inbound message, so the system knows whether a free-form reply is allowed or a template is required.
- Outbound queue. Messages sent through a queue that respects messaging limits and retries transient failures without duplicates.
- Webhook receiver. Inbound messages and delivery statuses (sent, delivered, read, failed) received on a verified endpoint, acknowledged fast, and processed asynchronously.
- Status reconciliation. Delivery and read statuses written back to the business record, such as marking a vendor as notified.
- Fallback channels. Email or SMS for users who are not on WhatsApp or whose messages fail.
Pro tip: Store the template category with every sent message. When Meta's invoice arrives, the system can reconcile costs per workflow, and misclassified templates, such as a marketing message submitted as utility, show up before Meta reclassifies them.
How can a business control WhatsApp messaging costs?
The October 2026 changes make cost design part of the architecture:
- Digest instead of drip. Combine several updates into one utility message where the workflow allows.
- Use push notifications for low-value alerts. If the user has the company's app, routine updates can go there.
- Answer within the window. Replies to a user's question are service messages, which are cheaper than templates and free within the monthly tier.
- Pick the right category. Utility and authentication templates cost less than marketing in most markets, but must genuinely match the category.
- Track cost per workflow. Budget alerts per workflow catch a misfiring reminder loop before the invoice does.
How AppMatic Tech builds WhatsApp integrations
AppMatic Tech has shipped 330+ products since 2017, holds a 5.0 Clutch rating, and keeps an 83% client retention rate. For an Indian pharmaceutical manufacturer with over ₹1,000 crore in annual revenue, AppMatic Tech built a vendor and enquiry management platform on React, Next.js, and Laravel, with the WhatsApp Business API notifying vendors of new enquiries, bid deadlines, and selection outcomes, replacing scattered WhatsApp chains with an auditable bidding workflow.
Related guides: AI in pharma regulatory operations and enterprise procurement SaaS architecture. The service is described on the custom software development page. Scoping starts at contact@appmatictech.com or the contact page.
Sources
| Claim used in this article | Source |
|---|---|
| Per-message pricing, categories, free tiers, October 1, 2026 changes, free entry point window, volume tiers, customer service window | Meta for Developers, WhatsApp pricing |
| Messaging limits, tiers, verification route, automatic scaling | Meta for Developers, WhatsApp messaging limits |
| On-Premises API end in October 2025 | Unipile, WhatsApp Cloud API integration |
| Pharma vendor platform and WhatsApp notification layer | AppMatic Tech, pharma vendor and enquiry management case study |
Frequently Asked Questions
- How does WhatsApp Business API pricing work in 2026?
- Since July 1, 2025, Meta charges per delivered message rather than per conversation. Marketing, utility, and authentication template messages are charged by category and the recipient's country. Each business phone number gets 1,000 free service messages per month, and from October 1, 2026, service messages beyond that tier and utility messages inside the customer service window are charged.
- What is the 24-hour customer service window on WhatsApp?
- The customer service window is a 24-hour period that starts when a user messages or calls a business, and every new user message resets the timer. Inside the window, a business can send free-form non-template messages. Outside the window, a business can send only pre-approved template messages, and only to users who have opted in.
- What are WhatsApp Business API messaging limits?
- Messaging limits cap how many unique WhatsApp users a business can message outside a customer service window in a moving 24-hour period. Limits are shared across the business portfolio, start at 250, and rise to 2,000, 10,000, 100,000, and unlimited. Business verification is one route to 2,000, and higher tiers unlock automatically with high-quality messaging.
- Should a business use the Cloud API directly or a Business Solution Provider?
- A business that needs WhatsApp inside the company's own software, with custom workflows and data in the company's own database, usually integrates Meta's Cloud API directly or through a technology partner. A Business Solution Provider adds a ready inbox, campaign tools, and support, which suits marketing teams. AppMatic Tech builds direct Cloud API integrations for SaaS, ERP, and procurement systems.
- Has AppMatic Tech built a WhatsApp Business API integration?
- Yes. AppMatic Tech built a vendor and enquiry management platform for an Indian pharmaceutical manufacturer with over ₹1,000 crore in annual revenue, using React, Next.js, Laravel, and the WhatsApp Business API. The WhatsApp layer notifies vendors of new enquiries, bid deadlines, and selection outcomes on the channel vendors already use for business communication.