Microsoft Teams vs Zulip

Agent access

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

   weight 2 · round to Zulip
   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

   Zulip~partialprobed3/10

   No llms.txt exists (confirmed 404) and other agent-friendly doc endpoints (openapi.json, docs.md) also 404 on the primary domain, but Zulip does publish a full machine-readable OpenAPI spec in its GitHub repo that an agent could be pointed at to understand the API surface. This is a weak substitute for a true llms.txt/agent-docs entry point. Missing for 10: an actual llms.txt file, any officially surfaced agent-oriented documentation page, and discoverability of the OpenAPI spec from the main docs site rather than only via GitHub raw.

   • [probe] “PROBE llms.txt: HTTP 404 at https://zulip.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://zulip.com/api/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://zulip.com/openapi.json, https://zulip.com/swagger.json, https://zulip.com/api/openapi.json, …”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”

   proof ↗⚑ flag

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

   weight 2 · round to Zulip
   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

   Zulip~partialprobed6/10

   Zulip ships a documented REST API (OpenAPI spec verified live), a keyless-working API endpoint, and an official Python CLI (zulip-send) that installs via pip and runs headlessly from scripts, supporting basic CI automation like sending messages. However, there's no evidence of first-class CI/CD integration patterns, GitHub Actions examples, containerized headless server mode, or broader automation tooling beyond bots/webhooks. missing for 10: CI-specific documentation or examples, containerized/headless deployment guidance for automation pipelines, evidence of use in real CI workflows.

   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”
   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Zulip—none0/10

   Zulip is a chat platform, so publishing an official MCP server to let AI agents connect is a plausible axis, but no evidence pack item mentions MCP at all — only bots, webhooks, REST API, and OpenAPI spec are documented. missing for 10: any mention of an MCP server (official or community), MCP protocol support, or agent-connection tooling beyond generic bots/API.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Microsoft Teams
   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

   Zulip~partialprobed6/10

   Hands-on evidence confirms an official 'zulip-send' CLI installs via PyPI and runs headlessly for scripting message sends, which supports agentic/automation use cases. However, the evidence pack shows no broader CLI feature set (e.g., reading messages, managing channels, bots) beyond sending, and no first-party docs elaborating CLI capabilities beyond the probe. Missing for 10: documented full CLI command reference, evidence of read/administrative CLI operations, and independent community corroboration of CLI use in agentic workflows.

   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

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

   weight 3 · round to Zulip
   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

   Zulip✓fullprobed9/10

   Zulip publishes a documented REST API (zulip.com/api) backed by a full OpenAPI 3.0 spec in its repo, verified live against a public server responding to documented endpoints, plus an official Python CLI (zulip-send) installable via pip for scripting/automation. This directly supports an AI-native user driving the product programmatically. Missing for 10: no discoverable llms.txt or machine-readable docs endpoint for LLM consumption, and no independent third-party corroboration beyond hands-on probes.

   • [claimed-docs] “Send a message”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   Zulip documents bot accounts and API keys for automation, but no evidence shows a mechanism for issuing scoped or least-privilege credentials (e.g., restricted permission bots, granular API scopes) specifically for AI agents — bots appear to get a single API key without documented fine-grained access controls.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Zulip
   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

   Zulip✓fullprobed8/10

   Zulip ships an official Python SDK/CLI installable via PyPI (pip install zulip) with hands-on verified functionality (zulip-send), a full machine-readable OpenAPI 3.0.1 spec covering the REST API, and a live documented REST API confirmed working on a public server. This directly satisfies building against official SDKs for an AI-native/agentic workflow. Missing for 10: no evidence of SDKs in other languages (JS/Node, Go, etc.), no llms.txt or dedicated agent-facing docs, and no independent third-party corroboration of SDK quality beyond the hands-on probe.

   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”
   • [claimed-docs] “Send a message”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Microsoft Teams
   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

   Zulip—none0/10

   Evidence only shows Zulip supports *incoming* webhooks for pushing external events into Zulip (zulip-docs-19) and a bot framework for reacting to messages (zulip-docs-4/12/24), but nothing documents an outgoing webhook mechanism for an AI-native user to subscribe to Zulip's own events. missing for 10: documentation of outgoing/subscription webhooks, event-type configuration, or webhook payload schema for external consumers.

   • [claimed-docs] “Incoming webhooks”
   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Microsoft Teams
   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

   Zulip—none0/10

   No evidence of any AI-generated insights, summarization, or suggestion features surfaced within Zulip itself; evidence covers topics, channels, search, bots (rule-based), integrations, and hosting/export, none of which involve AI analysis of data. Missing for 10: any AI summarization/insight feature, AI-generated suggestions, or documented AI assistant surfaced in the product UI.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Zulip~partialprobed5/10

   Zulip supports bots that run autonomously in the background via its bot API framework and Botserver for production deployment, plus a full REST/OpenAPI API and CLI tools for scripting automations. However, this is a general chatbot/integration framework rather than an AI-native agentic automation platform with built-in scheduling, triggers, or autonomous task orchestration. Missing for 10: evidence of AI-specific agent orchestration, native scheduling/triggering beyond message-reactive bots, and independent hands-on validation that bots run reliably unattended in production.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

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

   weight 3 · round to Microsoft Teams
   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

   Zulip—none0/10

   Zulip's evidence covers bots/integrations built by users via its API, but there is no mention of a built-in AI assistant that users can delegate tasks to directly within the product.

   ⚑ flag

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

   weight 2 · round to Microsoft Teams
   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

   Zulip—none0/10

   Zulip's docs describe channels, topics, search filters, and a bot API for building reactive bots, but none of this constitutes an AI-native natural-language command interface for operating the product itself — no evidence of NLU-driven commands, AI assistant, or agentic control layer. missing for 10: any natural-language command parsing/interface, AI assistant for operating Zulip, evidence of NL-driven actions beyond keyword search filters.

   • [claimed-docs] “channel:design has:image new logo: Search for messages in #design that include an image and contain the keywords new and logo.”
   • [claimed-docs] “Zulip also offers a wide array of search filters, which can be used on their own, or in combination with keywords.”
   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Zulip
   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

   Zulip~partialprobed5/10

   Zulip publishes a full machine-readable OpenAPI 3.0 spec for its REST API (zulip-probe-5) and a public API reference site with example endpoints like 'Send a message' (zulip-docs-5), and the API is confirmed live and functional hands-on (zulip-probe-4). However, there is no direct evidence that the API reference page itself offers interactive 'try it out' runnable examples in-browser rather than just documented curl/code snippets. Missing for 10: explicit confirmation of an in-browser interactive/try-it console on the API docs, independent user reports of using runnable examples.

   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”

   proof ↗⚑ flag

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

   weight 2 · round to Zulip
   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

   Zulip✓fullprobed9/10

   Zulip's REST API ships a machine-readable OpenAPI 3.0.1 spec (zulip.yaml, ~1.5MB) directly in its repo, confirmed hands-on, and the live API docs at zulip.com/api/ are generated from this spec. Missing for 10: no dedicated discoverable download link/endpoint on the main docs site itself (openapi.json probes 404'd, so it's not trivially discoverable without knowing the GitHub path).

   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi: all candidate paths 404 (https://zulip.com/openapi.json, https://zulip.com/swagger.json, https://zulip.com/api/openapi.json, …”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   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

   Zulip—none0/10

   The evidence pack covers self-hosting, export/import, integrations, and API access, but nowhere mentions a dedicated sandbox, staging, or test-mode instance that is separate from production data. Nothing describes a way to safely test bots/integrations against non-production data without standing up and fully configuring an entirely separate self-hosted server.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   While Zulip clearly has a documented, machine-readable REST API (OpenAPI spec, live endpoint, CLI) per zulip-docs-5, zulip-probe-4/5/6, the evidence pack contains no mention of API versioning scheme or a deprecation policy for changed/removed endpoints. Missing for 10: documentation of API version numbers, backward-compatibility guarantees, or a deprecation/changelog process.

   ⚑ flag

Apps

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

   weight 3 · round to Zulip
   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

   Zulip✓fullclaimed7/10

   Zulip provides an official integrations directory (zulip.com/integrations) listing 130+ native prebuilt integrations plus Zapier/IFTTT for hundreds more, which team-admins can browse and install/configure (e.g., via incoming webhooks) without custom coding. missing for 10: no evidence of an in-app 'install with one click' marketplace UI or independent hands-on confirmation of the install flow.

   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Over 130 native integrations.”
   • [claimed-docs] “Incoming webhooks”

   proof ↗⚑ flag

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

   weight 2 · round to Microsoft Teams
   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

   Zulip—none0/10

   Zulip's docs describe an interactive-bot framework that reacts to messages, but there is no evidence of a slash-command registration API or mechanism where a developer registers a custom command invoked via '/' in the message box, distinct from Slack-style slash commands.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”

   proof ↗⚑ flag

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

   weight 2 · round to Microsoft Teams
   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

   Zulip—none0/10

   Evidence covers Zulip's bot/API framework, integrations, and messaging features but contains no mention of interactive UI elements like modals, buttons, or structured message layouts within chat (unlike Slack's Block Kit or similar). Missing for 10: any documentation of interactive message components, modal dialogs, button widgets, or structured layout building blocks for developers.

   ⚑ flag

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   While Zulip exposes a full REST API and CLI tooling (zulip-probe-5, zulip-probe-6, zulip-docs-5) that could theoretically be scripted, the evidence pack contains no documentation or hands-on proof of a bulk/batch endpoint (e.g., mass message updates, bulk channel management, batch subscribe/unsubscribe) that lets an AI-native user act on many items in one call. missing for 10: documented bulk-update/bulk-delete/batch endpoints, evidence of batch request support, any example of operating on multiple items in a single API call.

   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Zulip~partialclaimed4/10

   Zulip has no documented native rules/automation engine; the closest capabilities are a bot framework requiring custom code (zulip-docs-4/12/24) and webhook/Zapier/IFTTT integrations (zulip-docs-9/19) that let external tools trigger actions on Zulip events. This is automation via third-party glue or coding, not a built-in 'define rules' feature. Missing for 10: a native no-code rules/trigger builder, first-party documentation of event-condition-action automation, and any evidence of it working out-of-the-box without external services or custom bot code.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Incoming webhooks”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   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

   Zulip—none0/10

   Zulip is a team chat platform with bots, integrations, and an API for sending messages, but there is no evidence of any scheduler, cron-like feature, or recurring workflow/job automation capability — only reactive bots and one-off messages are documented.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [claimed-docs] “Send a message”

   proof ↗⚑ 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 to Microsoft Teams
   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

   Zulip~partialprobed6/10

   Zulip's documented bot framework lets you write and run custom bots (including via a dedicated Botserver for production) that 'react to messages,' and the full REST/API surface (confirmed live and via OpenAPI spec) supports sending/receiving messages, which is the technical substrate needed for an AI-agent-as-channel-member use case. However, this requires custom bot development rather than a first-party 'add an AI agent to a channel' feature, and there's no explicit documentation or evidence of native @-mention-triggered AI agent participation out of the box. Missing for 10: explicit first-party AI-agent bot support (vs generic bot framework), documentation of mention-triggered behavior specifically, and independent/hands-on confirmation of an AI agent actually participating in a channel conversation.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”

   proof ↗⚑ flag

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

   weight 3 · round to Zulip
   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

   Zulip✓fullprobed7/10

   Zulip ships a documented, versioned REST API (OpenAPI spec, live endpoint confirmed) with a bot framework specifically designed to read and react to channel messages and a documented message-sending endpoint, plus an official CLI/Python client for scripting — bots authenticate via their own per-bot API key, which functions as a scoped credential distinct from a user's. missing for 10: explicit documentation of granular token scopes/permissions (vs. just per-bot keys), and an explicit documented 'read messages' endpoint (only send-message and bot-reacts-to-message are directly evidenced).

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Send a message”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

