At Google Marketing Live 2026, Google introduced Message Ads with RCS for Business — a conversational format that, in Google’s words, moves users from a Search ad into a verified text thread where AI qualifies leads instantly. The promise is a persistent, mobile-native channel that replaces the friction of “we’ll call you” with a real-time presence that captures intent around the clock. It is a genuinely new way to turn a click into a conversation. The question this guide answers is narrower and more useful than “is it exciting”: does it belong in a B2B SaaS funnel, and if so, where?
The honest reading is that RCS Message Ads were designed with consumer and local-business use cases front of mind, and B2B SaaS has to work harder to justify them. That does not mean ignore the format — it means test it deliberately, in the specific spots where a fast mobile chat actually fits how your product gets bought, and measure it against the lead forms and demo pages it would compete with. Below we break down what the format is, where it plausibly fits SaaS, where it does not, and how to run a contained test without letting it quietly degrade your lead quality.
What RCS Message Ads actually do
RCS — Rich Communication Services — is the carrier-backed successor to SMS, supporting verified sender profiles, rich media, typing indicators, and read receipts inside the phone’s native messaging app. A Message Ad with RCS uses that channel as the destination: a searcher taps your Search ad and, instead of landing on a page, drops into a branded, verified text thread. A Google AI agent greets them, answers questions, and qualifies intent, and the thread persists — so if the buyer closes the app, the conversation is still sitting in their inbox when they come back. Google’s framing is that this keeps a brand “top of mind” and easily reachable rather than vanishing at the end of a session.
Two properties matter most for evaluating fit. First, verification: the thread shows an official brand profile rather than an anonymous number, which reduces the trust gap that has always plagued SMS marketing. Second, persistence and asynchronicity: unlike a phone call, which is live-or-nothing, an RCS thread lets the buyer respond on their own schedule, and unlike a lead form, it is a two-way exchange rather than a one-shot submission. That places the format squarely between the lead form and the call-based ad in the capture spectrum — softer and more conversational than a form, less immediate and human than a call.
Where it plausibly fits B2B SaaS
The strongest B2B SaaS fit is high-velocity, lower-consideration products where an individual buyer can make a decision without assembling a committee. If you sell a self-serve tool with a short evaluation, a quick chat that answers “does it integrate with X” or “what does the team plan cost” can move someone toward a trial faster than a form that dumps them into a nurture sequence. Product-led motions, where the goal is to remove friction between interest and signup, are the most natural candidates — the same logic that drives our thinking on Google Ads for product-led SaaS. In those contexts, an always-on agent answering objections at the moment of intent is doing useful work.
Speed-to-lead is the other angle. In segments where the first vendor to respond disproportionately wins the deal, a channel that engages instantly and keeps the thread warm has real value, and the AI agent handles the coverage gap outside business hours. This overlaps conceptually with Google’s other agentic lead format; if you are weighing them, our breakdown of the Business Agent for Leads covers the same “AI qualifies the lead in-ad” pattern in a different surface. For both, the win condition is identical: the conversation has to produce qualified pipeline, not just a higher volume of shallow chats.
Where it does not fit — and why
For classic enterprise and mid-market B2B SaaS, RCS Message Ads face an uphill battle. Those deals are researched on desktop, evaluated against security and procurement requirements, and decided by a buying committee over weeks or months. A mobile chat thread is a poor container for that process: the person doing the searching is often a champion gathering information for others, not a decision-maker who can be closed in a text exchange. Pushing a considered, multi-stakeholder purchase into a consumer-style messaging format risks underperforming the landing pages and lead forms that are actually built for qualification — the same mismatch we flag for teams running sales-led B2B SaaS.
There is also a brand-safety dimension. An AI agent conversing live under your verified profile needs firm guardrails, because in B2B the wrong answer about data residency, SOC 2 status, contract terms, or pricing tiers is not a minor slip — it can misrepresent the product or create expectations sales cannot honour. The agent should be scoped to qualify and route, not to negotiate or commit. If your product carries compliance-sensitive claims, the setup and review overhead of governing that agent may outweigh the incremental leads, which is a perfectly valid reason to sit the format out until it matures.
How to run a disciplined test
If the format is plausibly a fit, test it the way you would test any new capture path: contained budget, one clear segment, and full-funnel measurement. Point RCS Message Ads at mobile traffic for a product or campaign where quick answers genuinely help, and run it in parallel with your existing lead forms rather than replacing them. Set up the AI agent with a tight qualification script — the questions your SDRs would ask on a first touch — and define exactly how a qualified thread hands off to a human and into the CRM. A conversation that never becomes a tracked, routable record is not a lead; it is a missed one.
Then judge it on the metric that matters. Cost per lead will almost certainly look good, because a low-friction chat entry generates volume — which is precisely why cost per lead is the wrong yardstick here. Measure lead-to-SQL and SQL-to-opportunity, compared against your other formats, exactly as you would when deciding between cost per lead and cost per SQL. If RCS produces cheaper leads that convert to pipeline at the same or better rate, scale it. If it produces a flood of chats that never qualify, cut it quickly — the setup cost is sunk, but the ongoing budget and the sales-team drag are not. Treated as a measured experiment rather than a must-adopt trend, RCS Message Ads are a low-risk thing to learn from; treated as a channel you owe adoption to, they are an easy way to bury your pipeline in noise.