Meta Ditches Google Chat for Slack Because of AI Agents

Meta is switching its internal communications from Google Chat to Slack — and the reason its own AI chief gave is not features, price, or security. It is agents.

In a staff memo reported by The Information and Business Insider, Meta Chief AI Officer Alexandr Wang told employees this week that the company is abandoning Google Chat less than a year after migrating to it from its homegrown Workchat tool. “Slack is the strongest platform available today for agents, which is why we’re deciding to make the switch,” Wang wrote. He pointed to Slack’s “rich conversational interface for agents, mature developer tooling and strong 3P integrations,” and added that “while not all of us are building agents today, everyone at the company will benefit from a robust and useful agent ecosystem.”

Meta and Salesforce declined to comment on the deal terms; Google did not respond to requests for comment.

A third messaging home in two years

The whiplash is the story. Meta ran its internal communications on Workchat — an internal fork of its Messenger infrastructure — for more than a decade. When Meta killed the commercial Workplace product and reorganized around its Superintelligence Labs, the company moved employees onto Google Chat. That experiment lasted under a year.

Now the pendulum has swung again, and the deciding factor has fundamentally changed. The first migration was about consolidation and cost. This one is about which chat surface an autonomous agent can actually reach into. That is a new kind of procurement criterion, and it arrived faster than most enterprise software categories ever evolve.

Why agents are reshaping the chat market

The collaboration-suite wars used to be fought over threads, huddles, and integrations with human tools. The 2026 version of that fight is about which platform gives AI agents the best operating environment:

• Conversational surface as agent runtime. Agents need a place where humans and software can share a channel, mention each other, and exchange structured actions — not just messages. Slack’s channel model, app framework, and bot semantics were designed for exactly this kind of third-party presence.
• Developer tooling maturity. Slack’s platform APIs, real-time events, and agent-adjacent frameworks (from Agentforce to third-party agent builders) give internal platform teams a proven path to deploy agents where employees already work.
• The MCP ripple effect. Slack shipped a Model Context Protocol server and real-time search API, turning its conversational archive into queryable context for agents. Anthropic’s MCP standard crossed 400 million monthly downloads this week — and agent-platform interoperability is increasingly the default assumption in enterprise AI stacks.

The irony is thick: Meta — the company building superintelligence with a reported multi-hundred-billion-dollar compute budget — concluded that the best agent substrate for its own 70,000+ employees is a product owned by Salesforce, which bought Slack for $27.7 billion in 2021 and has spent the years since trying to make agent orchestration the reason enterprises keep paying for it.

A marquee win for Salesforce’s agent bet

For Salesforce, this is the reference customer its Agentforce narrative has needed. The company has repositioned Slack as the “agentic OS” of the enterprise — the conversational layer where Agentforce agents, partner agents, and custom internal agents all live side by side with human coworkers. Winning Meta — a company with one of the most sophisticated internal AI organizations on the planet — as an internal-tooling customer is a validation no marketing campaign could buy.

It also sharpens the competitive dynamics in an awkward way. Google Workspace has been repositioning Google Chat around Gemini (including the “Ask Gemini” command-line rollout in late August). Microsoft is pushing Copilot and agents deep into Teams. Wang’s memo effectively argues neither is good enough yet — and that Meta, of all companies, would rather pay a rival’s bill than wait.

Europe is heading the other way

The Meta decision lands against a very different backdrop in the public sector. European governments are migrating toward sovereign stacks, not agent ecosystems:

• France has ordered its ministries to replace Teams and Zoom for 2.5 million civil servants by 2027, moving to Tchap, a messenger built on the open Matrix protocol running on sovereign infrastructure.
• The German state of Schleswig-Holstein moved 110 million emails off proprietary software, saving €15 million in licensing fees.
• The EU Data Act now caps switching costs and requires providers to complete data transfers within 30 days — and from January 12, 2027, switching charges are prohibited entirely.

So the market is bifurcating: private AI-first companies choosing platforms for agent operability, and public institutions choosing platforms for sovereignty and exit rights. Both trends punish the same thing — vendor inertia.

What we still don’t know

Notably absent from the memo and the reporting: a migration completion date, seat count, or contract value. Meta employs well over 70,000 people, and enterprise Slack pricing at that scale with agent platform add-ons plausibly runs to tens of millions of dollars a year. Whether Meta negotiated an unusual structure — data-residency terms, custom agent hosting, or an on-premise component — is unknown.

There is also an open question about Google’s response. Losing Meta as an internal-tools customer is a modest revenue hit but a symbolic bruise for Google Chat’s enterprise ambitions, and it hands Salesforce a story to tell at every Dreamforce for the next five years.

The bigger signal

Strip away the vendor politics and the takeaway for the industry is simple: agent-readiness has become a first-class procurement criterion. When one of the world’s largest AI laboratories evaluates its internal chat tool, the deciding question was not “which app do employees prefer?” but “which platform lets our agents live alongside our people?”

Every collaboration vendor now has to answer that question. Google’s answer will need to be more than Gemini embedded in Chat — it needs a credible agent runtime argument. Microsoft has the distribution with Teams but is still converting Copilot presence into genuine agent operability. And Slack just won the most convincing proof point available: the company building frontier AI chose it for its own people.

The chat window, it turns out, is becoming the agent’s home address. Meta just told the market whose door it is knocking on.