/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Memo: Alexandr Wang says Meta is switching from Google Chat to Slack for internal communications as Slack is the “strongest platform available today for agents”

- Meta is migrating to Slack for internal communications, a memo from AI chief Alexandr Wang says.

Business Insider

Context & Ripple Effects

Meta had already been expanding its internal AI tooling: a March report described how employees build and use those systems, including a CEO-focused internal agent effort. The communication-platform choice turns that internal AI push into a procurement and workflow decision.

Public reaction focused on the operational cost of another chat transition. @gergelyorosz said Meta had previously moved away from its in-house Workchat and that Google Chat messages would not be migrated, framing continuity of work history as a key concern alongside agent capability.

First-order effects

  • Meta employees will shift internal communication workflows from Google Chat to Slack, making Slack the company’s selected environment for agent-oriented collaboration.
  • Slack gains Meta as an internal-communications customer, while Google Chat loses that deployment.

Second-order effects

  • Meta’s internal AI-tool teams will have to build or adapt their collaboration workflows around Slack’s agent capabilities rather than Google Chat’s.
  • Google Chat and other workplace-chat vendors face a clearer competitive test: at Meta, agent support has become an explicit reason to switch platforms.

Third-order effects

  • If other large employers apply the same criterion, workplace chat will be bought less as a standalone messaging utility and more as an agent-enabled work surface.
  • The migration concerns raised by observers show that message history and workflow continuity can become a counterweight to agent features, increasing the switching costs of platform competition.

The trend: Enterprise collaboration software is evolving into an agentic work surface, with AI-tool fit becoming a decisive platform-selection factor.

Discussion

  • @gergelyorosz Gergely Orosz on x
    This was Meta They deprecated their in-house chat solution used a decade+ called Workchat less than a year ago. Decided to move to GChat. Now they're moving again, GChat messages not being migrated Very strange there's so little upfront planning, just YOLO then change course
  • @gergelyorosz Gergely Orosz on x
    Ok some folks liked GChat more than Workchat because of eg perf It's not just Meta: other large companies with dedicated teams build tailor-made products (usually infra ones) that can integrate better, but UX + features behind leading off-the-shelf vendors, and so experience gets…
  • @davidnazarov David Nazarov on x
    AI lowers the cost of writing enterprise software, but doesn't lower the cost of owning its SLOs.
  • @drewpusateri Drew Pusateri on x
    RIP Workplace. it was the worst form of work communications tool except for all those other forms that have been tried. iykyk
  • @elenarunsnyc Elena Dyachkova on x
    OMG! They literally just migrated to gChat from ‘workplace chat’ earlier this year (and that was a pain and a half!). And people were asking for Slack instead back then too.
  • @gergelyorosz Gergely Orosz on x
    Meta has ~75,000 staff. They will spend hundreds of millions per year split across SaaS vendors. And they are using MORE vendors not less vs before! Eg they had an in-house chat product for ~10 years... then bought a vendor (because in-house sucked, even at Meta scale!)
  • @gergelyorosz Gergely Orosz on x
    I just heard: a large company is moving from GChat (Google's Chat product) to Slack, because... Slack has much better agent operability (true) Who thought AI+agents would be a big selling point for Slack? Or that Google would sleep on agents + GChat!
  • @gergelyorosz Gergely Orosz on x
    And don't get me wrong, Meta and everyone else can easily build a chat product with AI, even with a dev and /goal and a large token bill It just won't be GOOD It won't have workflows that “just work.
  • @gergelyorosz Gergely Orosz on x
    Yes it's Meta That they were on GChat (even for a few months) is surprising enough
  • @gergelyorosz Gergely Orosz on x
    To everyone who said or liked posts on “SaaS is dead!  AI is killing it” - no it's not: Meta will be paying Slack easily ~$20M/year for a chat product Ask yourself: if they could build something with 2 devs + AI why not do it?  They'd save SO MUCH.  Because they clearly cannot!!
  • @ricefield Jonathan Tien on x
    It's actually deeply impressive how bad Google continues to fumble. They've had a Teams-level distribution advantage with GChat and have done absolutely nothing about it. Sign a massive deal with Meta.. immediately fumble it and lose it to Slack. Just incredible stuff
  • @charlesrollet1 Charles Rollet on x
    Scoop: @BusinessInsider obtained the memo from Alexandr Wang announcing that Meta is switching over to Slack from Gchat. Meta is making the move because Slack is the “strongest platform” for AI agents today, Wang wrote.