Bot api

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

   weight 2 · round to Zulip
   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

   Zulip✓fullprobed8/10

   Zulip explicitly documents incoming webhooks as a native integration type (zulip-docs-19) alongside 130+ native integrations (zulip-docs-9/13), and its API includes a straightforward 'send a message' endpoint (zulip-docs-5) backed by a full OpenAPI spec (zulip-probe-5) and live-verified API (zulip-probe-4). This matches the standard incoming-webhook-posts-to-channel pattern. Missing for 10: a first-party doc snippet showing the exact incoming-webhook URL format/config screen, and independent third-party confirmation of webhook setup ease.

   • [claimed-docs] “Incoming webhooks”
   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Send a message”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”

   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 Zulip
   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

   Zulip✓fullprobed7/10

   Zulip explicitly documents a bot framework that lets developers write custom bots that 'react to messages in Zulip' in real time, deployable persistently via the Zulip Botserver, backed by a full OpenAPI-documented REST API and a working live API endpoint plus an installable CLI/client library for scripting integrations. This maps to Zulip's known events/register API model for real-time bots, though the evidence pack never names the events/register endpoints or long-polling mechanics explicitly. Missing for 10: explicit documentation/citation of the events/register API endpoints and real-time event queue mechanics, and independent hands-on confirmation of a bot actually receiving live events.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Eventually, you’ll probably want to run it in a production environment where it’ll stay up, by deploying it on a server using the Zulip Bots…”
   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”

   proof ↗⚑ flag

