WhatsApp per-message pricing is the billing model that now governs almost every business message you send on the platform, and it works very differently from the conversation-based system it replaced. Instead of paying one fee to open a 24-hour window with a customer, you pay for each template message individually, priced by its category. That single change reshapes how marketing teams budget, how they design flows, and how they decide what to send at all.
This guide explains the shift in plain terms. We will cover why the model changed, what the template categories are, how marketing, utility, and authentication messages are priced differently, why service messages inside the customer-care window stay free, and how to build a realistic cost estimate for your own account. We will also walk through the optimizations that actually move your bill and the ones that do not.
One honest note before we start: WhatsApp pricing belongs to Meta, not to any messaging platform layered on top of it. The rates vary by country and by message category, and they change over time. We describe the structure of the model here, but we will not invent specific per-message rates, because they differ everywhere and go stale quickly. For the live numbers you need to plan a budget, always check Meta's WhatsApp pricing page. No third-party tool, KlyoChat included, sets or marks up these fees.
What actually changed in WhatsApp's per-message pricing?
For years, WhatsApp billed businesses by the conversation. When you sent a message or a customer messaged you, Meta opened a 24-hour conversation window and charged a single fee for it, regardless of how many individual messages passed back and forth inside that window. Conversations were bucketed into four types — marketing, utility, authentication, and service — and each type had its own conversation rate. If you sent five messages inside one window, you paid once.
Per-message pricing removes the conversation as the unit of billing. Now the thing you pay for is the template message itself. Each business-initiated template you send is priced according to its category, and the old idea of a 24-hour window as a billing container is gone for those messages. The window still exists as a concept for what you are allowed to send, but it is no longer the meter. The meter is the individual template.
The practical effect is that volume and message design matter more than they used to. Under conversation pricing, a chatty flow that sent several messages inside one window cost the same as a single message. Under per-message pricing, each of those templates can carry its own charge. That rewards tighter, more deliberate messaging and penalizes padding a flow with extra sends that a customer did not need.
The one big exception, and it is a genuinely good one for support teams, is that service messages exchanged inside the customer-care window remain free. When a customer messages you first and you reply within the open window using regular free-form messages rather than templates, you are not billed per message for those. We will unpack exactly how that window works later, because it is where most of the real savings live.
| Aspect | Old conversation model | Per-message model |
|---|---|---|
| Billing unit | One 24-hour conversation window | Each template message sent |
| Messages per charge | Many messages, one fee | One message, one fee |
| Categories | Marketing, utility, authentication, service | Marketing, utility, authentication (service is free in-window) |
| What drives cost | Number of windows opened | Number and category of templates sent |
| Free component | Some free service conversations | Service replies inside the customer-care window |
The window did not disappear — the billing unit did
You will still hear people talk about the 24-hour window, and it still governs what you can send without a template. What changed is that the window is no longer what Meta charges you for. The charge now attaches to each template message and its category. Keep those two ideas separate and the model gets much easier to reason about.
Why did WhatsApp move from per-conversation to per-message billing?
Meta has framed the shift as a move toward a simpler, more predictable unit of measurement. Conversation pricing was elegant in theory but confusing in practice. Businesses struggled to predict how many conversation windows a campaign would open, because a window could be triggered by a customer reply, by a template send, or by the timing of when messages landed. Two campaigns that sent the same number of messages could open very different numbers of billable conversations depending on customer behavior.
Per-message pricing trades that ambiguity for a directly countable unit. You know exactly how many marketing templates you sent, how many utility templates, and how many authentication templates, because you scheduled and triggered every one of them. Multiply each count by its category rate and you have your bill. For finance teams that need to forecast, a countable send is easier to model than an unpredictable window.
There is also a policy dimension. Conversation pricing arguably under-charged high-volume marketing blasts, because a business could pack a lot of promotional content into a single window at a single fee. Per-message pricing prices each promotional template on its own, which nudges businesses toward sending fewer, more relevant marketing messages rather than maximizing what they cram into one paid window. Whether you view that as fairer pricing or as a way to raise revenue on marketing depends on your vantage point, but the incentive it creates is clear.
For businesses, the takeaway is not to judge whether the change is good or bad in the abstract. It is to understand that your cost now scales with the count and category of what you send. That means the discipline of message design — sending the right message, in the right category, only when it earns its place — is now a direct lever on your invoice, not just on your engagement rates.
Same campaign, two billing models
- Conversation model
- Send 3 marketing templates in one 24h window = one marketing conversation fee
- Per-message model
- Send 3 marketing templates = three marketing message fees
What are the WhatsApp template message categories?
Every business-initiated template message on WhatsApp is assigned a category, and the category determines both how the message is treated and how it is priced. There are three billable categories under per-message pricing — marketing, utility, and authentication — plus service messages, which are handled separately and are free inside the customer-care window. Getting the category right is the single most important pricing decision you make, because the same content in the wrong category can cost more or get rejected.
Categories are not a suggestion box. When you submit a template for approval, you choose a category, and Meta reviews the content against that category's definition. If your template's content does not match the category you claimed — for example, a promotional message submitted as utility — Meta can re-categorize it or reject it. Mislabeling to save money does not work and risks your template being disabled.
Here is the structure at a glance. Note that we are describing what each category is for, not quoting a rate, because the actual per-message price differs by country and changes over time. The relative ordering — marketing typically being the most expensive and utility and authentication generally lower — holds broadly, but you must confirm the live figures for your markets on Meta's pricing documentation.
- Marketing is anything promotional or designed to drive awareness, engagement, or sales.
- Utility must relate to a specific transaction or account event the customer already has with you.
- Authentication is narrowly for verifying identity — codes and login confirmations, not marketing dressed up as a code.
- Service is not a template category you send proactively; it is your free-form reply to an inbound message inside the care window.
| Category | What it is for | Typical relative cost |
|---|---|---|
| Marketing | Promotions, offers, product news, re-engagement, cart nudges | Highest of the three |
| Utility | Order updates, receipts, appointment reminders tied to a transaction | Lower than marketing |
| Authentication | One-time passcodes and login verification | Often lowest; varies widely by country |
| Service | Free-form replies to a customer inside the open care window | Free inside the 24h window |
Category mismatch is a real risk, not a loophole
Submitting a marketing message as utility to pay a lower rate does not work and can get the template rejected or re-categorized. Meta reviews content against the category you declare. Choose the category that honestly matches the message, then optimize within the rules — not by mislabeling.
How does marketing template pricing work?
Marketing templates are the promotional workhorses of WhatsApp: new-product announcements, seasonal offers, abandoned-cart nudges, win-back campaigns, and any message whose purpose is to drive awareness, consideration, or a sale. Because they are business-initiated and promotional, they sit at the top of the pricing structure. Under per-message billing, every marketing template you send is a billable event, so the cost of a marketing blast scales linearly with your recipient count.
This is the category where the shift from conversation to per-message pricing bites hardest. Previously, a marketing conversation window could absorb several promotional messages at one fee. Now each marketing template is priced on its own. If your flow sends a promo, then a follow-up, then a last-chance reminder as three separate templates, that is three marketing charges per recipient, not one. Multiplied across a large list, the difference is significant.
The discipline that follows is straightforward: send marketing templates that earn their cost. That means tighter segmentation so you are not paying to reach people who will not convert, fewer redundant sends in a sequence, and a bias toward quality over frequency. A well-targeted marketing message to an engaged segment can be very profitable even at the highest per-message rate. A spray-and-pray blast to a cold list is where per-message pricing quietly drains a budget.
It is also worth remembering that marketing messages depend on the customer having opted in, and on your account's messaging limits and quality rating. If your quality drops because recipients block or report your marketing, your ability to send can be throttled. So the incentive under per-message pricing aligns with good practice anyway: relevant, wanted marketing is both cheaper in aggregate and safer for your account health. For how those send limits and quality tiers interact, see our companion piece on WhatsApp message limits and tiers.
A three-step marketing sequence to 10,000 recipients
- Step 1: launch announcement
- 10,000 marketing templates billed
- Step 2: 48h follow-up
- 10,000 more marketing templates billed
- Step 3: last-chance nudge
- 10,000 more marketing templates billed
- Total marketing sends
- 30,000 billable messages — segment hard before you press send
How does utility template pricing work?
Utility templates carry transactional information the customer expects: order confirmations, shipping updates, delivery notifications, appointment reminders, payment receipts, and account alerts. The defining test is that a utility message relates to a specific transaction or event the customer already has with you. It is not promotional, and it is not a cold outreach — it is the digital equivalent of a receipt or a status update.
Because utility messages are tied to something the customer actively wants to know, they are generally priced lower than marketing. That reflects both their value to the recipient and Meta's intent to keep genuinely useful transactional messaging affordable. For businesses with high transaction volumes — e-commerce order flows, logistics updates, booking confirmations — utility templates are often the largest share of message volume but a smaller share of cost per message than marketing.
The category boundary is where teams get into trouble. A shipping-update template that says your order is on the way is clearly utility. The same template with and by the way, here is 10 percent off your next order tacked on becomes promotional, and Meta may treat it as marketing. Keeping utility templates strictly transactional preserves the lower rate and the higher approval likelihood. If you want to cross-sell, do it in a separate, honestly-categorized marketing message rather than smuggling it into a utility one.
There is a timing nuance worth knowing. A utility template sent to a customer while you already have an open customer-care window with them can, in some configurations, be treated differently than one sent cold. The interaction between the free service window and paid utility templates is exactly the kind of detail that varies and gets updated, so confirm the current behavior for your markets in Meta's documentation before you build a flow that depends on it.
Keep utility templates strictly transactional
The fastest way to raise your WhatsApp bill by accident is to bolt a promotion onto a utility message. That can push the template into the marketing category, costing more and risking rejection. Keep receipts and updates clean, and put offers in a separate marketing send where they belong.
What is authentication template pricing?
Authentication templates exist for one narrow purpose: verifying a user's identity. The classic case is the one-time passcode you receive when logging into an account, resetting a password, or confirming a transaction. These templates are tightly constrained in format — they are meant to deliver a code and little else — and that narrowness is deliberate. Authentication is a high-trust, high-frequency message type, and WhatsApp treats it as its own category with its own pricing.
Authentication pricing is where country-level variation is most dramatic. Because one-time passcodes are sent in enormous volumes across very different telecom markets, Meta prices authentication with significant regional differences, and there have been market-specific rates and adjustments over time. In some countries authentication is among the cheapest message types; in others it is priced to reflect local carrier and fraud dynamics. This is the category where you most need to check the current rate for each specific country you send to rather than assuming a global number.
For product and growth teams, authentication cost is usually a function of how your login and verification flows are built. If every session requires a fresh code, your volume is high; if you use longer-lived sessions or fall back to other verification channels where appropriate, you send fewer. The per-message model makes each of those codes a line item, so authentication volume that was invisible under a bundled plan becomes a visible, optimizable cost.
One caution: authentication templates must actually be authentication. Using the authentication category to send anything that is not a genuine verification code — a promotion styled as a code, for example — violates the category rules and puts your templates at risk. As with the other categories, the honest label is also the safe one.
Authentication rates swing hardest by country
Of the three categories, authentication shows the widest country-to-country price variation, and Meta has adjusted it market by market over time. If one-time passcodes are a big part of your volume, price them per country from Meta's current documentation rather than trusting any single global figure.
Are service messages really free now?
Yes, with an important qualifier: service messages are free when they are free-form replies exchanged inside an open customer-care window. This is the part of the pricing change that genuinely benefits support-heavy businesses. When a customer messages you first, they open a 24-hour customer-care window, and within that window you can reply with normal, free-form messages — no template required — and those replies are not billed per message.
The qualifier matters because service being free does not mean all inbound-driven messaging is free. If you need to reply to a customer after their window has closed, you generally must use a template to reopen contact, and that template is billed according to its category. Likewise, if you proactively start a conversation, that is a business-initiated template and it is billed. Free service messaging is specifically the free-form back-and-forth that happens while the customer's window is open.
For a business that does a lot of reactive support — answering questions, resolving issues, handling inbound requests — this is a meaningful cost advantage. A support team that lives inside customer-initiated windows can handle enormous message volume at no per-message charge, paying only when it needs to reach back out with a template after a window closes. That is a very different economics profile from a marketing-led account that pays for every proactive send.
The strategic implication is to make it easy and attractive for customers to message you first, and to resolve issues within the open window rather than letting it lapse and needing a paid template to re-engage. Fast, complete first responses are not just good service; under this model they are also the cheapest form of WhatsApp messaging you have. A unified inbox that surfaces open windows and their remaining time helps teams stay inside the free zone, which is one of the practical reasons businesses adopt tools like the KlyoChat unified inbox for WhatsApp.
When a reply is free versus billed
- Customer messages first, you reply in 3 hours
- Free — inside the open care window
- Customer messages, you reply the next morning within 24h
- Free — still inside the window
- You reply 30 hours later, window closed
- Billed — you must send a template to reopen contact
- You proactively start a marketing conversation
- Billed — business-initiated marketing template
How does the customer-care window actually work?
The customer-care window is a 24-hour period that opens whenever a customer sends you a message. During that window, you can respond freely with regular messages — text, media, quick replies — without using a pre-approved template and without a per-message charge for those service replies. Each new inbound message from the customer refreshes the clock, so an active back-and-forth conversation keeps the window open and free.
When the window closes — 24 hours after the customer's last message with no new inbound — you can no longer send free-form messages. To reach that customer again, you send an approved template, and that template is billed by its category. This is the mechanic that ties the free service benefit to responsiveness: the value of the free window is only captured if you actually reply while it is open.
This creates a clear operational goal for support teams. The metric to watch is not just first response time for its own sake, but whether you are resolving conversations inside the window. A team that consistently closes issues within 24 hours captures the free-messaging benefit fully. A team that lets windows lapse and then reopens them with templates is paying for contact it could have had for free with faster handling.
It also shapes how you think about escalation and follow-up. If a customer issue genuinely needs a next-day follow-up after the window closes, budget for the template that reopens it — that is a legitimate cost. What you want to avoid is losing the window to slow handling and then paying to recover a conversation that never needed to lapse. Staffing, routing, and automation that keep first responses fast are, in effect, cost-control measures under per-message pricing.
Treat the open window as your cheapest channel
Every issue you fully resolve inside a customer's 24-hour window is handled at zero per-message cost. The moment a window lapses, re-engaging costs a template. Fast, complete first responses are not only good service — under per-message pricing they are the single biggest free lever you have.
Did conversation-based pricing really end?
For most practical purposes, yes — the conversation as the billing unit has been retired in favor of per-message pricing, and businesses should plan their budgets around the per-message model. The phrase you will see in industry coverage is the end of conversation-based pricing, and it refers exactly to this: Meta stopped charging by the 24-hour conversation window and started charging by the individual template message.
That said, transitions like this are rarely instantaneous or globally uniform. Rollouts can differ by region, by account type, and by timeline, and Meta publishes the authoritative status on its own documentation. If you are reading legacy invoices or older guides, you may still see conversation-based language, and some accounts may have transitioned at different times. The direction of travel is unambiguous, but the exact date your account moved and the precise mechanics for your markets are things to confirm from the source — the WhatsApp Business Platform documentation — rather than assume.
The reason this matters for planning is that a lot of older cost advice — spreadsheets, calculators, blog posts — was built around counting conversations. If you inherited a WhatsApp budget model that estimates cost by projecting conversation windows, it is now measuring the wrong thing. You need to re-base your estimate on message counts by category. Re-using a conversation-era model against per-message reality will produce numbers that drift, usually understating cost for marketing-heavy accounts.
For the broader picture of how all these WhatsApp costs stack up beyond the pricing-model mechanics, our full WhatsApp Business API cost breakdown for 2026 covers the platform and provider fees that sit alongside Meta's per-message charges. This article focuses specifically on the pricing-model change and the categories; that one zooms out to the total cost of running WhatsApp at scale.
Retire your old conversation-based estimates
Any budget model that counts 24-hour conversation windows is now measuring the wrong unit. Rebuild it around message counts by category — marketing, utility, authentication — or it will quietly understate your cost, especially on marketing-heavy sends. Verify the current model on Meta's pricing page before you re-base.
How do you estimate your WhatsApp per-message cost?
Estimating cost under per-message pricing is more direct than it was under conversation pricing, because you are counting something you control: the number of templates you send, broken down by category and country. The exercise below takes about fifteen minutes with your campaign calendar and a copy of Meta's current rate table open in another tab. We will not give you rates here — those you pull live from Meta — but we will give you the method to plug them into.
- List your template types and categoriesWrite down every template you send — welcome, order confirmation, shipping update, promo, cart nudge, OTP — and label each with its true category: marketing, utility, or authentication.
- Estimate monthly volume per templateFor each template, project how many you will send per month. For marketing, that is roughly your list size times the number of campaign sends. For utility and authentication, it tracks your transaction and login volume.
- Split volume by destination countryBecause rates vary by country, break each template's volume down by the countries you send to. Authentication especially needs a per-country split, since its rates swing the most.
- Pull current rates from Meta and multiplyOpen Meta's WhatsApp pricing documentation, find the rate for each category and country, and multiply by your projected volume. Sum across all templates and countries for your monthly total.
- Subtract the free service window and add a bufferRemember that free-form replies inside open customer-care windows are not billed, so exclude that reactive support volume. Then add a 15–25 percent buffer for growth and re-engagement templates you did not plan.
Your estimate is only as current as Meta's rates
This method is stable, but the numbers you plug into it are not — Meta updates rates and occasionally the model itself. Rebuild your estimate whenever you plan a budget cycle, and treat any figure older than a quarter as a starting point to re-verify, not a fact.
How does per-message pricing vary by country?
Country is one of the two axes that determine your per-message cost — the other being category — and the variation is large. Meta prices messaging differently across markets to reflect local telecom economics, competition, fraud patterns, and the value of the market. A marketing message to one country can cost several times what the same message costs to another. This is why a single blended cost-per-message figure is almost meaningless for a business that sends internationally.
The implication for planning is that you cannot budget WhatsApp as a single line. You budget it as a matrix of category by country. A business sending mostly authentication codes to a low-cost market has a completely different cost profile from one sending mostly marketing to a high-cost market, even at identical message volumes. If your audience is concentrated in a few countries, price those specifically rather than using a global average that will mislead you in both directions.
Country variation also interacts with strategy. If a marketing campaign is marginal in a high-cost market, the per-message price might tip it from profitable to break-even, whereas the same campaign in a low-cost market is clearly worth running. Under per-message pricing, geography becomes a real input to campaign decisions, not just an operational detail. Teams that map cost-per-message against expected revenue-per-message by country make sharper choices about where to invest their sends.
As with everything in this model, the specific numbers are Meta's and they move. The stable advice is structural: always price by country, never assume a global rate, and re-check the markets that carry most of your volume each planning cycle. For a sense of how these Meta fees combine with the subscription and provider costs of actually operating a WhatsApp account, our WhatsApp Business API cost breakdown puts the full stack together.
- Rates differ substantially between countries for the same category and message.
- Authentication shows the widest country-level variation of the three categories.
- A blended global cost-per-message hides real differences — budget by category and country.
- Concentrate your pricing research on the markets that carry most of your volume.
- Country cost can change whether a marginal campaign is worth running at all.
What common mistakes inflate your WhatsApp bill?
Most WhatsApp overspend is not caused by high rates — it is caused by avoidable habits that made sense under the old model or under no cost pressure at all. Because per-message pricing charges for each send, the mistakes that used to be free or cheap now show up directly on the invoice. Here are the ones that catch teams most often, all of which are fixable without cutting any messaging that actually earns its place.
The theme across all of them is that per-message pricing punishes waste that conversation pricing hid. A padded flow, a lapsed window, a mis-categorized template, an un-segmented blast — each of these was low-consequence when you paid by the window. Now each is a recurring charge. Auditing your existing flows against this list is usually the highest-return hour you can spend on WhatsApp cost.
- Padding flows with extra templates a customer did not need — each one is now a separate charge.
- Letting customer-care windows lapse through slow responses, then paying a template to re-engage.
- Blasting marketing to un-segmented or cold lists, so you pay to reach people who will not convert.
- Bolting promotions onto utility templates, pushing them into the pricier marketing category or getting them rejected.
- Sending redundant authentication codes because sessions expire too aggressively.
- Budgeting with a stale conversation-era model that undercounts marketing cost.
- Ignoring country mix and assuming one global rate, which distorts every projection.
The most expensive habit is the lapsed window
Slow first responses let free customer-care windows close, and then you pay a template to recover a conversation you could have kept for free. For support-led accounts, tightening response time is often a bigger cost win than trimming marketing sends.
How can you optimize WhatsApp per-message costs?
Optimization under per-message pricing is not about sending less for its own sake — it is about making sure every billed message earns its cost and that you capture the free service window fully. The tactics below are ordered roughly by return: the first few tend to move the bill most, and none of them require accepting worse marketing outcomes. Done well, they usually improve results and lower cost together, because the same discipline that reduces waste also raises relevance.
- Maximize the free customer-care windowRespond fast and resolve issues within the 24-hour window so reactive support stays free. Route inbound messages so no open window lapses through slow handling.
- Segment marketing hard before you sendEvery marketing template is billed, so send to engaged segments, not whole lists. Cutting a blast from your full list to your most responsive third can slash marketing cost while barely touching revenue.
- Trim redundant sends from sequencesAudit multi-step flows and remove any template that does not measurably lift results. Under per-message pricing, a three-step sequence costs three times a one-step one per recipient.
- Categorize honestly and keep utility cleanKeep utility templates strictly transactional to hold the lower rate and pass review. Put offers in dedicated marketing sends rather than inflating a utility message into a marketing one.
- Price by country and prioritize accordinglyMap cost-per-message against expected value per market. Lean into low-cost, high-return markets and set a higher relevance bar for sends into expensive ones.
- Prefer customer-initiated contact where you canMake it easy for customers to message you first — click-to-WhatsApp ads, website widgets, QR codes — so more conversations open a free window rather than requiring a paid outbound template.
Optimization and good marketing point the same way
Tighter segments, fewer redundant sends, cleaner categories, and faster support all lower your per-message cost and improve customer experience at the same time. Under this model, the cheapest WhatsApp program and the best one tend to be the same program.
Which platform controls these fees — and which does not?
This is the question that trips up a lot of buyers evaluating WhatsApp tools, so it is worth stating plainly: the per-message fees are set and billed by Meta, not by whatever software you use to send messages. Whether you send through the raw WhatsApp Business Platform, through a Business Solution Provider (BSP), or through a marketing tool layered on top, the underlying marketing, utility, and authentication charges are Meta's. A vendor cannot make marketing messages to a given country cheaper than Meta's rate for that country.
What vendors can differ on is everything around those fees: their own subscription price, whether they mark up or pass through Meta's charges, how they bill you, what analytics they give you to control volume, and how good their tooling is at helping you stay inside the free service window. Some providers add a per-message margin on top of Meta's rate; others pass the fee through at cost and charge only for their software. That distinction is one of the most important things to check when comparing platforms, because a low subscription price with a per-message markup can cost more at volume than a higher subscription with pass-through fees.
So when you read a headline WhatsApp price on any tool's marketing page, separate it into two parts: the software subscription, which the vendor controls, and the Meta message fees, which the vendor does not. The only way to compare tools fairly is to hold the Meta fees constant — they are the same underlying rates for everyone — and compare the subscriptions and the markup policies. For a worked example of how one popular tool structures its WhatsApp charges, see our breakdown of how ManyChat prices WhatsApp.
The reason we are emphatic about this is that it is easy for a vendor to blur the line and make WhatsApp look cheaper or more expensive than it is by bundling or hiding the Meta component. The honest framing — and the one that protects your budget — is that Meta's per-message fees are a pass-through reality for the whole industry. Verify them at the source, then evaluate software on the value it adds around them.
| Cost component | Who sets it | Can a vendor change it? |
|---|---|---|
| Marketing / utility / authentication per-message fee | Meta | No — same underlying rate for everyone |
| Free service messaging in the care window | Meta | No — free for everyone in-window |
| Software subscription | The vendor | Yes — this is where tools compete |
| Markup on Meta fees | The vendor | Yes — some mark up, some pass through at cost |
| Analytics and window tooling | The vendor | Yes — better tooling helps you spend less |
How does KlyoChat fit into WhatsApp per-message pricing?
Since we build KlyoChat, here is the honest version of where it sits in all this. KlyoChat is an AI-native unified inbox that includes WhatsApp alongside other channels, with broadcasts, automation, and analytics on top. On the specific question of per-message fees, our position is the one we have argued throughout this article: those fees are Meta's, they are billed by Meta or your BSP, and KlyoChat treats them as a pass-through. We do not mark them up and we do not control the rates, which vary by country and category — you verify those on Meta's page, not ours.
What KlyoChat adds is the software layer around the fees. The unified inbox surfaces open customer-care windows and how much time is left in them, which directly helps your team resolve issues inside the free window instead of letting it lapse into a paid template. Because the product knows the template categories and whether you are inside a window, it helps you avoid the exact mistakes — mis-categorized templates, unnecessary re-engagement — that inflate a per-message bill. Broadcasts and analytics let you segment before you send and measure what each category is costing you.
On subscription price, KlyoChat is flat and predictable: Basic is $19/month, Pro is $49/month ($39 billed yearly), and Business is $129/month, each with a 7-day free trial and no credit card required to start. That subscription is what you pay us; the WhatsApp message fees are separate and go to Meta or your provider at their rates. We think that separation is the honest way to price, because it means our software cost does not move when Meta changes a rate, and Meta's rate does not hide inside our subscription.
We will also be straight about the limits. KlyoChat does not offer native SMS or email, so if a big part of your plan needs those channels in the same tool, factor that in. We are a newer and smaller product than the biggest incumbents, with a smaller community and template library. And to be completely fair, the WhatsApp per-message economics we have described apply to us exactly as they apply to every other tool — no platform, ours included, can discount Meta's fees. What we can do is help you send fewer wasted messages and capture more free-window conversations. You can see how WhatsApp sits among our supported channels on the channels overview, and compare tiers on the pricing page.
| Layer | Who charges | How KlyoChat handles it |
|---|---|---|
| WhatsApp per-message fees | Meta / your BSP | Pass-through — no markup, rates set by Meta |
| Free care-window messaging | Meta | Inbox tracks open windows so you capture it |
| Software subscription | KlyoChat | Flat: $19 / $49 ($39 yearly) / $129, 7-day free trial |
| Segmentation and analytics | KlyoChat | Included — segment before you send, measure by category |
Honest scope: we help you spend Meta's fees well, not avoid them
KlyoChat cannot make WhatsApp's per-message fees cheaper — no platform can, because they are Meta's. What our unified inbox, category awareness, and window tracking do is help you waste fewer paid templates and keep more support inside the free window. That is where a good tool earns its subscription. Always verify current Meta rates on Meta's pricing page.
The short version of WhatsApp per-message pricing in 2026 is this: the billing unit moved from the 24-hour conversation to the individual template message, priced by category. Marketing sits at the top, utility below it, authentication varies most by country, and service messages inside an open customer-care window stay free. Your bill is now a direct function of how many templates you send, in which category, to which countries — which means message discipline is now budget discipline.
The practical playbook that follows is consistent and honest. Rebuild any conversation-era cost model around message counts by category and country. Capture the free service window by responding fast. Segment marketing hard, trim redundant sends, and keep every template in the category it truly belongs to. And separate the two parts of any WhatsApp price you are quoted: the software subscription, which vendors control, and Meta's per-message fees, which no vendor controls and which you should always verify at the source.
For the numbers themselves, go to Meta — they set the rates, they vary by country and category, and they change. For the wider cost picture around those fees, our WhatsApp Business API cost breakdown covers the full stack, how ManyChat prices WhatsApp shows one vendor's approach, and WhatsApp message limits and tiers explains how your send capacity scales. Understand the model, price it honestly, and design your messaging so every paid send is one you would gladly pay for.
