--- title: Meta is switching from Google Chat to Slack, citing AI... description: Meta is dropping Google Chat for Slack as its internal communication tool, less than a year after switching from its own Workchat to Google Chat. AI chief... canonical: https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Meta is switching from Google Chat to Slack, citing AI agent support | daily.dev og:description: Meta is dropping Google Chat for Slack as its internal communication tool, less than a year after switching from its own Workchat to Google Chat. AI chief... og:url: https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn og:image: https://api.daily.dev/og/posts/LjpjnoNpn.png og:image:alt: Meta is switching from Google Chat to Slack, citing AI agent support og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Meta is switching from Google Chat to Slack, citing AI agent support **[Collections](https://daily.dev/sources/collections)** · 2 min read · 0 upvotes · 0 comments ## Summary Meta is dropping Google Chat for Slack as its internal communication tool, less than a year after switching from its own Workchat to Google Chat. AI chief Alexandr Wang cited Slack's conversational interface, developer tooling, and third-party integrations - particularly better AI agent support - as the deciding factors. The deal will reportedly cost Meta around $20M annually, raising questions about why Meta didn't build an in-house alternative despite having the engineering resources. Meanwhile, European governments are heading the opposite direction, adopting sovereign self-hosted chat tools like France's Tchap (600,000+ users) and Germany's openDesk, prioritizing data control over ecosystem integrations, aided by EU Data Act provisions capping provider-switching fees by January 2027. ## Content Meta is moving its internal communications from Google Chat to Slack. AI chief Alexandr Wang pointed to Slack's conversational interface, developer tooling, and third-party integrations as the main reasons - specifically that AI agents work better there. The timing is a bit awkward. Meta deprecated its decade-old in-house chat tool Workchat less than a year ago and moved to Google Chat. Now it's moving again, with no message migration from GChat. It's hard not to notice the lack of upfront planning - two major platform switches in under a year. The Slack deal will likely cost Meta around $20M per year. Which raises an obvious question: why not just build something internally? Meta has the engineers. But apparently even a company of Meta's scale can't replicate what Slack offers cheaply enough to bother - which is a pretty direct rebuttal to the "SaaS is dead, just use AI to build it" crowd. The agent angle is genuinely interesting though. Slack's edge here isn't just features - it's that Google apparently hasn't prioritized agent integration in Chat, and that gap is now big enough to drive a company-wide platform switch at one of the largest tech firms in the world. Nobody predicted "agent operability" would be Slack's killer differentiator in 2025. Europe is moving in the opposite direction entirely. Governments there have spent two years adopting sovereign, self-hosted alternatives - France's Matrix-based Tchap has over 600,000 users, and Germany is rolling out openDesk. The priority is server control, not ecosystem integrations. The EU Data Act also caps and eventually eliminates provider switching fees by January 2027, which makes it easier to move between services. The tradeoff is that these sovereign stacks don't have anything close to Slack's agent ecosystem yet. So you have two very different bets playing out simultaneously: Meta chasing agent capabilities at significant cost, and European governments accepting a less integrated toolset in exchange for data sovereignty. It's not obvious which approach ages better. ## Questions this post answers ### Why is Meta switching from Google Chat to Slack? Meta's AI chief Alexandr Wang cited Slack's conversational interface, developer tooling, and third-party integrations as the main reasons, specifically that AI agents work better within Slack than Google Chat. The move comes less than a year after Meta had already migrated from its decade-old internal tool Workchat to Google Chat, and there is no message migration planned from Google Chat to Slack. _Teams weighing chat platforms for AI agent workflows can follow how Slack vs Google Chat integrations evolve on daily.dev._ ### How much will Meta's Slack deal cost annually? Meta's deal with Slack will reportedly cost around $20 million per year. This raised questions about why a company with Meta's engineering resources would pay for a third-party tool rather than build an internal alternative, suggesting that even large tech companies can't easily replicate Slack's ecosystem, including its AI agent integrations, cheaply enough to justify building in-house. _Anyone comparing build-versus-buy costs for internal tools can track vendor pricing shifts on daily.dev._ ### What sovereign chat alternatives are European governments adopting instead of Slack or Google Chat? France uses Tchap, a Matrix-based messaging platform with over 600,000 users, while Germany is rolling out openDesk. These sovereign, self-hosted alternatives prioritize server control and data sovereignty over ecosystem integrations, though they currently lack anything close to Slack's AI agent ecosystem. The EU Data Act will also cap and eventually eliminate provider-switching fees by January 2027. _Developers weighing data sovereignty against ecosystem features can follow this tradeoff on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 3 discussions and 295 comments across x (as of 2026-09-02). **TL;DR:** Discussion centers less on Meta specifically and more on why mature SaaS (like Slack) still wins over in-house or AI-built alternatives, with heavy skepticism toward Google's execution on chat/agent tooling and Meta's repeated migration churn. **Sentiment:** 15% positive · 40% mixed · 45% skeptical **The case for** - Some argue Slack clearly earned this by leaning hard into agentic workflows and bot APIs years before competitors. - Several note that outsourcing chat to a mature SaaS means Meta doesn't have to own support, integrations, and edge-case maintenance itself. **The pushback** - Many are baffled Meta chose Google Chat only a year ago and is already migrating again, calling it a planning/leadership failure. - Commenters worry that repeated migrations destroy searchable institutional chat history and context. - Multiple people argue Google Chat's API and integrations have always been weak/admin-gated compared to Slack's. - Several push back on the idea that AI makes building a Slack alternative easy, arguing the real cost is ownership, support, and edge cases, not code. **By community** - x (mixed): A large tangent debates whether AI/two-person teams can really replace mature SaaS platforms, while another thread mocks Google's chat strategy and Meta's repeated migrations. **Hottest debate:** Whether AI-assisted development makes it feasible to build an in-house Slack replacement, versus the argument that integrations, support, and long-term ownership are the real moat. **Open questions** - Why did Meta pick Google Chat only a year ago if these agent-support gaps were already visible? - Will Meta's chat history/context be preserved through this second migration, or lost again? - What specifically drove the decision — was it purely product capability, or vendor incentives/deals with Google/Slack? **Highlights** > @adam_fresko The “silliest thing” meaning ~75,000 using a tool for comms, bot automations etc You could make the same case for any tool: if it doesn’t work just change it. The more people you have the more it pays to do at least a little planning to avoid churn (that adds up) later. Or you > — [GergelyOrosz on x · 43 points, 1 comments](https://x.com/GergelyOrosz/status/2094681635052482838) > @GergelyOrosz the 2 devs and ai replacing saas thing never made sense to me, building the tool aint hard. Its the integrations, trust, and support built up over years that actually keeps companies paying > — [PeterRex on x · 1 points](https://x.com/PeterRex/status/2094792058347176026) > @GergelyOrosz AI made building the thing cheap. It didn't make owning the thing cheap. That $20M is not paying for a chat app. It's paying to never think about chat again. > — [nathangu76 on x · 1 comments](https://x.com/nathangu76/status/2094828760168071614) > @GergelyOrosz Google Chat feels like a basic wrapper for Gemini only. Slack's agentic AI actually takes actions & runs workflows across tools now. For large companies, saving 10 mins per task via an agent is worth the extra seat cost. Google has the tech but the integration is very slow. > — [akshatb712 on x · 3 points, 1 comments](https://x.com/akshatb712/status/2094706842173907367) > @GergelyOrosz Slack didn't plan for this, they just shipped a real bot API a decade ago and never walled it off. Google Chat's API has always been admin-gated and thin. > — [somi\_ai on x](https://x.com/somi_ai/status/2094588567934881862) **Source threads** - [x](https://x.com/GergelyOrosz/status/2094677471392059467) · 0 points · 78 comments - [x](https://x.com/GergelyOrosz/status/2094559887162306971) · 0 points · 105 comments - [x](https://x.com/GergelyOrosz/status/2094686709162131614) · 0 points · 112 comments --- Tags: [#google](https://daily.dev/tags/google), [#ai-agents](https://daily.dev/tags/ai-agents), [#slack](https://daily.dev/tags/slack) [View this post on daily.dev](https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Meta is switching from Google Chat to Slack, citing AI agent support","url":"https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn"},"datePublished":"2026-09-01T19:10:06.808Z","dateModified":"2026-09-02T03:26:15.854Z","description":"Meta is dropping Google Chat for Slack as its internal communication tool, less than a year after switching from its own Workchat to Google Chat. AI chief...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/05b201e6b353ed8f835ddd771303ff7b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/05b201e6b353ed8f835ddd771303ff7b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"google,ai-agents,slack","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Meta is switching from Google Chat to Slack, citing AI agent support"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/meta-is-switching-from-google-chat-to-slack-citing-ai-agent-support-ljpjnonpn#faq","mainEntity":[{"@type":"Question","name":"Why is Meta switching from Google Chat to Slack?","acceptedAnswer":{"@type":"Answer","text":"Meta's AI chief Alexandr Wang cited Slack's conversational interface, developer tooling, and third-party integrations as the main reasons, specifically that AI agents work better within Slack than Google Chat. The move comes less than a year after Meta had already migrated from its decade-old internal tool Workchat to Google Chat, and there is no message migration planned from Google Chat to Slack. Teams weighing chat platforms for AI agent workflows can follow how Slack vs Google Chat integrations evolve on daily.dev."}},{"@type":"Question","name":"How much will Meta's Slack deal cost annually?","acceptedAnswer":{"@type":"Answer","text":"Meta's deal with Slack will reportedly cost around $20 million per year. This raised questions about why a company with Meta's engineering resources would pay for a third-party tool rather than build an internal alternative, suggesting that even large tech companies can't easily replicate Slack's ecosystem, including its AI agent integrations, cheaply enough to justify building in-house. Anyone comparing build-versus-buy costs for internal tools can track vendor pricing shifts on daily.dev."}},{"@type":"Question","name":"What sovereign chat alternatives are European governments adopting instead of Slack or Google Chat?","acceptedAnswer":{"@type":"Answer","text":"France uses Tchap, a Matrix-based messaging platform with over 600,000 users, while Germany is rolling out openDesk. These sovereign, self-hosted alternatives prioritize server control and data sovereignty over ecosystem integrations, though they currently lack anything close to Slack's AI agent ecosystem. The EU Data Act will also cap and eventually eliminate provider-switching fees by January 2027. Developers weighing data sovereignty against ecosystem features can follow this tradeoff on daily.dev."}}]} ```