Ai notes

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   No evidence of any meeting/huddle recording, transcription, or AI-generated recap/notes feature; Zulip's evidence covers topics, channels, bots, integrations, and self-hosting but nothing about calls, huddles, or AI summarization of conversations.

   ⚑ flag

Calls

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

   weight 3 · round to Microsoft Teams
   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

   Zulip—none0/10

   No evidence in the pack mentions audio/video calling features in Zulip; all documentation and community references cover topics, channels, search, bots, integrations, export/import, and self-hosting, but nothing about starting a call from a channel or DM.

   ⚑ flag

External collaboration

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

   weight 2 · round to Zulip
   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

   Zulip~partialclaimed3/10

   Zulip docs mention that 'guests' are a distinct role with restricted channel subscription ability (zulip-docs-22), implying a guest-account mechanism exists, but the evidence pack contains no documentation of inviting external partners, guest account setup/permissions, or any shared-channel/cross-organization collaboration feature. Missing for 10: explicit guest-invite workflow docs, permission scoping details for guests, and any shared-channel-with-external-org capability or independent confirmation it works in practice.

   • [claimed-docs] “Everyone other than guests can subscribe to any public or web-public channel.”

   proof ↗⚑ flag

Messaging model

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

   weight 3 · round to Zulip
   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

   Zulip~partialclaimed6/10

   Docs confirm channels can be public/private/web-public with subscription controls (zulip-docs-2, zulip-docs-22), and channel-scoped search/export tools acknowledge private channel membership boundaries (zulip-docs-14, zulip-docs-17). However, there is no explicit documentation of admin-side membership management workflows (adding/removing members, role-based permissions per channel) or granular channel permission settings. missing for 10: detailed admin UI/API for managing channel membership and permissions, evidence of private channel invite-only enforcement, independent corroboration of admin controls in practice.

   • [claimed-docs] “Subscribing to a channel makes conversations in that channel appear in your inbox, recent conversations, combined feed and left sidebar.”
   • [claimed-docs] “Everyone other than guests can subscribe to any public or web-public channel.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “channels:public: Search messages in all public and web-public channels.”

   proof ↗⚑ flag

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

   weight 3 · round to Zulip
   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

   Zulip✓fullcommunity8/10

   Zulip's core topic-based threading model lets users reply within a topic to keep side discussions attached to the original conversation, and community evidence strongly corroborates this as a standout feature ('the killer feature', 'fundamentally superior model' to Slack threads). Docs describe starting/joining topics and searching within them, and admins have the same messaging capabilities as any user. missing for 10: explicit admin-specific documentation on replying in threads (evidence is general-user focused), and some community reports note UX friction/confusion for non-technical users when threading.

   • [claimed-docs] “To get the full benefits of Zulip's topic model, when starting a new conversation, you should start a new topic!”
   • [claimed-docs] “Lots of conversations can happen in the same channel at the same time, each in its own topic. You never have to worry about interrupting — e…”
   • [claimed-docs] “Click the start a new topic () button next to the name of the channel where you’d like to start a conversation.”
   • [community] “The 'threaded' part is key here. Slack threads are useless compared to Zulip. In Zulip you can create threads on the fly from existing messa…”
   • [community] “Threads are one major reason I like Zulip over Slack, but speed is another... For some reason when I use Slack, the keys feel mushy.”
   • [community] “I used Zulip while at Akamai... My experience was so positive that I've continued to evangelize it at other companies since then... The most…”
   • [community] “I use Zulip all the time at work. It is ugly, sometimes will post to a different thread than you expect... has an infuriating tick that if y…”

   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 Zulip
   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

   Zulip✓fullcommunity8/10

   Zulip's topic model is core to the product: docs explain starting new topics per conversation, subscribing to channels surfaces conversations in inbox/feed, and topic-scoped search lets admins filter busy channels. Community reports strongly corroborate that this threading model is 'fundamentally superior' to Slack for following busy, high-volume discussions without being overwhelmed, and the 'all messages' view helps catch up chronologically across channels. Missing for 10: independent measurement of catch-up efficiency and some community reports note UX friction (miscasting to wrong topic, non-technical user confusion) that slightly tempers the ideal experience.

   • [claimed-docs] “To get the full benefits of Zulip's topic model, when starting a new conversation, you should start a new topic!”
   • [claimed-docs] “Subscribing to a channel makes conversations in that channel appear in your inbox, recent conversations, combined feed and left sidebar.”
   • [claimed-docs] “channel:design has:image new logo: Search for messages in #design that include an image and contain the keywords new and logo.”
   • [claimed-docs] “Lots of conversations can happen in the same channel at the same time, each in its own topic. You never have to worry about interrupting — e…”
   • [claimed-docs] “Click the start a new topic () button next to the name of the channel where you’d like to start a conversation.”
   • [community] “We've been using Zulip internally for a couple of years now... It lets us have real, ongoing, and substantive conversations with a large num…”
   • [community] “The 'threaded' part is key here. Slack threads are useless compared to Zulip. In Zulip you can create threads on the fly from existing messa…”
   • [community] “We used Zulip (then a commercial product) at FoundationDB, and really liked it... the killer feature is the 'all messages' view that merges …”
   • [community] “I used Zulip while at Akamai... My experience was so positive that I've continued to evangelize it at other companies since then... The most…”
   • [community] “I use Zulip all the time at work. It is ugly, sometimes will post to a different thread than you expect... has an infuriating tick that if y…”
   • [community] “Zulip seemed like technically the most polished product... what ended up being the showstopper was that new users were very confused about h…”

   proof ↗⚑ flag

