/
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 has been building internal AI tools, with reporting in March describing employee use and a CEO-oriented agent for faster information access. Its August Meta AI expansion into Google Workspace placed the company’s assistant across existing work software, making the communications layer a consequential choice for agent use.

The move also follows a sequence of internal-chat changes: public commenters said Meta had only recently moved from its deprecated Workchat product to Google Chat and flagged the operational burden of another transition. The decision gives AI chief Alexandr Wang a visible role in selecting a core employee work surface.

First-order effects

  • Meta employees’ internal conversations will move from Google Chat to Slack, while Slack becomes the communications environment Meta has selected for AI agents.
  • Google Chat loses Meta as an internal communications deployment; Meta’s employee-agent workflows will be designed around Slack rather than Google Chat.

Second-order effects

  • Meta must reconcile a Slack-centered internal chat workflow with the Meta AI integration with Google Workspace, preserving interoperability across work surfaces rather than standardizing on one vendor.
  • Slack gains a high-profile enterprise deployment whose stated rationale is agent capability, raising the importance of agent-ready collaboration features in competition with Google’s workplace tools.

Third-order effects

  • If large employers increasingly choose collaboration software based on how well agents can operate inside it, chat platforms become an execution layer for workplace AI rather than only a messaging utility.
  • Meta’s shift, after years of building internal tools described in reporting on its employee AI systems, points to a hybrid model in which proprietary agents run atop third-party work surfaces.

The trend: Enterprise collaboration suites are being evaluated as agentic work surfaces, with AI interoperability becoming a purchasing criterion alongside messaging and administration.

Discussion

  • @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
  • @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.
  • @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…
  • @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