Pricing and strategy · Smerio

WhatsApp service message pricing 2026 vs RCS

Published 30 Sept 2026

What changes on October 1, 2026, what WhatsApp service replies cost, and when RCS conversation pricing can help businesses reduce channel dependence.

From October 1, 2026, WhatsApp Business Platform service replies become chargeable per delivered message after a monthly free allowance. For businesses handling long support exchanges, that makes RCS conversational pricing worth evaluating: an eligible exchange can bundle messages into one paid 24-hour conversation.

The opportunity is practical. A retailer resolving a return or an agency building a booking assistant needs room for questions, clarification and confirmation. When each additional reply has a delivery cost, conversation length becomes a budget variable.

RCS can offer a different cost structure and another way to reach customers. Whether it saves money depends on your market, the contracted billing model, customer reach and the work needed to complete the same task.

Pricing checked on September 30, 2026. October rates below take effect on October 1, based on Meta’s Messaging account timezone.

What changes in WhatsApp service message pricing?

A service message is a non-template reply within the customer service window. It can come from a human or a third-party assistant. Meta’s update also makes utility templates inside that window chargeable. Service rates match the market’s utility and authentication list rates, but service messages have no volume tiers. This differs from Meta Business Agent’s separate token-based pricing. Meta’s pricing update.

These rules concern the Business Platform/API. An open service window permits non-template replies but no longer makes every reply free. Meta’s qualifying free-entry-point exemption remains relevant. Reactions and eligible government/non-profit traffic have exceptions, and AI Providers have a separate policy. Check your applicable category before budgeting. Meta’s pricing rules and exceptions.

How much will WhatsApp service messages cost?

The recipient’s market and your billing currency determine the rate. Here are selected EUR service rates effective October 1, 2026, read from Meta’s published rate card:

The monthly examples apply one 1,000-message allowance, leaving 9,000 charged replies. They assume ordinary one-to-one service traffic in one market, with no other exemptions. These are Meta delivery charges only. Add your provider, software, AI, staffing and applicable tax costs separately. Source: Meta’s October 2026 rate cards, EUR download.

A Spain example: measure replies, not tickets

Imagine 2,000 support cases each requiring five delivered business replies. That is 10,000 service messages, even if your helpdesk reports only 2,000 conversations.

The Meta service charge is (10,000 − 1,000) × €0.0166 = €149.40, or €0.0747 per case. If each case requires ten replies, the same case volume produces €315.40, or €0.1577 per case.

Splitting a useful answer into several chat bubbles therefore affects the bill. Improve clarity and remove redundant acknowledgements, while preserving the questions and explanations customers need.

How the RCS 24-hour conversation window works

Under Google’s standard RCS billing model, a Conversational agent can generate a fixed-price conversation when either party replies within 24 hours. The billing window lasts 24 hours from that first reply and includes the message answered. Messages exchanged during it are grouped into the conversation.

For example, a customer asks about a return at 10:00 and the business replies at 10:05. The eligible window runs to 10:05 the following day. It does not keep extending with every reply.

There are limits: non-conversational agents remain billed per message. Messages outside a qualifying conversation may be charged separately. If several business messages precede a reply, only the last is included in the resulting conversation. Confirm your provider’s actual tariff and treatment of inbound events. Google’s standard billing FAQ.

US traffic uses a different trigger

Google’s US model requires four Rich or Rich Media messages, including at least one business-to-user message and two user responses, within 24 hours to trigger a session. The window begins with the first trigger message. Per-message and suggested-action charges can also matter. Use a US-specific quote for US traffic. Google’s US billing FAQ.

RCS vs WhatsApp: compare the completed conversation

For procurement, “price per message” is incomplete when one quote covers a message and another covers an exchange.

Consider the Spain workload above. Suppose an RCS supplier quotes €0.06 per qualifying conversation. This is an illustrative assumption, not a Smerio price or a market quote. If all 2,000 cases each fit one eligible conversation, delivery would cost €120, compared with €149.40 for five WhatsApp replies per case.

At two replies per case, WhatsApp’s example cost would be €49.80, below that €120 RCS assumption. At ten replies, it would be €315.40. Conversation depth changes the outcome.