Notifications

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   The evidence pack contains no documentation or mentions of per-channel, per-keyword, or scheduled notification controls (e.g., no citations about notification settings, alert words, or do-not-disturb/quiet hours) — only topics, channels, search, bots, and export/import material. Notification tuning is a standard, fair axis for a chat product, but nothing in the pack demonstrates it.

   ⚑ flag

Compliance

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   No evidence pack items mention audit logs, admin action logs, or user activity tracking features in Zulip; the evidence covers topics, channels, search, bots, integrations, and export/import tools but nothing about auditability of admin/user actions.

   ⚑ flag

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

   weight 2 · round to Microsoft Teams
   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

   Zulip—none0/10

   The evidence pack only covers data export/import tools for migrating organizations, with no mention of configurable message retention policies, automatic deletion schedules, or legal hold/eDiscovery preservation features. No documentation or community evidence addresses compliance-driven retention enforcement.

   ⚑ 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 Zulip
   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

   Zulip✓fullclaimed8/10

   Zulip's docs explicitly describe an export tool that can include 'public and private data (with consent)' — private channel messages and DMs from consenting members — in a machine-readable export format used for migration/backup, directly matching the compliance-export story for a team-admin. This is corroborated by general export/import documentation and self-hosting docs confirming full data portability. Missing for 10: independent/hands-on verification of the export tool's exact output format and confirmation of admin-level override for private data without member consent.

   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “To import data from Slack, Mattermost, Rocket.Chat, Zulip Cloud, or another Zulip server, follow the linked instructions.”

   proof ↗⚑ flag

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

   weight 2 · round to Zulip
   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

   Zulip~partialprobed7/10

   Zulip ships a large, machine-readable OpenAPI spec (~1.5MB) covering messaging, bots, integrations, and administration, with a live public endpoint confirming the API works and an official CLI/bot framework for scripting (zulip-probe-5, zulip-probe-4, zulip-probe-6, zulip-docs-5, zulip-docs-12). However, there is no explicit vendor or independent claim that every UI action (e.g., search filters, topic management UI nuances) has a 1:1 API equivalent. Missing for 10: explicit UI-API parity documentation/audit, independent confirmation that all UI-only features (e.g., advanced search UX, settings toggles) are scriptable via API.

   • [probe] “PROBE openapi-spec: fetched zerver/openapi/zulip.yaml from the Zulip repo → HTTP 200, ~1.5 MB spec beginning 'openapi: 3.0.1' — the complete…”
   • [probe] “PROBE api-live: GET https://chat.zulip.org/api/v1/server_settings → HTTP 200 {"result":"success",...,"zulip_version":"12.0-919-gb1bd7d7d3e"}…”
   • [probe] “PROBE cli-runtime: pip install zulip (v0.9.1) → official zulip-send CLI installs from PyPI and runs headlessly (--help prints usage for send…”
   • [claimed-docs] “Send a message”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”

   proof ↗⚑ flag

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

   weight 3 · round to Zulip
   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

   Zulip✓fullcommunity8/10

   Zulip documents high-quality export tools that let users take both public and private (consented) data out in open formats, explicitly for migrating away from Zulip Cloud to self-hosted servers, and is fully open-source/self-hostable so no vendor lock-in exists. This directly matches 'export data and leave.' Missing for 10: no independent/hands-on verification of the export file format's openness or completeness, and no community testimonial specifically confirming a successful full data exodus.

   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [community] “Zulip is my favorite modern chat program because it's actually 100% FOSS, unlike Mattermost and RocketChat, which are only 'open core'.”

   proof ↗⚑ flag

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

   weight 2 · round to Zulip
   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

   Zulip✓fullcommunity8/10

   Zulip's source code is hosted publicly on GitHub with a contributing guide, and Zulip is widely documented (including in community evidence) as being fully open-source (100% FOSS, not open-core), consistent with its known Apache 2.0 licensing. Missing for 10: explicit citation of the license file/text itself and independent third-party confirmation of the specific license terms.

   • [github] “Contributing code. Check out our guide for new contributors to get started.”
   • [community] “Zulip is my favorite modern chat program because it's actually 100% FOSS, unlike Mattermost and RocketChat, which are only 'open core'.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Zulip
   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

   Zulip~partialcommunity7/10

   Zulip is documented as fully open-source and self-hostable, with official production install docs, import/export tools to migrate between cloud and self-host, and a GitHub repo for contributing (zulip-docs-8, zulip-docs-25, zulip-docs-7, zulip-gh-1). However, community hands-on reports describe real friction: installs require a dedicated server/VM with poor containerization support, heavy RAM requirements, and limited distro support beyond Ubuntu (zulip-comm-18, zulip-comm-13, zulip-comm-14, zulip-comm-3). Missing for 10: independent verification that installation friction has been resolved, broader OS/container support, and clearer resource-requirement documentation.

   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [claimed-docs] “install a self-hosted Zulip server on a system of your choice”
   • [claimed-docs] “To import data from Slack, Mattermost, Rocket.Chat, Zulip Cloud, or another Zulip server, follow the linked instructions.”
   • [claimed-docs] “Then, run the installer, providing your email address and the public hostname that users will be able to access your server with”
   • [github] “Contributing code. Check out our guide for new contributors to get started.”
   • [community] “On the downside, if you are self-hosting, Zulip requires a dedicated server (or VM). There are some efforts to make it run in a container bu…”
   • [community] “I love Zulip... what Zulip lacks right now is polish. Server installation for example is a mess. You basically need a dedicated Debian machi…”
   • [community] “The install procedure looks like a bad joke. So if I'm using RHEL, Fedora, Arch or any other Linux distribution, tough luck. If they're supp…”
   • [community] “Something has gone horribly wrong when a chat server can barely run on 2G... recommended 4GB of RAM for production use.”

   proof ↗⚑ flag

Pricing

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   The evidence pack contains no mention of Zulip's free-tier message history limits or retention policy, so there is no support for the claim that a free-tier team retains full access to older messages. Missing for 10: any documentation or community evidence about free-plan message history caps/retention, and confirmation that free tier does not truncate history.

   ⚑ flag

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

   weight 2 · round to Zulip
   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

   Zulip~partialclaimed6/10

   Zulip's self-hosting docs let users install the server 'on a system of your choice' anywhere they want, effectively giving control over data location/residency, and full export/import tools support migrating data between Zulip Cloud and self-hosted servers. However, there is no evidence of a built-in region-selection feature within Zulip Cloud itself (e.g., choosing EU vs US data centers) — the only residency mechanism is self-hosting your own infrastructure. Missing for 10: explicit multi-region hosting options within Zulip Cloud, documented data-residency guarantees, and independent confirmation of regional deployment support.

   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [claimed-docs] “install a self-hosted Zulip server on a system of your choice”
   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “Then, run the installer, providing your email address and the public hostname that users will be able to access your server with”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   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

   Zulip—none0/10

   No evidence in the pack addresses AI training data usage, opt-out controls, or any explicit AI-training privacy policy for Zulip; self-hosting is mentioned but not tied to preventing AI training use of data. missing for 10: explicit policy/statement on AI model training use of data, opt-out mechanism, or contractual guarantee against training use.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Zulip
   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

   Zulip~partialclaimed4/10

   Zulip's self-hosting option and data export/import tools (including exporting private data with consent) give users significant control over where their data lives and how it can be extracted or migrated, which touches on data retention/portability. However, there is no direct evidence of message retention policies, auto-deletion settings, or a documented data-deletion workflow for accounts/messages. Missing for 10: explicit retention-policy controls, message/account deletion documentation, and any GDPR-style data-deletion API or admin setting.

   • [claimed-docs] “Zulip has high quality export tools that can be used to migrate between the hosted Zulip Cloud service and your own servers.”
   • [claimed-docs] “You can move freely between Zulip Cloud hosting and your own servers with our high quality export and import tools.”
   • [claimed-docs] “Public and private data (with consent): Everything in the export of public data, plus all the private channel messages and direct messages t…”
   • [claimed-docs] “When you self-host Zulip, you get the same software as our Zulip Cloud customers.”
   • [claimed-docs] “install a self-hosted Zulip server on a system of your choice”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   No evidence in the pack addresses telemetry, usage tracking, analytics collection, or an opt-out setting for Zulip; the self-hosting docs discuss data export/import and deployment but never mention telemetry controls.

   ⚑ flag

Ai catchup

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

   weight 2 · round drawn
   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

   Zulip—none0/10

   No evidence of any AI-generated summary, recap, or digest feature for missed channels/threads; documentation focuses on topics, search, bots, integrations, and export/import but never mentions AI summarization.

   ⚑ flag

Search

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

   weight 3 · round to Zulip
   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

   Zulip~partialcommunity6/10

   Zulip's docs confirm a full-text search with real filter syntax (channel:design, has:image, channels:public) and state it offers 'a wide array of search filters', but the evidence pack never shows explicit sender: or date-range filter syntax, and one community report from 2016 claims the search function 'barely works'. missing for 10: explicit sender: and date/time filter documentation, independent verification of search accuracy, resolution of the community complaint about search reliability.

   • [claimed-docs] “channel:design has:image new logo: Search for messages in #design that include an image and contain the keywords new and logo.”
   • [claimed-docs] “channels:public: Search messages in all public and web-public channels.”
   • [claimed-docs] “Zulip also offers a wide array of search filters, which can be used on their own, or in combination with keywords.”
   • [community] “I love Zulip... what Zulip lacks right now is polish. Server installation for example is a mess. You basically need a dedicated Debian machi…”

   proof ↗⚑ flag

Workflow builder

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

   weight 3 · round drawn
   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

   Zulip—none0/10

   Zulip's evidence shows only custom-coded bots, webhooks, and 130+ integrations plus optional Zapier/IFTTT connections (external tools), but no built-in no-code workflow/automation builder with triggers, schedules, or form submissions inside the chat product itself.

   • [claimed-docs] “Zulip's API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot”
   • [claimed-docs] “Over 130 native integrations. And hundreds more through Zapier and IFTTT.”
   • [claimed-docs] “Zulip’s API has a powerful framework for interactive bots that react to messages in Zulip. You can write and run a custom bot, or run an exi…”
   • [claimed-docs] “Incoming webhooks”

   proof ↗⚑ flag