Slack vs Microsoft Teams

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Slack
   Slack✓fullprobed8/10

   Slack has a confirmed llms.txt at docs.slack.dev/llms.txt (HTTP 200) plus llms-full-deno.txt variants, and its developer docs are explicitly agent-oriented (MCP server, AI build guides, quickstart) suitable for pointing an agent at. missing for 10: no independent/community confirmation of an agent successfully consuming llms.txt in practice, and OpenAPI-style machine spec endpoints under docs.slack.dev returned 404.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.slack.dev/llms.txt # Slack Developer Docs > The official documentation for building on the Slack p…”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “You can create Slack-hosted workflows written in TypeScript using the Deno Slack SDK.”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   Probes explicitly show no llms.txt (404), no markdown-accessible docs endpoint, and no OpenAPI spec at Microsoft Learn — there's no agent-oriented documentation surface for an AI agent to point at. All other evidence is standard human-readable docs, not agent-consumable formats.

   • [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://learn.microsoft.com/en-us/microsoftteams/platform/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Web API (chat.postMessage etc.) is a pure HTTP interface callable without any UI, the Events API supports webhook/Socket Mode server-side listening, Workflow Builder supports webhook triggers to kick off automations from outside Slack, and the Slack CLI/Bolt SDKs let apps be built, deployed, and run non-interactively — all enabling headless automation suitable for CI-like use. Missing for 10: explicit CI/CD pipeline examples (e.g. GitHub Actions integration), and no documentation of running the CLI/SDKs specifically inside a CI runner or headless test harness.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Microsoft Teams~partialprobed5/10

   Microsoft Teams platform is automatable via the Microsoft 365 Agents Toolkit CLI (create, provision, deploy, package, and publish agents entirely from the command line) and via Microsoft Graph APIs that let external services 'run outside the Microsoft Teams user experience' to automate Teams scenarios like messaging, team/channel creation, and exports. This supports CI-style scripted automation of app/agent lifecycle and messaging, but there is no explicit documentation of running the Teams client itself headlessly or wiring these tools into a CI pipeline end-to-end. Missing for 10: explicit headless/CI runbook or GitHub Actions example, confirmation of non-interactive auth flows for CI, and independent evidence of real-world CI usage.

   • [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
   • [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
   • [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
   • [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
   • [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions... Agent/Application Creation: Generate a new agent or app using available…”
   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round drawn
   Slack—none0/10

   All evidence describes Slack exposing its own official MCP server so external AI clients (Claude, ChatGPT, custom agents) can call Slack's tools — the reverse direction of this story, which asks whether a user can plug external MCP servers into Slack so Slack's own agents (e.g., Slackbot) can use their tools. No evidence shows Slack acting as an MCP client that consumes third-party MCP servers.

   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   No evidence that Microsoft Teams (or its agent/bot platform) supports plugging in MCP servers as tool providers; docs cover bots, message extensions, connectors, webhooks, and Copilot/Graph integration but never mention MCP. Missing for 10: any documentation of MCP server connection, tool registration via MCP, or first-party MCP client support in Teams agents.

   • [claimed-docs] “Quickstart: Create an agent and chat with it in Teams”
   • [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
   • [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Slack
   Slack✓fullprobed8/10

   Slack publishes an official MCP server (docs.slack.dev/ai/slack-mcp-server/) that lets MCP clients/agents search channels, send/draft messages, manage canvases, lists, files, and users, with admin approval controls for governance; this is corroborated by a direct probe confirming the docs page exists. Missing for 10: independent hands-on third-party verification of the MCP server's real-world reliability/performance beyond first-party docs.

   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Send messages — send messages to any type of conversation in Slack.”
   • [claimed-docs] “Create and read lists — create lists with custom schemas and read their contents.”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “Draft messages — draft, format, and preview messages directly within AI clients.”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   The evidence pack covers Teams' bot/agent SDK, Graph API, webhooks, and Agents Toolkit CLI, but nowhere mentions an official MCP (Model Context Protocol) server or endpoint that would let external AI agents connect to Teams. As a SaaS collaboration platform, this axis is a fair question, but no evidence shows it is delivered.

   ⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round drawn
   Slack✓fullprobed8/10

   Slack ships an official CLI for building/managing Slack apps (slack-docs-9, slack-docs-1, slack-docs-26/40/60, slack-probe-4), with quickstart guides supporting Bolt frameworks in multiple languages, tied into an AI-native workflow (docs mention creating agents via 'slack create' and building AI-integrated apps). Missing for 10: independent/hands-on community corroboration of the CLI itself (community evidence in the pack is unrelated to CLI usage) and more detail on AI-native-specific CLI commands beyond scaffolding.

   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “Download the command-line tool for developing Slack apps.”
   • [claimed-docs] “Set up a new Bolt project from a starter template. `slack create`”
   • [claimed-docs] “slack create”
   • [claimed-docs] “Set up a new Bolt project from a starter template.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [probe] “official CLI documented at https://docs.slack.dev/tools/slack-cli/”

   proof ↗⚑ flag

   Microsoft Teams✓fullprobed8/10

   Microsoft ships an official Microsoft 365 Agents Toolkit CLI, documented as offering the same features as the IDE extensions—agent/app creation from templates, resource provisioning/deployment to Azure, validation/packaging/publishing, and preview—directly supporting AI-native agentic workflows for Teams apps/agents. missing for 10: independent/hands-on verification of CLI usage and no evidence of scripting/automation depth (e.g., CI/CD examples) beyond first-party docs.

   • [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
   • [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
   • [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
   • [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
   • [claimed-docs] “Upload and preview your agent or app in Teams, Outlook, and the Microsoft 365 app.”
   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Slack
   Slack✓fullprobed9/10

   Slack ships extensive documented public APIs (Web API with 200+ methods, Events API, Bolt/CLI SDKs, official OpenAPI/AsyncAPI specs in slackapi/slack-api-specs) plus an official MCP server enabling AI-native agents to search, message, upload files, manage lists/canvases — all first-party documented and independently verifiable via the public GitHub spec repo. missing for 10: no independent hands-on report specifically confirming the raw REST/Web API (vs MCP) working end-to-end from a third-party AI integrator, and the docs.slack.dev/openapi.json probe returned 404 suggesting the interactive spec isn't hosted at the expected discovery path.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “official MCP server documented at https://docs.slack.dev/ai/slack-mcp-server/”
   • [probe] “official CLI documented at https://docs.slack.dev/tools/slack-cli/”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Microsoft Teams✓fullprobed8/10

   Microsoft Teams exposes extensive, well-documented public APIs (Microsoft Graph Teams API, Bot Framework, webhooks/connectors, Teams platform APIs) enabling programmatic control of chats, channels, teams, and messages, plus a CLI (Agents Toolkit CLI) for automating agent/app creation, provisioning, and publishing. This is corroborated by community complaints acknowledging the API exists but noting it requires the fuller Azure/Graph stack rather than simple webhooks. Missing for 10: a discoverable OpenAPI/llms.txt spec (probes returned 404s) and stronger independent hands-on validation of API robustness beyond docs and one critical community note.

   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
   • [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
   • [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
   • [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
   • [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”

   proof ↗⚑ flag

7. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Slack
   Slack~partialclaimed4/10

   Slack's API model implies scoped bot/user tokens (the OpenAPI spec notes 'user and bot user token usage of public Web API methods') and admin approval of MCP client integrations is described as keeping data safe, suggesting some governance over agent access, but there is no explicit documentation of an OAuth-scopes system or a user-facing flow to mint least-privilege credentials specifically for an agent. Missing for 10: explicit OAuth scope list/granularity docs, a documented workflow for a user to generate a scoped token for an agent, and any admin/user UI for restricting agent permissions beyond MCP client approval.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   While Teams' Graph API and Agents Toolkit are documented for building agents/apps, none of the evidence describes issuing scoped or least-privilege API credentials specifically for an agent (e.g., granular OAuth scopes, permission consent flows tied to agent identity). The docs mention Azure resource provisioning and Graph API access broadly but not credential scoping mechanics.

   • [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
   • [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Slack
   Slack✓fullclaimed9/10

   Slack ships multiple official SDKs (Bolt for Java, node-slack-sdk, Deno Slack SDK), an official CLI, Web API with published OpenAPI spec, Events API, and Block Kit docs, all clearly documented as first-party developer tooling for building AI-native/agentic integrations, plus a developer sandbox for safe testing. Missing for 10: independent/hands-on developer corroboration beyond official docs and a fully discoverable OpenAPI endpoint (probe found candidate paths 404 despite spec repo existing).

   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “You can create Slack-hosted workflows written in TypeScript using the Deno Slack SDK.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “Whether you're composing layouts for modals, messages, or tabs, the Block Kit building experience is the same — your app will be sculpting s…”

   proof ↗⚑ flag

   Microsoft Teams✓fullprobed7/10

   Microsoft documents official SDKs/toolkits (Bot Framework/Teams AI SDK equivalents implied via bots, Agents Toolkit CLI, Microsoft Graph API, Copilot extensibility) for building agents, bots, tabs, and message extensions against Teams, with a dedicated CLI and IDE tooling for creation, provisioning, and publishing. missing for 10: no independent/hands-on developer corroboration of SDK quality or ergonomics, and probes show no machine-readable API spec (openapi.json 404) or llms.txt, suggesting docs aren't fully AI-native optimized.

   • [claimed-docs] “Agents Toolkit CLI offers the same features as the IDE extensions.”
   • [claimed-docs] “Agent/Application Creation: Generate a new agent or app using available templates and samples.”
   • [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”
   • [claimed-docs] “Validation, Packaging, and Publishing: Validate, package, and publish your agent or application using CLI commands.”
   • [claimed-docs] “Port a Slack Bolt app to Teams”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
   • [probe] “official CLI documented at https://learn.microsoft.com/en-us/microsoftteams/platform/toolkit/microsoft-365-agents-toolkit-cli”
   • [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Events API lets developers subscribe to specific event types via webhook (public HTTP endpoint) or Socket Mode, with Slack calling the subscriber's endpoint on events — a core webhook-subscription mechanism well documented for building AI/agentic integrations. Workflow Builder also supports webhook triggers for starting workflows externally, reinforcing webhook-based event subscription. missing for 10: independent/hands-on corroboration of webhook reliability at scale, and more explicit framing of Events API webhooks specifically for AI-native/agent consumption (most AI-agent docs emphasize MCP/Web API rather than raw event webhooks).

   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Webhook triggers for workflows”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed6/10

   Teams documents Incoming and Outgoing Webhooks and Connectors that let external services subscribe to and post messages/events to Teams channels (ms-teams-docs-12, ms-teams-docs-30, ms-teams-docs-36, ms-teams-docs-44), which is a real webhook subscription mechanism. However the evidence doesn't show Microsoft Graph's richer change-notification/subscription API for broader event types (message edits, membership changes, etc.), nor any AI-agent-specific webhook workflow. Missing for 10: explicit Graph webhook/subscription API documentation for arbitrary event types, and independent confirmation of reliability for programmatic/AI-native use cases.

   • [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
   • [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
   • [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
   • [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships built-in AI features (intelligent daily briefing, Slackbot summaries/recaps, channel/thread summarization, workspace-wide semantic search across integrated data, meeting notes from huddles) that surface AI-generated insights directly inside the product, per slack-docs-13/14/15/16/19/34/52. missing for 10: independent/hands-on verification of insight quality and accuracy, and detail on how suggestions are surfaced/actioned beyond marketing copy.

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Conversations with coworkers, PDFs, images for your social campaign, decks buried in Google Drive, support tickets, customer records from Sa…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “if it's shared in or integrated into Slack, it's searchable.”

   proof ↗⚑ flag

   Microsoft Teams✓fullclaimed6/10

   Docs confirm Copilot Chat is embedded in Teams and Outlook, drawing on Microsoft Graph and Work IQ (work data) to generate AI insights/suggestions inside the product, with prompt starters to surface suggestions to users. Missing for 10: concrete detail on specific insight types (e.g., meeting summaries, action-item extraction) and independent/hands-on validation of insight quality beyond vendor docs.

   • [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
   • [claimed-docs] “Securely interact with Copilot using web data and work data (Microsoft Graph and Work IQ)”
   • [claimed-docs] “Copilot Chat in Outlook and Teams”
   • [claimed-docs] “Prompt starters”
   • [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack's Workflow Builder lets users build no-code automations with triggers (including webhook triggers from outside Slack) and conditional branching that run autonomously in the background once configured, and the Events API/CLI/Bolt frameworks let developers build bots/apps that respond to activity without manual intervention. This directly satisfies the 'autonomous background automation' story for AI-native and non-technical users alike. missing for 10: independent/hands-on verification that these automations run reliably unattended over time, and explicit AI-agent-triggered automation examples beyond marketing copy

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”
   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed5/10

   Teams' platform docs describe bots, webhooks/connectors, and Graph API automation that can post messages, create teams/channels, and react to external service events without direct real-time user interaction, which supports background-style automation. However, there is no clear documentation of persistent, autonomous AI-agent workflows (e.g., scheduled triggers, continuous background execution) beyond basic bot/connector integrations, and no independent verification of such automations running reliably unattended. Missing for 10: explicit scheduling/triggering mechanisms for autonomous agent runs, evidence of long-running background AI automation, and independent hands-on confirmation of this capability.

   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Post updates from external services to channels.”
   • [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
   • [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
   • [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
   • [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Slack✓fullclaimed7/10

   Slack ships Slackbot as a built-in AI agent that can summarize channels, prepare meeting briefs, analyze reports, answer open-ended questions, and act on tasks like updating deals or routing work to other agents (slack-docs-13,14,15,38,55,57,69). This is a native, in-product delegation capability, not just a third-party integration. Missing for 10: independent/hands-on user reports confirming Slackbot's agentic task delegation works as advertised, and more detail on the scope of actions it can autonomously perform beyond summarization/Q&A.

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Update deals just by asking Slackbot”
   • [claimed-docs] “Slackbot can now dig deep on open-ended questions, not just quick ones.”
   • [claimed-docs] “Slackbot just got a full-screen workspace built for deeper work.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”

   proof ↗⚑ flag

   Microsoft Teams✓fullclaimed7/10

   Teams docs confirm a built-in Copilot Chat assistant integrated directly in Teams and Outlook, capable of securely interacting with work/web data via Microsoft Graph, plus agent slash commands and prompt starters that let users delegate conversational tasks to it. Missing for 10: independent/hands-on evidence of successful task delegation (community evidence pack focuses on unrelated complaints/bugs, not Copilot capability), and more detail on the scope of tasks Copilot can autonomously execute vs. just answer.

   • [claimed-docs] “Copilot Chat in Outlook and Teams”
   • [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
   • [claimed-docs] “Securely interact with Copilot using web data and work data (Microsoft Graph and Work IQ)”
   • [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
   • [claimed-docs] “Prompt starters”
   • [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack ships Slackbot as an in-product AI agent that responds to natural-language requests (e.g., 'Update deals just by asking Slackbot', daily briefings, summarization, open-ended Q&A) and exposes an official MCP server so AI assistants can search, message, and manage Slack objects via natural language. This directly supports NL-command operation for AI-native users. missing for 10: independent/hands-on validation of Slackbot NL command accuracy and reliability, and clearer documentation of the scope/limits of what natural-language commands can trigger (vs. workflow builder's no-code but still menu-driven automations).

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Update deals just by asking Slackbot”
   • [claimed-docs] “Slackbot can now dig deep on open-ended questions, not just quick ones.”
   • [claimed-docs] “Slackbot just got a full-screen workspace built for deeper work.”
   • [claimed-docs] “AI agents can now read, write, and manage your Slack Lists directly.”
   • [claimed-docs] “Once connected, your AI assistant can search channels, read messages, and use real conversation context to help you build.”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity6/10

   Docs show Teams supports natural-language interaction via Copilot Chat, agent slash commands, and prompt starters (ms-teams-docs-15, ms-teams-docs-31, ms-teams-docs-37, ms-teams-docs-6, ms-teams-docs-32), giving a documented path for AI-native users to operate the product conversationally. However, this is vendor-only documentation with no independent corroboration of real-world reliability, and one community report describes a related bot (T-Bot) as 'greyed out and unusable' (ms-teams-comm-11), casting some doubt on maturity. Missing for 10: independent/hands-on validation of Copilot Chat command reliability, broader coverage beyond slash commands/prompt starters, and resolution of the T-Bot usability complaint.

   • [claimed-docs] “Securely interact with Copilot using web data and work data ([Microsoft Graph](/en-us/graph/overview-major-services) and [Work IQ]”
   • [claimed-docs] “Securely interact with Copilot using web data and work data (Microsoft Graph and Work IQ)”
   • [claimed-docs] “Copilot Chat in Outlook and Teams”
   • [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
   • [claimed-docs] “Prompt starters”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Slack—none0/10

   Slack has API method reference docs (e.g. chat.postMessage) and an OpenAPI/AsyncAPI spec repo, but there is no evidence of an interactive, runnable API reference (e.g. a Swagger/try-it console); a direct probe for openapi.json/swagger.json on the docs site returned 404s, indicating no in-browser interactive reference exists.

   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   No evidence of an interactive API reference with runnable examples; probes show llms.txt, docs-md, and openapi.json endpoints all 404, and cited docs are static reference/tutorial pages with no mention of interactive/runnable playgrounds.

   • [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://learn.microsoft.com/en-us/microsoftteams/platform/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Slack
   Slack~partialprobed6/10

   An official OpenAPI 2.0 spec for the Web API (and AsyncAPI spec for Events API) exists in the slackapi/slack-api-specs GitHub repo, satisfying the core ask of a machine-readable spec. However, live probes show the obvious/expected locations on docs.slack.dev (openapi.json, swagger.json, etc.) all 404, meaning the spec isn't directly downloadable from the primary docs site and requires knowing about a separate GitHub repo. Missing for 10: direct download link from docs.slack.dev, first-party documentation pointing users to the spec repo, and independent confirmation the spec is kept in sync with the live API.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   Teams/Graph exposes REST APIs (e.g., channel-post-messages) so an OpenAPI-style spec is a plausible ask, but the evidence pack shows explicit probe failures (404s) for openapi.json/swagger.json and no documentation page offering a downloadable machine-readable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://learn.microsoft.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://learn.microsoft.com/en-us/microsoftteams/platform/.md”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Slack
   Slack✓fullclaimed7/10

   Slack's official docs describe a 'developer sandbox' as an Enterprise org environment explicitly built to let developers 'build against all Slack features safely and securely' and 'empower teams to build without putting production at risk,' directly matching the story of testing without touching production data. However, missing for 10: independent/hands-on confirmation of the sandbox in use, clarity on whether this is available outside Enterprise plans, and detail on how it isolates AI/agent-specific testing (e.g., MCP server or bot testing) within that sandbox.

   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “Empower teams to build without putting production at risk”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   No evidence describes a sandbox/test environment isolated from production data for Teams; docs cover agent creation, toolkit CLI, provisioning, and publishing but never mention a dedicated sandbox mode or test tenant separate from live data. missing for 10: dedicated sandbox/test-tenant environment, documentation on data isolation from production, any first-party or community confirmation of safe testing without touching real data.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Slack
   Slack~partialclaimed6/10

   Slack maintains official OpenAPI specs for its Web API and a dated, running deprecation changelog with explicit migration windows (e.g., classic app deprecation date), which supports documented deprecation policy; the Web API and Events API references also show first-party API documentation. However, there's no explicit evidence of a formal API versioning scheme (e.g., v1/v2 endpoint versioning) beyond method-level docs and changelog dates. Missing for 10: explicit versioning scheme documentation, independent/community corroboration of deprecation practices being honored reliably.

   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “api.slack.com/changelog/deprecations is a running, dated log of API deprecation announcements with migration windows, e.g. "We'd like to upd…”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   While Graph API endpoints are referenced (e.g., graph-rest-1.0 versioning), no evidence pack item documents an explicit API versioning scheme or deprecation policy for Teams/Graph APIs; probes for OpenAPI specs and machine-readable docs also returned 404s. Missing for 10: documented API version lifecycle, deprecation timelines, and changelog/versioning policy pages.

   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [claimed-docs] “Send a new chatMessage in the specified channel.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://learn.microsoft.com/openapi.json, https://learn.microsoft.com/swagger.json, https://learn.mi…”

   proof ↗⚑ flag

Apps

1. team-adminInstall prebuilt integrations from an app directory or marketplace

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack explicitly advertises an App Directory with 2,600+ prebuilt apps (Salesforce, Jira, Google Drive, ChatGPT, etc.) and a help doc specifically for admins on how to add apps to a workspace. This directly matches the team-admin persona and app-platform theme. missing for 10: independent/hands-on confirmation of the admin install/approval workflow beyond the docs, and no detail on admin-specific approval controls for directory apps (only MCP client approval is mentioned).

   • [claimed-docs] “Choose from over 2,600 apps in the Slack App Directory — from Salesforce, Jira, Google Drive, ChatGPT, and more.”
   • [claimed-docs] “Add apps to your Slack workspace”
   • [claimed-docs] “Connect, simplify, and automate. Discover the power of apps and tools.”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed4/10

   Teams docs mention publishing agents/apps to Teams (ms-teams-docs-7) and built-in Connectors that let users subscribe to notifications from external web services (ms-teams-docs-30, ms-teams-docs-36, ms-teams-docs-44), implying a gallery of prebuilt integrations, but the evidence never explicitly describes a team-admin-facing app directory/marketplace (e.g., Teams Admin Center app catalog or AppSource) or an admin installation workflow. Missing for 10: explicit documentation of the Teams Admin Center app catalog/AppSource marketplace, admin approval/installation flow for prebuilt third-party apps, and independent corroboration of ease of use for admins.

   • [claimed-docs] “Publish your agents or apps in Teams”
   • [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
   • [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
   • [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”

   proof ↗⚑ flag

2. developerRegister custom slash commands that users invoke from the message box

   weight 2 · round to Microsoft Teams
   Slack—none0/10

   The evidence pack covers Slack's general app-platform tooling (CLI, Bolt frameworks, Web/Events APIs, Block Kit, Workflow Builder, MCP server) but never mentions slash commands specifically as a registrable app feature invoked from the message box.

   ⚑ flag

   Microsoft Teams✓fullclaimed7/10

   Microsoft's official developer docs explicitly document 'Agent slash commands' as a supported bot/agent capability for Teams apps, allowing developers to register custom commands invoked from the message compose box. Missing for 10: no detailed first-party walkthrough content beyond the title/reference, and no independent/hands-on developer corroboration of the feature in practice.

   • [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
   • [claimed-docs] “Agent slash commands”
   • [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”

   proof ↗⚑ flag

3. developerBuild apps with rich interactive UI inside chat — modals, buttons, and structured message layouts

   weight 2 · round to Slack
   Slack✓fullclaimed9/10

   Slack's Block Kit is explicitly documented as the JSON-based framework for building modals, messages, and tabs with the same building blocks, backed by chat.postMessage's structured 'blocks' parameter, plus SDKs (Bolt for Java/Python/JS, Node Slack SDK) and CLI tooling to build these apps. This directly matches the story of building rich interactive UI (modals, buttons, structured layouts) inside Slack chat. Missing for 10: no independent/hands-on developer corroboration of the Block Kit UI-building experience beyond first-party docs.

   • [claimed-docs] “Whether you're composing layouts for modals, messages, or tabs, the Block Kit building experience is the same — your app will be sculpting s…”
   • [claimed-docs] “A JSON-based array of structured blocks, presented as a URL-encoded string.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”
   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed7/10

   Docs confirm Teams platform supports rich in-chat UI building blocks — tabs, message extensions, message streaming, suggested actions, and bots — which are the primitives used to build modals, buttons, and structured layouts in Teams chat. However, the evidence never explicitly names 'Adaptive Cards' or 'task modules/dialogs' (the actual modal/button mechanism), and there is no independent developer corroboration of building such rich UI. Missing for 10: explicit Adaptive Cards/dialog (modal) documentation citation, hands-on developer testimony confirming ease of building interactive card UI.

   • [claimed-docs] “Tab apps](/en-us/microsoftteams/platform/tabs/what-are-tabs)”
   • [claimed-docs] “Message extensions](/en-us/microsoftteams/platform/messaging-extensions/what-are-messaging-extensions)”
   • [claimed-docs] “Message streaming](/en-us/microsoftteams/platform/bots/streaming-ux)”
   • [claimed-docs] “Message streaming ... Targeted messages ... Suggested actions ... Agent slash commands ... Emoji reactions ... Prompt starters”
   • [claimed-docs] “Tab apps”
   • [claimed-docs] “Message extensions”
   • [claimed-docs] “Message streaming”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Slack—none0/10

   Slack's Web API and MCP server document single-item actions (send one message, upload one file, create one list entry, etc.) with no documented batch/bulk endpoints or MCP tools for operating across many items in one call. Workflow Builder and automations are trigger-based, not bulk-operation mechanisms, and export tools are admin-only data dumps rather than AI-native bulk actions.

   ⚑ flag

   Microsoft Teams—none0/10

   The evidence describes individual Graph API calls (single channel message send, single team/channel creation, export APIs) and CLI commands for single agent/app packaging, but nothing documents bulk or batch operations across many items at once (e.g., batch message send, bulk channel creation, bulk data export in one call). Missing for 10: batch API support, bulk create/update endpoints, CLI bulk commands, or any documented example of operating on multiple items simultaneously.

   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team ... add the right people ... configure the team with channels, tabs, and apps.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Workflow Builder lets users define triggers, conditional branches, and webhook-based automations that fire actions on events (message posted, emoji reaction, webhook call, etc.), directly matching the story; the Events API further supports event-driven automation. missing for 10: independent/hands-on verification of workflow trigger reliability and no evidence of AI-native rule authoring beyond no-code builder.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”
   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed4/10

   Teams offers webhooks/connectors and Graph API triggers (incoming/outgoing webhooks, channel message posting) that could be wired into external automation like Power Automate, but there's no native user-facing rule engine within Teams itself for defining 'if event X then action Y' automations. missing for 10: a documented native automation/rules builder (e.g., Power Automate integration specifics), evidence of trigger-condition-action configuration UI, and independent confirmation of reliability.

   • [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
   • [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
   • [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
   • [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Slack
   Slack~partialclaimed4/10

   Slack's Workflow Builder is documented as a no-code automation tool with webhook triggers and conditional branching, which are automation-depth building blocks, but the evidence never explicitly mentions a 'scheduled' or 'recurring' trigger type for jobs/workflows. AI-native automation is described mostly around single-shot chat/AI features (summaries, briefings) rather than recurring job scheduling. missing for 10: explicit documentation of scheduled/recurring trigger type in Workflow Builder, independent confirmation of recurring automation use, and any AI-agent-specific recurring job scheduling capability.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   No evidence in the pack shows Teams supporting scheduled or recurring jobs/workflows (e.g., no mention of Power Automate/Workflows integration, cron-like triggers, or recurring automation setup) — the docs cover bots, tabs, message extensions, webhooks, and CLI tooling but nothing about recurring/scheduled automation. Missing for 10: any documentation of recurring/scheduled workflow triggers, workflow automation platform integration, or CLI/API support for scheduling jobs.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Slack—none0/10

   The evidence covers Workflow Builder's creation, branching, and webhook triggers, but nothing describes version history, change review, or rollback capabilities for workflows/automations built in Slack. The axis is applicable (automation platforms commonly offer versioning/rollback) but no supporting evidence exists.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   No evidence of any versioning, review, or rollback capability for automations/workflows in Teams; the Agents Toolkit CLI docs cover creation, provisioning, and publishing but nothing about version history, diffing, review workflows, or reverting a deployed agent/automation to a prior state.

   ⚑ flag

Ai agents

1. ai-native userAdd an AI agent as a member of a channel that participates in conversations when mentioned

   weight 3 · round drawn
   Slack✓fullclaimed7/10

   Slack's Events API lets bots/apps respond to activity in channels ('Slack calls you'), and its ecosystem explicitly supports adding AI agents like ChatGPT, Claude, and Slackbot as channel-integrated participants that act on mentions/requests (e.g. 'start using tools like ChatGPT, Claude... within your chats', 'Route work through Slackbot... routing requests to agents', 'Coding agents can now work with your whole team'). Combined with the CLI/Bolt SDKs for building bot apps that join channels, this shows the underlying capability is well supported. Missing for 10: explicit first-party documentation of the app_mention event/scope specifically triggering agent responses, and independent hands-on confirmation that a mentioned agent reliably replies in-channel.

   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “Coding agents can now work with your whole team, not just you.”
   • [claimed-docs] “Route work through Slackbot. Coordinate work by routing requests to agents and get results delivered right back into your workflow.”
   • [claimed-docs] “Easily connect agents, software, and all your apps in just a few clicks, and start using tools like ChatGPT, Claude, and Asana right within …”
   • [claimed-docs] “By connecting them to your conversations and data in Slack, agents like Agentforce, ChatGPT, Claude, Notion, Slackbot, and Writer become eve…”
   • [claimed-docs] “The Slack command-line interface (CLI) allows you to create and manage Slack apps from the command line.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Microsoft Teams✓fullclaimed7/10

   Docs confirm Teams supports bots/agents that can be added to Teams and 'initiate and participate in conversations' within channels, with quickstart guidance to 'create an agent and chat with it,' plus supporting features like slash commands and message streaming that are used for triggering agent responses in conversations. Missing for 10: explicit documentation of the @mention trigger mechanism specifically and independent/hands-on confirmation that agents behave as first-class channel members when mentioned.

   • [claimed-docs] “Quickstart: Create an agent and chat with it in Teams”
   • [claimed-docs] “Create Microsoft Teams apps with bots that can initiate and partici”
   • [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
   • [claimed-docs] “Message streaming](/en-us/microsoftteams/platform/bots/streaming-ux)”
   • [claimed-docs] “Help users get tasks done in conversations.”

   proof ↗⚑ flag

2. ai-native userHave an agent read and post channel messages through the official API using scoped tokens

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's official Web API (chat.postMessage, chat.history-type methods via OpenAPI spec covering user/bot token usage) plus scoped OAuth tokens is well documented, enabling agents to read and post channel messages programmatically; the MCP server and SDKs (Bolt, node-slack-sdk) further formalize agent access with admin-approved scopes. missing for 10: no independent hands-on developer report confirming real-world token-scoping friction or reliability at scale, and no explicit doc excerpt enumerating channel-read scopes (e.g., channels:history) alongside chat:write in one place.

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “The Slack Web API is an interface for querying information _from_ and enacting change _in_ a Slack workspace.”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “your integrated apps can search channels, send messages, and perform other Slack actions through MCP clients”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Workspace admins can approve and manage all MCP client integrations, keeping your Slack data safe.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity7/10

   Microsoft Graph API documentation confirms an app/agent can post a chatMessage to a channel (ms-teams-docs-11/21) and Teams bots/agents can participate in conversations and automate channel/team actions (ms-teams-docs-8,9,19,20,35), and export APIs allow reading channel messages (ms-teams-docs-13). This is inherently permission-scoped via Azure AD app registrations, consistent with an 'official API with scoped tokens' model. Missing for 10: explicit documentation naming OAuth scope/permission types (e.g., ChannelMessage.Send/Read.All) for this exact read+post flow, and independent hands-on confirmation that an AI agent can freely read arbitrary channel messages (community notes Graph/Azure API setup is heavier than Slack's webhooks, ms-teams-comm-11).

   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [claimed-docs] “Send a new chatMessage in the specified channel.”
   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Help users get tasks done in conversations.”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
   • [claimed-docs] “Create Microsoft Teams apps with bots that can initiate and partici”
   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”

   proof ↗⚑ flag

Bot api

1. developerPost a message into a channel with a simple incoming webhook URL

   weight 2 · round to Slack
   Slack~partialclaimed5/10

   Slack's docs evidence shows webhook-based triggers for Workflow Builder ("how to start a workflow from outside of Slack") and the chat.postMessage Web API method for sending messages, both of which can be used to post into a channel from an external system, but neither is the classic single-URL 'Incoming Webhook' integration developers commonly expect. Missing for 10: explicit documentation of the dedicated Incoming Webhooks app/URL for zero-config posting, and any hands-on confirmation that a bare webhook POST (without workflow setup or OAuth token) posts a message.

   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Sends a message to a channel.”
   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”

   proof ↗⚑ flag

   Microsoft Teams!disputedcontradicted5/10

   Docs clearly describe Incoming Webhooks as a way to post messages from external apps to a Teams channel via a webhook URL (ms-teams-docs-36, ms-teams-docs-12, ms-teams-docs-44, ms-teams-docs-30), matching the story's ask. However, hands-on community feedback contradicts the 'simple' framing, stating that real API integration with Teams 'requires the full Azure/Graph API stack unlike Slack's simple webhooks' (ms-teams-comm-11), indicating the webhook path is not as frictionless as documented. Missing for 10: independent corroboration that incoming webhook setup is as simple in practice as the docs claim, and clarity on whether legacy Incoming Webhooks/connectors remain fully supported going forward.

   • [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
   • [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
   • [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
   • [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”

   proof ↗⚑ flag

2. developerBuild a bot that receives messages and events in real time through an events API or gateway connection

   weight 3 · round to Slack
   Slack✓fullclaimed9/10

   Slack's Events API is explicitly documented to push real-time events to developer-built apps/bots via HTTP endpoint or Socket Mode, with subscription filtering, and this is complemented by SDKs (Bolt for Java, Node SDK) and quickstart guides for building bots. Missing for 10: independent hands-on developer corroboration of reliability/latency of the events pipeline beyond first-party docs.

   • [claimed-docs] “Subscribe to only the events you want; don't worry about the ones you don't need.”
   • [claimed-docs] “When you use the Events API, Slack calls you.”
   • [claimed-docs] “When you use the Events API, _Slack_ calls _you_. ... you can either use Socket Mode or you can designate a public HTTP endpoint”
   • [claimed-docs] “The Events API is a streamlined way to build apps and bots that respond to activities in Slack.”
   • [claimed-docs] “With the Events API, _Slack_ calls _you_.”
   • [claimed-docs] “Bolt for Java is a framework on the JVM that offers an abstraction layer to build Slack apps using modern platform features.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “This quickstart guide covers how to create a Slack app using the Slack CLI and the Bolt frameworks, in either Python or JavaScript.”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity6/10

   Teams supports building bots that receive messages/events, with docs covering bot creation, message streaming, slash commands, and porting Slack Bolt apps (implying event-driven bot architecture), plus webhooks/connectors for real-time notifications to channels. However, evidence never explicitly describes a dedicated 'events API' or gateway/WebSocket connection mechanism (like Slack's Events API or Socket Mode) — the Bot Framework's underlying real-time messaging endpoint mechanics aren't detailed, and one community comment notes API integration requires the full Azure/Graph stack rather than simple webhooks, adding friction. Missing for 10: explicit documentation of the real-time events/gateway protocol (e.g., Bot Framework messaging endpoint or streaming API mechanics), independent/hands-on validation of real-time event delivery reliability.

   • [claimed-docs] “Quickstart: Create an agent and chat with it in Teams”
   • [claimed-docs] “Port a Slack Bolt app to Teams”
   • [claimed-docs] “Message streaming](/en-us/microsoftteams/platform/bots/streaming-ux)”
   • [claimed-docs] “Agent slash commands](/en-us/microsoftteams/platform/agents-in-teams/agent-slash-commands)”
   • [claimed-docs] “With Outgoing Webhooks, you can send text messages from a channel to a web service.”
   • [claimed-docs] “Connectors allow users to subscribe to receive notifications and messages from your web services.”
   • [claimed-docs] “Incoming Webhooks help in posting messages from apps to Teams.”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”

   proof ↗⚑ flag

Ai notes

1. ai-native userGet AI-generated notes and recaps from meetings and huddles I attended or missed

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's docs directly claim AI note-taking for huddles (key takeaways, action items, who said what compiled at huddle end) and AI-generated channel/thread summaries and daily recaps for content missed, matching the story's core ask. Missing for 10: independent/hands-on corroboration of huddle-note accuracy or completeness, and no explicit confirmation that recaps cover 'missed' meetings specifically (recaps are framed around channels/threads more than scheduled meetings).

   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “Create time-saving automations in a few clicks, translate conversations into any language, and even use AI to take meeting notes.”
   • [claimed-docs] “translate conversations into any language, and even use AI to take meeting notes”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack. Any links, documents, and messages shared during a huddle are automatically saved once the …”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack.”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   The evidence pack contains no mention of Copilot meeting recap, AI-generated notes, or transcript summarization features for Teams meetings/huddles; it only covers bot/app platform docs, Graph APIs, webhooks, and unrelated community complaints. Missing for 10: any documentation of Copilot meeting recap/notes generation, evidence of summarizing missed meetings, or hands-on confirmation of this capability.

   ⚑ flag

Calls

1. team-adminStart an audio or video call directly from a channel or DM without leaving the app

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Huddles feature lets any user click the headphones icon in a channel/DM header to instantly start audio or video calls with screen sharing, all inside the app, and includes admin-manageable extras like AI notes and saved shared content. missing for 10: no explicit documentation of admin-specific controls/permissions for enabling or restricting huddles, and no independent hands-on corroboration beyond Slack's own marketing docs.

   • [claimed-docs] “Simply click on the headphones icon in the conversation header to start a huddle with your team.”
   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you're already working…”
   • [claimed-docs] “Bring the feeling of working side-by-side to a virtual space that lets you collaborate and co-create live.”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “If it's shared in a huddle, it's saved in Slack. Any links, documents, and messages shared during a huddle are automatically saved once the …”
   • [claimed-docs] “Emoji reactions. Colorful backgrounds. Delightful effects. In huddles, teams can express themselves to make being together even better.”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity4/10

   Docs confirm Teams delivers integrated 'calling' alongside chat and meetings (ms-teams-docs-18), and community reports reference an in-app 'join call UI' and audio/video controls during calls (ms-teams-comm-10), implying calls happen without leaving the client. However, there is no specific documentation describing the exact one-click call button from a channel or DM, nor confirmation it works reliably. Missing for 10: explicit product docs on the channel/DM call-start UI, and reliable hands-on confirmation (the only firsthand account cites bugs with call UI being broken/missing).

   • [claimed-docs] “Microsoft Teams delivers chat-based collaboration, meetings, calling, and enterprise voice features.”
   • [community] “'I've had many critical bugs, including the video on/off & audio mute button failing during calls, the join call UI being broken/missing, jo…”

   proof ↗⚑ flag

2. team-adminShare my screen during a call for live collaboration

   weight 2 · round to Slack
   Slack✓fullclaimed7/10

   Slack huddles explicitly support instant audio/video connection with screen sharing directly in the conversation, usable by any team member including admins, per first-party docs (slack-docs-33, slack-docs-66, slack-docs-18). However, missing for 10: independent/hands-on corroboration of screen-share quality or reliability, and no explicit admin-specific controls or documentation around screen sharing during calls beyond the general huddles feature description.

   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you're already working…”
   • [claimed-docs] “Huddles happen right in Slack. Instantly connect over audio or video and share screens so you can get more done where you’re already working…”
   • [claimed-docs] “Simply click on the headphones icon in the conversation header to start a huddle with your team.”
   • [claimed-docs] “Bring the feeling of working side-by-side to a virtual space that lets you collaborate and co-create live.”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity4/10

   Teams docs only vaguely reference 'meetings and calling' features without a specific citation of screen-sharing, while community hands-on reports confirm the capability exists (screen share + annotation) but describe it as slow to enable ('a good 30 seconds') and annotation mode 'gets stuck', undermining the smooth live-collaboration promise. Missing for 10: explicit first-party documentation of the screen-share feature, admin/policy controls for screen sharing, and reliability corroboration beyond the negative anecdotes.

   • [claimed-docs] “Microsoft Teams delivers chat-based collaboration, meetings, calling, and enterprise voice features.”
   • [community] “'We use zoom but are switching to teams... To my horror it was the epitome of bloat. It essentially takes a screenshot of the presenters des…”
   • [community] “Complaint list: no ability to link to conversations, inconsistent UI between channels and direct chats (no threading/code blocks in DMs), no…”

   proof ↗⚑ flag

External collaboration

1. team-adminCollaborate with external partners through guest accounts or shared channels with limited access

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack contains no mention of guest accounts, Slack Connect, or shared/external channels with limited access — nothing about admin controls for external collaboration appears anywhere in the docs, community, or probe items. This is a mainstream, applicable capability for a workspace chat product, but absence of evidence means it cannot be credited.

   ⚑ flag

   Microsoft Teams—none0/10

   The evidence pack contains no mention of guest accounts, external access controls, or shared channels for cross-organization collaboration — it focuses entirely on bots, agents, APIs, webhooks, and app development. Missing for 10: any documentation of guest account provisioning, external user permissions, shared/B2B channels, or admin controls governing external partner access.

   ⚑ flag

Messaging model

1. team-adminOrganize conversations into public and private channels with membership controls

   weight 3 · round to Microsoft Teams
   Slack—none0/10

   The evidence pack focuses almost entirely on Slack's AI/MCP tooling, developer SDKs, huddles, and integrations, with no first-party documentation describing channel creation, public vs. private channel types, or admin membership controls. The only channel-related mentions (e.g., MCP 'search channels', a raw SEO keyword list) do not document this admin capability.

   ⚑ flag

   Microsoft Teams~partialclaimed3/10

   Evidence confirms Teams channels exist and can be created/configured via Graph API (ms-teams-docs-8, ms-teams-docs-35, ms-teams-docs-43), implying channel-based organization, but nothing explicitly documents public vs. private channel types or membership/access controls for admins. Missing for 10: explicit documentation of public/private channel distinction, membership management APIs or admin UI, and any independent confirmation of these controls working as described.

   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team ... add the right people ... configure the team with channels, tabs, and apps.”

   proof ↗⚑ flag

2. team-adminReply in threads so side discussions stay attached to the original message

   weight 3 · round to Microsoft Teams
   Slack~partialcommunity3/10

   No first-party Slack documentation in this evidence pack describes the threading/reply feature directly; the only evidence that threads exist comes from community complaints (comm-12, comm-14) confirming the feature is used but describing it as poorly notified, hard to find replies, and 'close to impossible to use' as a tiny side panel with missing capabilities (snippets/files/slash commands not working in threads). This suggests threads function but with real UX friction, not a clean full delivery. Missing for 10: official docs/screenshots describing thread-reply UX, independent confirmation that reply notifications and thread views work smoothly, and resolution of the cited usability complaints.

   • [community] “My biggest pain point is Slack's awful implementation of threads - you only get notified of new thread replies in a 'New Threads' view that …”
   • [community] “Zulip is a very good fit for open source communities, and much much better for communication than Slack. Slack encourages saying everything …”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity4/10

   Teams channels do support conversation threads (implied by generic docs about conversations and channel messaging, e.g. ms-teams-docs-9, ms-teams-docs-11), but the evidence pack lacks any first-party documentation specifically describing 'reply in thread' functionality, and multiple community reports call out threading as confusing or poorly implemented ('the biggest issue was the threading; it truly beggars belief', 'no threading... inconsistent UI', 'took me long to realise... to follow along the threads'). Missing for 10: explicit product docs/UI walkthrough of thread-reply feature, and independent confirmation that threading works smoothly rather than being a pain point.

   • [claimed-docs] “Help users get tasks done in conversations.”
   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [community] “Complaint list: no ability to link to conversations, inconsistent UI between channels and direct chats (no threading/code blocks in DMs), no…”
   • [community] “'Teams is horribly unintuitive to use. The UI is much worse than Slack. Took me long to realise I was looking at the chat window and to foll…”
   • [community] “'My team hated it, I tolerated it... The biggest issue was the threading; it truly beggars belief... Moving (and paying) for Slack was the b…”

   proof ↗⚑ flag

3. team-adminCatch up on busy channels efficiently because every conversation is organized under a named topic or thread

   weight 2 · round to Slack
   Slack!disputedcontradicted5/10

   Slack does support channel/thread organization plus AI features to summarize channels and threads for catching up (slack-docs-15, slack-docs-19, slack-docs-34), but concrete hands-on community reports say the thread implementation itself is poorly organized and hard to use — notifications don't auto-update, threads are 'a tiny section off to the side,' and Slack 'encourages saying everything in the main channel' rather than threads (slack-comm-12, slack-comm-14). This directly contradicts the premise that conversations are cleanly organized under threads for efficient catch-up. Missing for 10: independent verification that threading/summarization actually resolves the catch-up problem in practice, admin-specific tooling for enforcing thread discipline.

   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [community] “My biggest pain point is Slack's awful implementation of threads - you only get notified of new thread replies in a 'New Threads' view that …”
   • [community] “Zulip is a very good fit for open source communities, and much much better for communication than Slack. Slack encourages saying everything …”

   proof ↗⚑ flag

   Microsoft Teams!disputedcontradicted3/10

   Docs confirm Teams channels exist and can be organized with channels/tabs (ms-teams-docs-8, ms-teams-docs-35, ms-teams-docs-43), implying topic-based organization, but hands-on community reports directly contradict effective thread/topic organization: 'The biggest issue was the threading; it truly beggars belief' and no ability to link to conversations, with 'inconsistent UI between channels and direct chats (no threading/code blocks in DMs)' and users confused distinguishing chat vs threads. Missing for 10: first-party documentation specifically describing named-topic thread organization, and any hands-on evidence that threading actually helps admins catch up efficiently.

   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team ... add the right people ... configure the team with channels, tabs, and apps.”
   • [community] “'My team hated it, I tolerated it... The biggest issue was the threading; it truly beggars belief... Moving (and paying) for Slack was the b…”
   • [community] “Complaint list: no ability to link to conversations, inconsistent UI between channels and direct chats (no threading/code blocks in DMs), no…”
   • [community] “'Teams is horribly unintuitive to use. The UI is much worse than Slack. Took me long to realise I was looking at the chat window and to foll…”

   proof ↗⚑ flag

Notifications

1. team-adminTune notifications per channel, keyword, and schedule so only what matters interrupts me

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack contains no documentation on per-channel/keyword/schedule notification preferences (e.g., mute channels, keyword alerts, do-not-disturb scheduling) — Slack's actual notification settings are not represented anywhere in this pack, only unrelated AI, workflow, MCP, and integration docs. Missing for 10: any mention of notification preferences, keyword alerts, per-channel mute/schedule controls, or admin-level notification policy tools.

   ⚑ flag

   Microsoft Teams—none0/10

   No evidence in the pack documents per-channel, keyword, or schedule-based notification tuning; the only related community evidence explicitly says users 'can't seem to unsubscribe' and that muting notifications is 'impossible' even with settings turned off. missing for 10: any docs on channel-level notification settings, keyword alerts, or scheduled quiet hours.

   • [community] “'MS have not implemented muting as a feature... you can't unsubscribe yourself... Unavoidable alerts that any idiot on any channel can annoy…”
   • [community] “'My biggest grief with Teams is that it's impossible to shut off notifications. With pretty much everything turned off... it still blinks th…”

   proof ↗⚑ flag

Compliance

1. platform-engineerReview audit logs of admin and user actions across the workspace

   weight 2 · round drawn
   Slack—none0/10

   The evidence pack includes only workspace data export/import documentation (e.g., slack-docs-22/23/35/36) and community complaints about export restrictions (slack-comm-2), but nothing that documents an audit log capability tracking admin and user actions across the workspace. This is a fair and applicable axis for an enterprise collaboration platform, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   The evidence pack includes Teams Export APIs for exporting chat/channel messages, but nothing documents an audit log of admin and user actions across the workspace (e.g., admin center audit trail, sign-in/action logs). This is an applicable enterprise-compliance axis for a SaaS collaboration platform, but no evidence demonstrates it. Missing for 10: any documentation of an audit log feature, admin action tracking, or audit log search/export API distinct from content export.

   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”

   proof ↗⚑ flag

2. platform-engineerEnforce message retention policies and legal holds for compliance and eDiscovery

   weight 2 · round to Microsoft Teams
   Slack—none0/10

   The evidence pack shows generic data export/import guides (slack-docs-22/23/35/36) and a community note that Corporate Export requires legal/compliance justification and Slack approval (slack-comm-2), but nothing documents actual retention-policy enforcement, legal-hold placement, or eDiscovery tooling. Missing for 10: retention policy configuration, legal hold mechanism, eDiscovery search/export APIs, admin documentation on compliance holds.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed3/10

   The evidence only covers Teams Export APIs for retrieving 1:1, group, meeting, and channel messages (including deleted messages up to 21 days) for eDiscovery-style export, but there is no documentation of retention policy configuration, legal hold mechanisms, or Purview-based compliance controls referenced in this pack. Missing for 10: retention policy documentation, legal hold configuration/enforcement details, and independent/hands-on confirmation of compliance workflows.

   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”

   proof ↗⚑ flag

Exports

1. team-adminExport the full message history of my workspace in machine-readable formats, including private conversations where policy allows

   weight 3 · round to Microsoft Teams
   Slack!disputedcontradicted5/10

   Slack does document official export tools for workspace data (slack-docs-22/23/35/36), which nominally support the compliance-export story, but community evidence directly contradicts free/easy access: Corporate Export of DMs and private channels requires legal/compliance justification and Slack's approval, and users questioned whether migrating years of full message history out of Slack is even feasible under these restrictions. Missing for 10: no first-party documentation of a machine-readable format spec (JSON/CSV schema details), no evidence addressing the approval-gate friction, and no independent confirmation that large-scale/private-channel exports actually work in practice.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed6/10

   Microsoft documents Teams Export APIs that allow admins to export 1:1, group chat, meeting chats, and channel messages, including recovering deletions within 21 days, which directly supports machine-readable compliance exports. However, evidence does not confirm formats, full scope of 'all private conversations where policy allows', eDiscovery integration details, or independent/hands-on verification. Missing for 10: documentation of specific export file formats/schema, confirmation of full coverage of private chats beyond examples, independent or hands-on validation of the export process, and details on policy-based access controls governing what admins can export.

   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Slack
   Slack~partialprobed6/10

   Slack ships an extensive Web API (200+ methods per slack-docs-74), an Events API, official OpenAPI/AsyncAPI specs (slack-supp-openapi-spec), a CLI, SDKs, and an MCP server covering messaging, search, canvases, lists, and file uploads (slack-docs-8, slack-docs-28-30, slack-docs-48). However, community evidence shows a concrete gap: exporting DMs and private channel content requires legal/compliance justification and Slack approval, not open self-serve API access (slack-comm-2, slack-comm-4), and moderation tooling is described as 'purposefully useless' compared to UI expectations (slack-comm-9). Missing for 10: verified parity for admin/compliance-only UI actions (e.g., full data export, moderation controls) via API, and a public discoverable OpenAPI schema (probe shows standard openapi.json paths 404, slack-probe-2).

   • [claimed-docs] “The Slack Web API is an interface for querying information from and enacting change in a Slack workspace.”
   • [claimed-docs] “Send data to or query data from Slack using any of more than 200 methods.”
   • [claimed-docs] “Official slackapi/slack-api-specs repo: "This repository contains API specifications of Slack platform features and APIs... You'll find Open…”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”
   • [claimed-docs] “Sends a message to a channel.”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”
   • [community] “I think 'less capable moderation tools' really undersells how purposefully useless and nonexistent Slack's moderation tools are for open com…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.slack.dev/openapi.json, https://docs.slack.dev/swagger.json, https://docs.slack.dev/api…”

   proof ↗⚑ flag

   Microsoft Teams~partialcommunity5/10

   Microsoft Graph and the Bot/Agents Toolkit expose substantial programmatic control—creating teams/channels, posting messages, managing webhooks, exporting chats, and building agents/bots/tabs—but this is a broad SDK/app-extension surface, not a documented 1:1 API mirror of every UI action (e.g., meetings/calls, reactions, threading UI). A community report also notes API integration requires the full Azure/Graph stack, unlike simpler alternatives, indicating friction rather than seamless UI-API parity. Missing for 10: explicit API coverage for meeting/calling controls and other real-time UI actions, and independent verification that all UI capabilities are exposed via API.

   • [claimed-docs] “These apps can also automate creating teams, channels, and conversations, enhancing the value of Microsoft Teams.”
   • [claimed-docs] “Send a new [chatMessage](resources/chatmessage?view=graph-rest-1.0) in the specified [channel](resources/channel?view=graph-rest-1.0).”
   • [claimed-docs] “You can create websites, services, and native platform applications that run outside the Microsoft Teams user experience, and call the Teams…”
   • [claimed-docs] “Use Microsoft Graph to create a new virtual team when a new business issue arises, add the right people to the team, and configure the team …”
   • [claimed-docs] “Webhooks and connectors help to connect the web services to channels and teams in Microsoft Teams.”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Microsoft Teams
   Slack!disputedcontradicted4/10

   Slack documents a workspace data export feature (slack-docs-22/23/35/36), but concrete community evidence shows this is heavily restricted in practice: Corporate Export of DMs/private channels requires legal/compliance justification and Slack's approval (slack-comm-2), users openly question whether multi-year history can even be exported (slack-comm-4), and Slack has shut down open-protocol (IRC/XMPP) access that once enabled third-party/portable access (slack-comm-11). There's no evidence the export format is genuinely open/interoperable rather than a locked-down archive. Missing for 10: documented open export format specification, independent confirmation of unrestricted self-service export, and no contradicting reports of approval gating.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”
   • [community] “Slack decided to close down IRC and XMPP gateways, ending third-party client access via open protocols; the IRC gateway was the only thing t…”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed4/10

   Microsoft documents Teams Export APIs that let (typically admin/compliance) users export 1:1, group, meeting, and channel chat content, including recently deleted messages — showing some data portability exists. However, this is framed as a compliance/eDiscovery tool rather than a self-service 'export everything and leave' flow, and no evidence specifies open, non-proprietary formats or a full account/data export including files, calendar, and settings. Missing for 10: explicit open-format guarantee (e.g., JSON/CSV/mbox), self-service full account export for ordinary end-users, and confirmation of completeness (files, contacts, calendar) beyond chat messages.

   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Slack—none0/10

   Slack is closed-source proprietary SaaS; no evidence of any open-licensed source code release. Its CLI, MCP server, and APIs are tools around a closed core, not the product's source itself.

   ⚑ flag

   Microsoft Teams—none0/10

   Microsoft Teams is closed-source proprietary software; no evidence in the pack indicates any open-license source availability, and the axis clearly applies since the story concerns openness of source code.

   ⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Slack—none0/10

   Slack is a cloud SaaS product; the evidence pack shows only hosted/cloud offerings, developer sandboxes, CLI, SDKs, and export tools—no self-hosted deployment option is documented anywhere, and community evidence even discusses difficulty exporting data or migrating off Slack's hosted service.

   • [claimed-docs] “A developer sandbox is an Enterprise org environment (a network of two or more Slack workspace instances) that can be used to build against …”
   • [claimed-docs] “A developer sandbox is an Enterprise org environment ... that can be used to build against all Slack features safely and securely, without a…”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   Microsoft Teams is a proprietary SaaS cloud service with no evidence of a self-hostable core product; all evidence describes cloud-hosted collaboration, extensibility via bots/tabs/connectors, and Azure-hosted app deployment, not self-hosting the Teams service itself.

   • [claimed-docs] “Microsoft Teams delivers chat-based collaboration, meetings, calling, and enterprise voice features.”
   • [claimed-docs] “Resource Provisioning and Deployment: Provision necessary cloud resources and deploy your application to Azure.”

   proof ↗⚑ flag

Pricing

1. team-adminKeep my team on a free tier without losing access to older message history

   weight 2 · round to Slack
   Slack!disputedcontradicted4/10

   Slack marketing claims 'Unlimited message history' (slack-docs-43), but this benefit is documented on the pricing page and is know to apply to paid tiers, and multiple community reports concretely describe free workspaces having message/storage limits enforced, with older messages disappearing once a few thousand messages are exceeded (slack-comm-10, slack-comm-15). This directly contradicts the idea that a team-admin can stay on a free tier indefinitely without losing history. Missing for 10: an explicit first-party statement about free-tier retention limits, and any first-party pricing-page confirmation that free tier does NOT purge history.

   • [claimed-docs] “Unlimited message history Every message, file, and conversation shared in Slack is saved and fully searchable.”
   • [community] “So much information that would reduce support burdens is buried in Slacks and Discords. It can't be found through Google, and if you aren't …”
   • [community] “I have like 7 Slacks, 2 paid and 5 hobby ones I use once a month. Slack pushing storage/message limits on free workspaces feels like a tiny …”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   No evidence in the pack addresses free-tier message history retention policies, retention limits, or admin controls for preserving history without upgrading; the pack covers bots, agents, APIs, webhooks, and general complaints, none of which touch pricing-tier history retention.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Slack—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic data controls for Slack; the evidence covers MCP servers, APIs, workflows, and AI features but nothing about choosing where data is stored. This is a fair axis for an enterprise SaaS product, but absence of evidence means it cannot be credited.

   ⚑ flag

   Microsoft Teams—none0/10

   No evidence in the pack addresses data residency, regional storage options, or geo-controls for Teams data; all evidence concerns app development, messaging features, or unrelated reliability/security complaints.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Slack—none0/10

   No evidence in the pack addresses AI training data opt-out or controls preventing Slack/customer data from being used to train AI models; the pack covers unrelated AI features (search, summarization, MCP server) and export/pricing controversies but nothing about AI-training data usage or opt-out settings.

   ⚑ flag

   Microsoft Teams—none0/10

   No evidence in the pack addresses opt-out or controls for AI/model-training use of Teams data; docs cover bots, agents, webhooks, and Copilot features but nothing about training-data exclusion or privacy controls for AI training.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Microsoft Teams
   Slack!disputedcontradicted3/10

   Slack documents workspace export/import tools (data retention/deletion-adjacent controls), but community evidence explicitly says business customers can't freely export their own chats — Corporate Export requires legal/compliance justification and Slack's approval, and even feasibility of full history export is questioned. This directly contradicts the notion of straightforward user/admin control over data retention and deletion. Missing for 10: explicit documentation of configurable retention periods, deletion policies/workflows, and independent confirmation that exports/deletions can be self-served without gatekeeping.

   • [claimed-docs] “Export your workspace data | Slack”
   • [claimed-docs] “Guide to Slack import and export tools | Slack”
   • [claimed-docs] “Guide to Slack import and export tools”
   • [claimed-docs] “Export your workspace data”
   • [community] “Wow, Slack does not allow business customers to export their chats freely. Corporate Export requires legal/compliance justification and Slac…”
   • [community] “Is it even possible to migrate 10 years of message history out of Slack? Users questioned whether such an export was even feasible given Sla…”

   proof ↗⚑ flag

   Microsoft Teams~partialclaimed3/10

   Teams' Graph docs mention export APIs and note that user-deleted messages remain recoverable for 21 days, showing some retention/deletion behavior exists, but there is no evidence of AI-native controls (e.g., agent-specific data retention settings, deletion APIs for AI interactions, or admin policies tailored to AI usage). Missing for 10: explicit AI/agent data retention controls, user-facing deletion tools, and documentation on how AI interaction data (e.g., Copilot logs) is retained or purged.

   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Slack—none0/10

   No evidence in the pack addresses telemetry or usage-tracking opt-out controls for Slack; the privacy/data-export items (slack-comm-2, slack-docs-22/23/35/36) relate to data export/retention, not telemetry opt-out. This axis plausibly applies to a SaaS collaboration product, but no supporting capability is documented.

   ⚑ flag

   Microsoft Teams—none0/10

   No evidence in the pack addresses telemetry opt-out or usage-tracking controls for AI-native users; the documentation excerpts cover app/agent building, messaging, webhooks, and CLI tooling, with no mention of privacy/telemetry settings. Missing for 10: any documentation of a telemetry opt-out mechanism, admin controls for usage tracking, or AI-specific data collection settings.

   ⚑ flag

Ai catchup

1. ai-native userGet AI-generated summaries and recaps of channels and threads I missed

   weight 2 · round to Slack
   Slack✓fullclaimed8/10

   Slack's first-party AI features docs explicitly state AI in Slack can summarize channels and threads and serve daily recaps (slack-docs-15), backed by Slackbot as an intelligent daily briefing/agent (slack-docs-13, slack-docs-14) and huddle note-taking/recaps (slack-docs-19, slack-docs-34). This directly matches the story of AI-generated summaries/recaps of missed channels/threads. Missing for 10: independent/hands-on verification of summary quality or accuracy, and no community evidence corroborating real-world reliability of this specific feature (community evidence pack focuses on unrelated pain points like pricing/export/threads UX).

   • [claimed-docs] “Today is your new intelligent briefing that signals what needs your attention based on your priorities.”
   • [claimed-docs] “Slackbot is your personal AI agent in Slack that understands you and your workspace, helping you prepare for upcoming meetings, analyze repo…”
   • [claimed-docs] “AI in Slack can summarize channels and threads and serve up daily recaps, giving you the information you need to stay organized and in the k…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”
   • [claimed-docs] “AI in Slack keeps you focused on the conversation by taking notes for you. Key takeaways, action items, and who said what are all neatly org…”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   The evidence pack contains only general platform/bot/webhook/API docs and community complaints, with no mention of AI-generated channel/thread summaries or 'catch-up' recap features (e.g., Copilot's recap capability is not cited here); nothing ties Copilot or any feature to summarizing missed conversations. Missing for 10: any documentation of a summarization/recap feature for channels or threads, independent verification of its use.

   ⚑ flag

Search

1. team-adminSearch the full message history with filters like sender, channel, and date

   weight 3 · round to Slack
   Slack~partialclaimed6/10

   Slack docs confirm full, unlimited searchable message history (slack-docs-43, slack-docs-16/52) and Slack's native search supports filtering, but the evidence pack does not explicitly document admin-specific advanced search operators (from:, in:, before:/after:) or an admin-console-level cross-workspace search UI beyond general user search claims; the MCP server also offers 'searching through Slack' but is a separate API-driven tool rather than the admin search UI itself. missing for 10: explicit documentation of native in-app search filter syntax (sender/channel/date), evidence of admin-level search scope (e.g. Enterprise-wide search across workspaces), and independent/hands-on confirmation of filter functionality.

   • [claimed-docs] “Unlimited message history Every message, file, and conversation shared in Slack is saved and fully searchable.”
   • [claimed-docs] “Conversations with coworkers, PDFs, images for your social campaign, decks buried in Google Drive, support tickets, customer records from Sa…”
   • [claimed-docs] “if it's shared in or integrated into Slack, it's searchable.”
   • [claimed-docs] “The Slack MCP server provides tools for searching through Slack, retrieving and sending messages, managing canvases, managing users, uploadi…”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   The evidence pack contains no vendor documentation of an admin-facing search feature with sender/channel/date filters — only generic Export APIs for compliance extraction (ms-teams-docs-13,14), which do not describe search/filter UI. Community reports explicitly complain that Teams search cannot filter Files by type or search within a channel and results can't be sorted (ms-teams-comm-11) and that 'search is abysmal' (ms-teams-comm-8), reinforcing the lack of evidence for this capability.

   • [claimed-docs] “Teams Export APIs allow you to export 1:1, group chat, meeting chats, and channel messages from Microsoft Teams.”
   • [claimed-docs] “Messages deleted by users from the Teams client can be accessed using export APIs up to 21 days from the time of deletion.”
   • [community] “Long complaint list: can't filter Files by type or search within a channel, search results can't be sorted except by date modified, T-Bot ch…”
   • [community] “Detailed complaint: search is abysmal, messages go missing in 1:1 chats, images fail to display, notifications get lost, and the app window …”

   proof ↗⚑ flag

Workflow builder

1. team-adminBuild no-code workflows triggered by events, schedules, or form submissions inside the chat tool

   weight 3 · round to Slack
   Slack✓fullclaimed8/10

   Slack's Workflow Builder is documented as a no-code way to build workflows directly in Slack, supporting event/schedule/form-submission triggers, webhook triggers, and conditional branching. missing for 10: independent/hands-on corroboration of the builder in use, and detail on schedule-based triggers specifically beyond webhook/event mentions.

   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack. Any user can combine a limited set of steps and triggers to quickly se…”
   • [claimed-docs] “Webhook triggers for workflows - How to start a workflow from outside of Slack.”
   • [claimed-docs] “Add a branch to a workflow - How to add conditional branching that will present users with different options based on their interaction with…”
   • [claimed-docs] “Workflow Builder is a no-code way to build workflows, right in Slack.”
   • [claimed-docs] “Webhook triggers for workflows”
   • [claimed-docs] “Add a branch to a workflow”

   proof ↗⚑ flag

   Microsoft Teams—none0/10

   Evidence pack covers developer-oriented bots, connectors, webhooks, and the Agents Toolkit CLI, all of which require coding/deployment rather than a no-code, admin-facing workflow builder triggered by events/schedules/forms; there is no mention of a no-code automation surface (e.g., Power Automate/Workflows app) inside Teams chat.

   ⚑ flag