For a first comparison, use:

WhatsApp service delivery = charged replies × market service rate. Apply the free allowance separately for each business phone number, and treat templates and exemptions separately.

RCS delivery = qualifying conversations × contracted conversation rate + separately charged events. Add fallback, setup and provider fees.

Then divide each channel’s total operating cost by successfully resolved cases. This catches a cheap route that creates more failed deliveries, repeat contacts or manual work. For mixed markets, calculate each market separately and respect how the number’s allowance is actually consumed.

Where conversational RCS can benefit a business

Start with workflows that naturally require dialogue:

• Returns and exchanges: identify the order, clarify the issue, agree on an option and confirm next steps.
• Appointments: offer available times, handle a preference and confirm the booking.
• Product selection: understand requirements and help the customer choose.
• Troubleshooting: ask diagnostic questions, explain a step and check the result.

These are candidates for a pilot, not promised savings. Compare equivalent outcomes and service quality. A single notification that rarely attracts a reply needs a different cost model.

Can RCS reduce WhatsApp vendor lock-in?

RCS is based on an industry specification maintained by the GSMA, with an interoperable messaging ecosystem. That gives businesses an additional route beyond a single app’s audience and commercial rules. GSMA Universal Profile.

Our recommendation is to make that choice usable in your architecture. Keep customer records, channel permissions, case history and business rules in systems you control. Separate those rules from provider-specific APIs. Require exports, documented webhooks and clear migration terms when choosing a supplier.

RCS still has dependencies: providers, carriers, supported devices and messaging apps, and approved business agents. Switching an API supplier does not automatically transfer a live sender or its reach. Ask who owns the agent, how migration works, what must be reapproved and how billing records can be exported.

Adding a channel reduces concentration only if customers can use it and your team can operate it. Keep WhatsApp where it serves customers well, while making suitable journeys available through RCS and other supported routes.

What to check before moving support traffic to RCS

1. Measure the existing workload. Count delivered business replies per resolved case, by market and number. Separate service replies from utility, marketing and authentication templates.
2. Confirm reachable customers. RCS support is specific to the recipient and agent. Use capability checks and confirm launch approval.
3. Request a complete quote. Include conversation triggers, inbound events, messages outside sessions, fixed charges and contract minimums.
4. Prepare another route. Design RCS and SMS fallback with its own content, cost and duplicate-prevention policy.
5. Pilot one journey. Compare resolution rate, customer effort, repeat contacts and total cost. Confirm customer permissions and opt-out handling for each channel.

For Spain, use Spain’s WhatsApp destination rate and an RCS quote for the actual Spanish routes and agent category. A global RCS headline price cannot establish your local business case.

Frequently asked questions

Are WhatsApp service messages still free in 2026?

Until September 30, ordinary service replies are free at Meta’s delivery layer. From October 1, the monthly 1,000-message allowance and applicable exceptions determine which remain free. Provider charges are separate.

Can a business exchange unlimited RCS messages within a 24-hour conversation?

Yes. With a sender configured as Conversational under the standard RCS billing model, a qualifying 24-hour conversation includes unlimited message exchanges without an additional delivery charge for each message. The business pays for the conversation, so asking another question, sharing details or confirming a resolution does not add another per-message delivery charge within that window.

That makes conversational RCS a strong fit for support, bookings and product advice that need several replies. Confirm that your provider offers this conversation tariff for your target market. Separate platform or AI fees can still apply, and US traffic follows the session rules explained above. Google’s conversational billing rules.

Is RCS cheaper than WhatsApp for customer service?

It can be when longer exchanges fit a competitively priced conversation. Short cases, allowances, reach and additional fees can reverse the comparison. Use your own case volume and reply counts.

Can a business replace WhatsApp entirely with RCS?

That depends on customer reach, preference and the required workflow. A gradual pilot gives you evidence before changing a channel customers already use.

Planning an RCS pilot? Book an RCS discovery call. Bring your reply counts and target countries so we can discuss where conversational RCS fits your support workflow. Read how an RCS test sender moves toward production before planning a launch.

What should we explain next? Send us your feedback.