Google documents RCS billing thoroughly. Two billing categories, five billable events, precise definitions of what counts as which, a character threshold that changes how a message is charged, and rules for when a conversation window opens.
It does not publish a price. Not for India, not anywhere outside the United States, and in the US it names the carriers instead.
That gap is the whole story of RCS pricing in India, and it is worth understanding before you compare a single quote.
- Google publishes its RCS billing mechanics in exhaustive detail and never publishes a rate.
- The only operator-level figure with a traceable origin is ₹0.11 per message, reported by the Economic Times in December 2025 and carried by TelecomTalk. Eight months on it is still the most recent.
- Airtel confirmed the Google partnership on the record in March 2026 and said nothing about price.
- Meta, by contrast, publishes a dated per-market rate card as a downloadable file, including a category it marks as not applicable because it is free.
What Google publishes about RCS pricing in India
The standard billing model, which is what applies in India, has two categories. Note these are a property of the agent, not of the message.
| Billing category | Applies to | How it bills |
|---|---|---|
| Non-conversational | Agents that mainly send one-way messages: OTPs, alerts, offers | Per message |
| Conversational | Agents built for back-and-forth exchange | Per conversation, a 24-hour window |
Two things about that table matter more than they look.
The category is chosen when you create the agent and cannot be changed afterwards.
You choose this category when you create your agent, and it can't be changed later.
Standard billing FAQ — Google for Developers
That is a larger commitment than any rate you are quoted, and it is made before you have sent a message.
The categories were only just consolidated. Google merged the legacy Basic Message and Single Message categories into Non-conversational on 20 November 2025, with existing agents migrating from 16 March 2026. Any guide written before that date describes a structure that no longer exists.
Separately, and easy to confuse with the above, Google defines five billable events which are a property of the message rather than the agent. Google warns about the confusion explicitly: "The basic_message and single_message billable events shouldn't be confused with the Basic Message and Single Message billing categories."
One of those events contains a cost trap worth naming.
basic_message is a text-only message of 160 characters or fewer. A text-only message over 160 characters is billed as single_message, the same event as a message with rich content.
There is no image, no button and no carousel involved. Going one character over a threshold moves the message into a different billing event.
Also worth knowing: on non-conversational agents there is a p2a_message event, which means the business is billed when a user messages it. Inbound is not free.
What Google never states is what any of this costs. Its US carrier billing page says so directly, and there is no India equivalent of that page at all.
US carriers set the price for the billable message types described in the following sections. They also determine the developer's final charge for sending RCS for Business messages.… For additional pricing or billing information, please contact the appropriate carrier representatives.
US billing model — Google for Developers
Google will tell you precisely how you are billed and never once what you are billed.
The one operator figure, and how it travelled
Three outlets carry the figure with its attribution intact. TelecomTalk's version, verbatim: "According to unnamed industry executives quoted by the Economic Times, Airtel will levy a charge of Rs 0.11 per RCS message under an 80:20 revenue-sharing arrangement with Google." The Week and Developing Telecoms reported it the same way, in early December 2025 and from the same source.
A fourth carried the number without it. Angel One's write-up credits the Economic Times for the partnership itself, then states the rate in its own voice: "Airtel will begin offering RCS using Google's platform under a commercial model that charges ₹0.11 per message, supported by an 80:20 revenue share." That is Angel One on 8 December 2025; its standfirst goes further, describing the partnership as "enabling ₹0.11 per message business messaging".
Same figure. The newspaper is still named, but the executives, the anonymity and the hedge are gone, and what was a reported intention has become a commercial model.
Then Airtel published officially, and said nothing. Its press release of 1 March 2026 confirms the Google partnership and the spam-filtering arrangement. It contains no rate, no revenue share, no mention of paise. The operator went on the record about the partnership and left the price to the leak.
Eight months on, that December report remains the most recent operator-level figure anyone can point to. Everything else in this market is a vendor's own pricing page.
What Meta does instead
The comparison is not flattering, and it is the same industry.
Meta publishes a downloadable rate card by currency, listing every destination market it bills in that currency, with a stated effective date. The India row of the INR card for the WhatsApp Business Platform:
| Category | Rate per message |
|---|---|
| Marketing | ₹0.8631 |
| Utility | ₹0.1150 |
| Authentication | ₹0.1150 |
| Authentication (international) | ₹2.4971 |
| Service | not applicable |
Effective 1 July 2026, published by Meta as a downloadable CSV and PDF.
The last row is the part worth pausing on. Service is listed and marked not applicable, because Meta made service conversations free for all businesses in November 2024. A rate card that names a category in order to say it costs nothing is disclosing more than four numbers alone would.
This is not an argument that WhatsApp is cheaper. Meta's utility and authentication rate, ₹0.1150, sits below most RCS quotes. Its marketing rate, ₹0.8631, sits well above them. Which channel costs less depends entirely on which category of message you need to send, and you can work that out because Meta published the figures.
What to ask before you sign
Since no published rate exists to compare against, the useful move is making a quote specific enough that two of them can be compared at all.
- Is my agent non-conversational or conversational, and can that be changed later
- What is the rate for a text message over 160 characters, not just the headline basic rate
- Am I billed when a user messages me, and at what rate
- What is the SMS fallback rate, and am I billed for the RCS attempt as well as the fallback
- Is this rate volume-committed, and what happens if I do not hit the volume
- Does the rate differ by operator, given Jio, Airtel and Vi price independently
- Are DLT registration and brand verification included or billed separately
The first one is not a pricing question. It is an architecture decision that cannot be reversed, and most quotes do not mention it at all.
The short version
All three major Indian operators carry RCS through Google. None of them publishes a rate. Google documents the billing model in more detail than most platforms bother with and stops short of the number.
That leaves every quote you receive as an aggregator's margin on an unpublished wholesale rate, which is not a scandal but does mean two quotes cannot be compared without knowing the agent category, the character threshold, the inbound billing and the fallback terms.
The channel is worth using. Just do not mistake a headline rate for a price.
As of August 2026:
- RCS rate for India: ₹0.11/message (one leaked figure, not official)
- WhatsApp marketing rate for India: ₹0.8631 (published by Meta, effective 1 July 2026, source: developers.facebook.com)
- WhatsApp utility rate for India: ₹0.1150 (same source)
- No operator rate card for RCS exists anywhere in the public domain
Sources
Sources last verified: 4 August 2026. The Google billing documentation, Meta rate card, and Airtel press release were all retrieved and confirmed on this date.
- Standard billing FAQ — Google for Developers
- US billing model — Google for Developers
- Pricing on the WhatsApp Business Platform — Meta for Developers
- Airtel and Google Collaborate to Advance Spam Protection in India With Secure RCS Messaging — Bharti Airtel, 1 March 2026
- Airtel Teams Up With Google to Roll Out RCS Messaging in India — TelecomTalk
- Why did Bharti Airtel, Google join hands to roll out RCS messaging in India after months of hesitation? — The Week, 8 December 2025
- Airtel working with Google to launch RCS: report — Developing Telecoms
- Airtel and Google Partner to Bring RCS Messaging to India — Angel One, 8 December 2025
Originally published at botsense.io by Mohit Nagwani, Founder of Botsense — a Verified Meta Tech Provider offering WhatsApp Business API and AI Calling software for Indian businesses.
Top comments (0)