Start here
A Service message is a reply, not a synonym for every WhatsApp message
On the WhatsApp Business Platform, a customer message opens or resets a rolling 24-hour customer service window. During that window, a business may send a free-form response through WAB2C or another official API integration. Under the October 1, 2026 Pakistan model, each eligible outbound response delivered in that context is a Service message.
1
Customer starts
An inbound message opens or resets the 24-hour window.
24h
Business responds
Free-form support, order help or follow-up is permitted.
Delivered
Message is counted
The outbound delivery event—not a read tick—is the unit.
Outside the active window, an approved message template is required to start the conversation. That message is classified by its purpose—Marketing, Utility or Authentication—rather than as a Service message.
Meta rulebook
Four rules to teach every operator
The customer controls the clock
Each new customer message restarts the rolling 24-hour window. A business cannot extend it by sending itself another reply.
Inbound does not use the allowance
The customer's trigger opens the journey. Eligible outbound Service messages delivered by the business use the allowance.
Consent and policy still apply
Use only approved use cases, respect opt-outs, protect customer data and avoid misleading or prohibited content.
Automation needs an exit
A bot may assist inside the window, but customers must have a clear route to a human or another support channel.
Do not optimize by hiding support. Reducing unnecessary messages is good; making it hard to reach a human is not. Policy quality and customer outcome come first.
Count the event
What uses the Service allowance—and what does not
A practical rule: count deliveries, not keystrokes, words or read ticks. That is why a concise, structured response is both easier for the customer and more efficient for the monthly allowance.
Route before device
API, mobile phone, Desktop App and WhatsApp Web
The screen used by an operator does not always reveal the billing route. What matters is whether the outbound message was delivered through the WhatsApp Business Platform/API or through the standalone WhatsApp Business App channel.
WAB2C / Business Platform API
A delivered free-form business reply inside the active 24-hour window is an eligible Service message. It uses the monthly allowance until the allowance is exhausted.
WhatsApp Business App on mobile
A message sent through the standalone Business App is on the app channel, not automatically an API Service message. Business App terms and limits still apply.
WhatsApp Web or Desktop
These are paired surfaces of the Business App. The device is not the billing test—the sending route is. In Coexistence, confirm the route in WAB2C/provider reporting.
In a Coexistence setup, mobile and API activity can appear around the same customer journey. Use WAB2C and provider delivery reporting as the operational evidence; do not estimate consumption from the visible device alone.
Allowance, not unlimited access
What “free Service message” actually means
1,000
eligible Service messages per registered number, per calendar month
It is not a bundle of all WhatsApp categories, not a promise of unlimited automation, not transferable between phone numbers and not carried into the next month. The customer is not charged; the rule concerns the business account's messaging bill.
Think of the allowance as the first layer of a monthly meter. At 600 eligible deliveries, 400 remain. At 1,000, the free balance is zero. At 1,250, the first 1,000 are within the allowance and 250 are billable Service messages.
Visible control
The WAB2C top-bar counter
WAB2C places the remaining Service message counter in the top bar so an owner, administrator or team lead can see the monthly balance without opening a spreadsheet. It turns an invisible cost event into an everyday operating signal.
Illustrative counter
742 messages left
Use the WAB2C counter for daily decisions and the provider's delivery records for billing reconciliation. Small differences can occur because delivery status, timing, route or account reporting may settle at different times.
The meter continues
What happens after the Service messages are over
Reaching 1,000 does not normally switch customer support off. The next eligible Service delivery becomes billable at the configured route's Service rate. For Pakistan, WAB2C's partner BSP route is currently Rs. 5 per delivered Service message; Meta-direct uses the actual Meta charge to the customer's card, with the current reference rate listed as US$0.015 before card conversion and bank charges.
600 delivered
400 left
Within allowance
1,000 delivered
0 left
Allowance reached
1,250 delivered
250 billable
Rs. 1250 on the current BSP Service rate
Delivery may be affected when Meta card billing, provider credit or account payment setup is not valid. Review the current WAB2C pricing page and provider terms before launch; rates and platform rules can change.
Protect the allowance
How to prevent early exhaustion
Compose before sending
Put the answer, status, next action and escalation option in one useful response instead of four fragments.
Route before replying
Send the conversation to the right sales, support or operations owner so multiple teams do not duplicate the answer.
Stop retry loops
Set retry limits, idempotency checks and delivery-state conditions. A broken loop can consume allowance without improving service.
Use structured inputs
Collect order ID, branch, issue type and preferred action in a Flow Form rather than asking one question at a time.
Set operating thresholds
Review at 70%, investigate at 90% and switch to only essential replies at 100% unless billable volume is approved.
Protect quality
Do not use optimization to avoid customer care. Resolve the issue clearly and provide a human escalation path.
Message strategy
Replace fragments with one decision-ready response
Fragmented · up to 6 messages
- 1. “Hello.”
- 2. “Please share your order number.”
- 3. “Thank you.”
- 4. “Your order has shipped.”
- 5. “Delivery is expected tomorrow.”
- 6. “Reply if you need help.”
Optimized · 1 message
Expected delivery: tomorrow.
Track: [secure link]
Need help? Choose an option below or ask for an agent.
One complete reply gives context, next action and escalation without making the customer decode a sequence of bubbles.
New WAB2C automation
Trigger → Flow Form → Google Sheet
WAB2C can turn a conversational request into structured data with one outbound Service message. The design is simple: the customer starts the journey, WAB2C sends one interactive form, and the completed form is written to Google Sheets without another WhatsApp reply.
1. Trigger
Customer message, keyword, QR entry or supported business event starts the journey.
Inbound · 0 outbound
2. Flow Form
One interactive message collects order ID, issue, location and the next required action.
1 outbound Service message
3. Google Sheet
WAB2C creates or updates the row for the team, report or downstream workflow.
Backend action · 0
Maximum one outbound message—when configured as this exact path
The result assumes the trigger and form submission are customer-originated, the sheet write is a backend action, and no extra confirmation, retry, validation bubble, template or follow-up is enabled. Add any of those and the message count can increase.
This approach is useful for order-status requests, service bookings, warranty intake, dealer enquiries, COD confirmation, lead qualification and support triage. WAB2C's automation team can help map the fields, build the Flow, connect the sheet, define routing and test the delivery path before it reaches customers.
Run it every month
A practical operating plan
The operational objective
Do not chase the lowest message count at any cost. Chase the lowest number of messages required to give the customer a complete, accurate and actionable resolution.
Fast answers
Frequently asked questions
Are the first 1,000 WhatsApp messages of every type free?
No. The allowance applies to eligible Service messages for each registered Business Platform phone number. Marketing, Utility and Authentication are separate categories and remain subject to their applicable rates.
Does the customer's first message consume the allowance?
No. A customer's inbound message starts or resets the 24-hour service window. The eligible outbound Service message delivered by the business is the metered unit.
Does one long reply cost more than several short bubbles?
The message count is based on delivered message events, not word count. One clear, structured reply normally uses one message, while six separate bubbles can use six.
Do mobile, WhatsApp Web and the Desktop App use the API allowance?
Messages sent through the standalone WhatsApp Business App and its paired Web or Desktop surfaces follow the Business App channel. Messages delivered through WAB2C or another Business Platform integration follow the API channel. In a Coexistence setup, verify the sending route in WAB2C reporting rather than guessing from the screen used by the operator.
Do messages stop when the free allowance reaches zero?
Not automatically. Eligible Service messages above the allowance become billable at the configured Meta-direct or BSP Service rate when billing is active. Delivery can be affected if the account has no valid payment or provider credit arrangement.
Does unused allowance roll into the next month or pool across numbers?
No. The allowance resets each calendar month, is assigned per registered phone number and does not roll over or pool across business numbers.
Can automation reply without offering a human?
Automation is permitted inside the service window, but the WhatsApp Business Messaging Policy requires clear escalation paths. Useful options include transfer to a human agent, phone, email, web support or a support form.
Is the WAB2C top-bar number the final invoice?
No. It is an operational counter that helps teams manage the allowance. Provider delivery records and the applicable Meta or BSP invoice remain the billing authority.
Official references
Sources and scope notes
- WhatsApp Business Messaging Policy — consent, 24-hour window, automation and escalation requirements.
- WhatsApp Service Messages — official Service-message use cases.
- WhatsApp Business Platform Pricing — categories, delivery-based charging and market rate structure.
- Meta developer pricing documentation — current rate cards and implementation detail.
- WAB2C Pakistan pricing — current partner BSP and Meta-direct route display.
Meta and provider documentation can update at different times. The current official Meta rate card, the configured provider route and the customer's written commercial terms control billing. This guide explains the October 2026 operating model and is not a substitute for account-specific billing records.