Shortwave vs Missive

Multi account

1. switcherConnect several accounts across providers — Gmail, Microsoft 365, IMAP — and work them from one place

   weight 3 · round to Missive
   Shortwave—none0/10

   No evidence Shortwave supports connecting multiple providers (Gmail, Microsoft 365, IMAP) from one inbox; in fact the founder explicitly states they integrate only with Gmail's APIs ('not IMAP'), and a user confirms 'it only works with Google servers.' This directly contradicts the multi-provider switcher story rather than merely lacking support for it.

   • [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”

   proof ↗⚑ flag

   Missive~partialclaimed4/10

   Evidence only touches this obliquely: contacts management explicitly 'syncs with Office 365 and Google' (missive-docs-23), and shared/team inboxes are documented (missive-docs-32, missive-docs-28), implying multi-account consolidation, but there is no explicit documentation in the pack of connecting Gmail, Microsoft 365, and generic IMAP accounts as email sources worked from one unified inbox. Missing for 10: explicit account-connection docs for Gmail/O365/IMAP email (not just contacts sync), and confirmation that all provider types can be combined in one inbox view.

   • [claimed-docs] “Manage your contacts in shared or private address books. ✓ Syncs with Office 365 and Googl”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other’s toes.”

   proof ↗⚑ flag

Portability

1. switcherMy mail stays reachable over open protocols and standard formats — IMAP/JMAP/SMTP access and standards-based export — so no client can lock me in

   weight 2 · round drawn
   Shortwave—none0/10

   Shortwave's own founder states they integrate via Gmail's proprietary APIs 'not IMAP,' and there is no mention anywhere in docs of JMAP, SMTP-level access, or standards-based export tooling — the product only works atop Google's servers (also confirmed by a security-focused user noting 'it only works with Google servers'). No evidence of any open-protocol mail access or portable export path exists in the pack.

   • [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”
   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”

   proof ↗⚑ flag

   Missive—none0/10

   The evidence pack contains no mention of IMAP, JMAP, or SMTP access for user mailboxes, nor any standards-based export functionality; all connectivity evidence is about REST API, webhooks, and MCP integrations for AI/automation, not about open mail protocol interoperability or data portability for switchers.

   ⚑ flag

2. switcherSelf-host the email app and keep the mail pipeline under my own control

   weight 1 · round drawn
   Shortwave—none0/10

   Shortwave is a cloud-hosted email client that syncs data to its own servers and works only with Gmail/Google servers (per community reports), with no documentation of any self-hosting option, on-prem deployment, or open-source pipeline; probes for docs/API specs also return 404s, indicating no infrastructure exposed for self-hosting.

   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive—none0/10

   Missive is a cloud-hosted SaaS collaboration/email platform with no documented self-hosting option; community evidence confirms mail data routes through Missive's own servers (missive-comm-1), and no docs mention on-premise or self-hosted deployment.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

Agent access

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

   weight 2 · round drawn
   Shortwave—none0/10

   Direct probes show no llms.txt or agent-oriented docs endpoint exists (404s across llms.txt, docs-md, openapi paths), and no other evidence mentions such agent-facing documentation.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive—none0/10

   Direct probes show no llms.txt, no docs.md, and no OpenAPI spec exposed at expected locations (all 404), and no evidence of agent-oriented documentation formats being offered elsewhere; while Missive has an MCP server (a different axis), there's no proof an agent can be pointed at llms.txt or similar agent-readable docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round to Missive
   Shortwave—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Missive~partialprobed3/10

   Missive exposes a REST API, webhooks, and a documented MCP server that let external systems and AI agents trigger actions without using the UI, which could be scripted from CI/automation pipelines. However there is no evidence of an official CLI, headless mode, Docker/container deployment, or CI-specific documentation/examples for running Missive itself in automated pipelines. Missing for 10: dedicated CLI or headless execution mode, CI/CD integration guides, and independent confirmation of automation-in-CI use cases.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “API & MCP access”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Shortwave✓fullcommunity8/10

   Shortwave explicitly documents connecting to any MCP server via 'Add custom integration' to let its AI Assistant use those tools, with first-party blog docs and pricing page confirming MCP support alongside built-in integrations. Missing for 10: independent hands-on verification of the MCP setup flow and no detail on tool-call reliability/limits beyond marketing docs.

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [community] “Security vendor blog highlighted that Shortwave's AI Email with MCP integration 'opens up rich capabilities—but also new attack surfaces,' f…”

   proof ↗⚑ flag

   Missive✓fullclaimed8/10

   Missive documents a clear custom-MCP flow: users add a 'Custom MCP' server with a URL and auth, and 'connect any MCP-compatible server to Missive's AI Copilot' to let the assistant use internal APIs, databases, or custom tooling, alongside pre-built MCP integrations (Notion, Linear, Attio, Lindy.ai). Missing for 10: independent/hands-on verification of the custom MCP connection flow beyond vendor docs, and more detail on tool invocation limits or reliability.

   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “Add "Custom MCP" and enter a name and your server URL. Choose an authentication method and click Add”
   • [claimed-docs] “Missive ships with ready-to-use MCP integrations for Notion, Linear, and Attio, plus AI automation platforms like Lindy.ai.”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”
   • [claimed-docs] “Connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprietary data, or homegrown too…”
   • [claimed-docs] “Extend capabilities beyond Missive's built-in MCP integrations”
   • [claimed-docs] “Missive ships with ready-to-use MCP integrations for Notion, Linear, and Attio, plus AI automation platforms like Lindy.ai. The assistant ru…”

   proof ↗⚑ flag

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

   weight 3 · round to Missive
   Shortwave—none0/10

   Shortwave documents letting its own AI Assistant connect out to third-party MCP servers ('Add custom integration', point to an MCP server of your choice) — this is MCP-client behavior, not Shortwave exposing an official MCP server that external agents could connect to. As a SaaS email product, offering an official MCP server for outside agents is a fair, applicable axis, but no evidence pack item shows such a server (docs/openapi/llms.txt probes all 404).

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive✓fullprobed9/10

   Missive explicitly documents an official MCP server that lets external AI apps (Claude, ChatGPT, Cursor) connect and act on conversations, contacts, calendar, and drafts with configurable permissions, and a dedicated docs page for the MCP server is confirmed to exist via probe. Missing for 10: independent/hands-on third-party confirmation that external agents successfully connect and operate via this server.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”
   • [claimed-docs] “API & MCP access”

   proof ↗⚑ flag

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

   weight 3 · round to Missive
   Shortwave—none0/10

   Shortwave's evidence only shows it acting as an MCP *client* (connecting its AI Assistant to other apps' MCP servers) or integrating with third-party APIs like Zapier/GitHub — none of this constitutes Shortwave itself exposing a documented public API for external developers to drive the product. Direct probes for llms.txt, docs-as-markdown, and OpenAPI/Swagger specs all returned 404s, confirming no discoverable public API surface.

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “Just click "Add custom integration" and point to an MCP server of your choice — or even create your own.”
   • [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive✓fullprobed8/10

   Missive documents a REST API, webhooks, UI integrations, and custom channels for developers (missive-docs-31/39/15), plus an official MCP server exposing conversations, contacts, calendar, and drafts to AI apps like Claude/ChatGPT/Cursor (missive-docs-1/20, missive-probe-4). This gives AI-native users a documented, programmatic way to drive the product beyond the UI. Missing for 10: a discoverable OpenAPI/swagger spec or llms.txt (all probed and 404'd) and independent third-party corroboration of API robustness.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”
   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”
   • [claimed-docs] “API & MCP access”

   proof ↗⚑ flag

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

   weight 2 · round to Missive
   Shortwave—none0/10

   Shortwave's evidence covers MCP/app integrations and AI assistant features, but there is no mention of scoped or least-privilege API credential issuance, API key management, or granular permission controls for agents; probes confirm no public API/OpenAPI spec exists. Community comments even note complaints about over-broad permission requests rather than scoped credentials, reinforcing absence of this capability.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
   • [community] “User complaint: 'all these apps either want gmail way too many gmail permissions, and/or are hosted... I'm trying to get rid of gmail lol.'”

   proof ↗⚑ flag

   Missive~partialclaimed5/10

   Missive's MCP integration explicitly notes external AI apps connect "with the permissions you choose" (missive-docs-20) and custom MCP setup lets you "choose an authentication method" (missive-docs-17), implying some scoped access control for agents. However, there's no documentation of granular API-key scopes, role-based permission tiers, or a dedicated credential-issuance UI for least-privilege agent access. Missing for 10: explicit scoped API key/token generation flow, documented permission levels/roles for agents, and independent confirmation that scoping is enforced in practice.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Add "Custom MCP" and enter a name and your server URL. Choose an authentication method and click Add”
   • [claimed-docs] “API & MCP access”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence of any official SDKs for developers; probes for llms.txt, docs.md, and OpenAPI/swagger specs all returned 404, and the evidence pack only documents MCP-based integrations for end-user workflows (Slack, Notion, Zapier) rather than a developer SDK.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive—none0/10

   Missive documents a REST API, webhooks, custom channels, and MCP integrations for developers, but no evidence anywhere mentions official client SDKs (e.g. language libraries) for building against Missive; probes even show 404s for OpenAPI/spec files that would typically back SDK generation.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Missive
   Shortwave—none0/10

   Shortwave's evidence covers triggers, MCP integrations, and Zapier connections, but nothing describes outbound webhooks that let an AI-native user subscribe to Shortwave events; no webhook API, subscription endpoint, or event schema is documented, and OpenAPI/llms.txt probes returned 404s.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive~partialclaimed4/10

   Missive's developer tools page explicitly lists webhooks alongside REST API and custom channels, confirming the capability exists, but there is no detail on event types, subscription setup, payload format, or independent corroboration of webhook usage. Missing for 10: documented list of subscribable event types, webhook setup/config instructions, security/signing details, and third-party confirmation of reliability.

   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave delivers AI-generated insights directly in-product: Instant Summaries appear atop threads, AI Assistant reads threads/searches history/checks calendar to surface answers, Ghostwriter offers inline autocomplete suggestions, and custom AI filters/triggers auto-label and organize emails based on AI analysis. These are well-documented first-party features spanning summarization, suggestion, and automated insight generation across the inbox. Missing for 10: independent hands-on validation of insight quality/accuracy and no third-party review confirming these AI insights work reliably in practice beyond vendor claims.

   • [claimed-docs] “Instant Summaries show up at the very top of your email threads the instant you open them.”
   • [claimed-docs] “Instant Summaries show up at the very top of your email threads the **instant** you open them.”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”

   proof ↗⚑ flag

   Missive~partialclaimed5/10

   Missive's AI assistant can summarize inboxes, draft replies, and triage conversations against connected data (CRM, docs) via MCP, and can compose/reply/translate with AI, which counts as AI-generated insights/suggestions from data. However, evidence is mostly marketing copy without hands-on demonstration of proactive 'insights' (e.g., analytics-driven suggestions) and no independent corroboration of quality or accuracy. missing for 10: independent/hands-on verification of insight quality, concrete examples of proactive analytics-style insights beyond summarization/drafting, and detail on how suggestions are surfaced in UI.

   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”

   proof ↗⚑ flag

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

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed7/10

   Shortwave explicitly supports triggers that draft replies, add comments, organize threads into todos when emails arrive, plus custom AI filters running as background scripts and Tasklet integration to auto-act on emails—these run autonomously without user initiation. However, evidence is all vendor-sourced with no independent verification of reliability or scope of autonomy. Missing for 10: independent/hands-on confirmation of trigger reliability, detail on trigger configuration UI, and evidence of complex multi-step autonomous workflows beyond simple triggers.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”
   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”

   proof ↗⚑ flag

   Missive~partialclaimed7/10

   Missive documents rule-based workflow automation (up to 1000 rules) and long-running AI assistant sessions that operate in the background with a session tab showing progress ('no longer need babysitting'), plus agent-driven triage of conversations against a CRM before a human looks at them — evidence of autonomous background automation. However, there's no independent/hands-on confirmation of reliability or scope of autonomy, and details on triggers/scheduling for rules are thin. Missing for 10: independent corroboration of autonomous execution reliability, deeper documentation on rule triggers/scheduling and failure handling.

   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “The session tab now shows what the assistant is up to, and a conversation links back to the sessions attached to it.”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”

   proof ↗⚑ flag

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

   weight 3 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave has a built-in AI assistant/executive assistant that can read threads, write drafts, search email history, check calendar, run custom AI filters, and take multi-step actions via triggers and MCP integrations without leaving the inbox — clearly delegatable task execution. Missing for 10: independent hands-on validation of end-to-end delegated task completion (beyond vendor blog claims) and details on reliability/error handling.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”

   proof ↗⚑ flag

   Missive✓fullclaimed7/10

   Missive documents a built-in AI Assistant/Copilot that can compose, reply, translate, triage conversations against CRM data, and run extended 'sessions' with a visible status tab, plus access internal tools via MCP — all delegatable from within the product (missive-docs-49, missive-docs-34, missive-docs-22, missive-docs-16, missive-docs-52). Missing for 10: independent/hands-on evidence of actual task delegation outcomes and more detail on assistant capabilities/limits beyond first-party changelog blurbs.

   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “Give your AI assistant access to your own tools and internal systems, directly from Missive.”
   • [claimed-docs] “The session tab now shows what the assistant is up to, and a conversation links back to the sessions attached to it.”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”

   proof ↗⚑ flag

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

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave's AI Assistant lets users operate the inbox via natural language—reading threads, writing drafts, searching email history, checking calendar, and running custom AI filters written in plain English—directly in the product's core value proposition. Docs consistently describe this as the primary UX (chat-based assistant, plain-English filter scripts, natural-language triggers). missing for 10: independent/hands-on verification specifically of the natural-language command interface's reliability (community evidence focuses on UI/pricing/privacy, not NL command execution quality).

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “connects our AI Assistant to all your business applications, letting you accomplish complex workflows without ever leaving your inbox”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”

   proof ↗⚑ flag

   Missive✓fullclaimed7/10

   Missive's AI Assistant/Copilot and MCP integration let users issue natural-language requests (e.g., 'Ask Claude to summarize your inbox and draft replies,' 'compose, reply, and translate messages with AI') and let external AI apps act on conversations, contacts, calendar, and drafts through natural language via Claude/ChatGPT/Cursor. The command bar also supports quick text-based commands for actions like snoozing. Missing for 10: independent/hands-on user validation of natural-language accuracy and no detailed listing of all supported natural-language actions beyond marketing copy.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Ask how a feature works, how to set up a rule, or where a setting lives. The answer comes straight from the Missive documentation instead of…”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Shortwave—none0/10

   Shortwave is an email client, not a developer platform with an API reference; probes for llms.txt, docs.md, and OpenAPI specs all returned 404s, and no evidence mentions any interactive API documentation or runnable code examples.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive—none0/10

   Missive documents a REST API and developer tools, but there is no evidence of an interactive API reference or runnable examples; explicit probes for openapi/swagger specs all returned 404s, indicating no interactive API explorer exists.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shortwave—none0/10

   Direct probes for OpenAPI/swagger specs and llms.txt all returned 404s, and no docs mention a machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”

   proof ↗⚑ flag

   Missive—none0/10

   Probes for OpenAPI/Swagger spec files at standard locations all returned 404, and no evidence pack item mentions a downloadable machine-readable API spec despite Missive having a REST API and developer docs.

   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI/llms.txt/docs endpoints all returned 404s, and no docs mention versioned APIs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive—none0/10

   There is a REST API and MCP integrations documented, but no evidence of API versioning scheme or any documented deprecation policy; probes for openapi/spec files all 404. missing for 10: versioning scheme documentation, explicit deprecation/backward-compatibility policy, changelog of breaking API changes.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

Agent workflows

1. ai-native userAn external agent — Claude, ChatGPT, or my own — can read, triage, draft, and send my email end to end through a documented connection

   weight 2 · round to Missive
   Shortwave—none0/10

   Shortwave documents an internal AI Assistant that reads/drafts/searches email, and it can act as an MCP *client* connecting its own AI to external apps (Slack, GitHub, Zapier, etc.), but there is no evidence Shortwave exposes itself as an MCP server or documented API that lets an external agent (Claude, ChatGPT, or a custom agent) read/triage/draft/send mail through it. Probes confirm no llms.txt, no docs.md, and no OpenAPI/Swagger endpoint, indicating no documented external-agent connection surface.

   • [claimed-docs] “You can connect virtually any application through the Model Context Protocol (MCP). Just click "Add custom integration" and point to an MCP …”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “AI Integrations for Shortwave—a powerful new feature that connects our AI Assistant to all your business applications, letting you accomplis…”
   • [claimed-docs] “Connect the AI with your favorite apps and services for enhanced productivity workflows through built-in integrations or MCP”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive~partialprobed6/10

   Missive documents an official MCP server (missive-probe-4) that lets external AI apps like Claude, ChatGPT, or Cursor connect and act on conversations, contacts, calendar, and drafts with configurable permissions (missive-docs-1, missive-docs-20), including summarizing inboxes, drafting replies, and triaging conversations against a CRM (missive-docs-21, missive-docs-22). However, explicit end-to-end 'send' capability via the agent is not directly documented, and there is no independent/hands-on corroboration of the full read-triage-draft-send loop working in practice. Missing for 10: explicit documentation of agent-initiated sending (not just drafting), and third-party/hands-on verification of the full workflow.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”
   • [claimed-docs] “Connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprietary data, or homegrown too…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”

   proof ↗⚑ flag

Ai assistant

1. ai-native userAsk an assistant questions across my whole inbox and calendar — who said what, what's outstanding — and get grounded answers

   weight 2 · round to Shortwave
   Shortwave✓fullcommunity8/10

   Docs directly describe the AI Assistant reading threads, writing drafts, searching entire email history, and checking calendar — matching the grounded cross-inbox/calendar Q&A story. Community evidence corroborates fast search/summaries and real usage, though no independent hands-on confirmation of complex multi-thread grounded reasoning exists. Missing for 10: independent hands-on verification of accuracy/groundedness across large inboxes, and detail on how calendar+email context are combined in answers.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “Instant Summaries show up at the very top of your email threads the instant you open them.”
   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”

   proof ↗⚑ flag

   Missive~partialclaimed6/10

   Missive's AI Assistant/MCP integration lets external AI apps (Claude, ChatGPT, Cursor) act on conversations, contacts, calendar, and drafts, and docs explicitly mention asking Claude to summarize the inbox and draft replies — directly supporting cross-inbox Q&A grounded in Missive data. However, evidence doesn't demonstrate calendar-specific querying depth or explicit 'what's outstanding' style aggregate reasoning across the whole inbox, and there's no independent/hands-on validation of answer groundedness or accuracy. Missing for 10: concrete examples of calendar-integrated Q&A, evidence of multi-conversation aggregate answers, and independent corroboration of answer quality/groundedness.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”

   proof ↗⚑ flag

Ai drafting

1. ai-native userAI drafts replies in my own voice and tone — ready to review and send, not generic boilerplate

   weight 3 · round to Shortwave
   Shortwave~partialclaimed6/10

   Shortwave's AI Assistant explicitly 'writes drafts' and Ghostwriter autocompletes replies as you type, confirming AI-drafted replies are a core capability. However, no evidence specifically shows the AI learns or mimics the user's personal voice/tone (vs. generic suggestions or template-based AI Snippets), so the 'own voice' personalization claim is unverified. Missing for 10: explicit documentation of voice/tone personalization or learning from user's writing style, and independent user reports confirming drafts sound authentically like them rather than generic AI text.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete.”
   • [claimed-docs] “you’ll see suggestions presented to you automatically as you draft emails. Just press ‘tab’ to complete”
   • [claimed-docs] “AI Snippets let you define an email template once upfront and then re-use it whenever you need it.”

   proof ↗⚑ flag

   Missive~partialclaimed4/10

   Missive documents AI compose/reply features ("Quickly compose, reply, and translate messages with AI directly in Missive" and "Ask Claude to summarize your inbox and draft replies") confirming AI drafting exists, but there is no evidence describing tone/voice personalization or that drafts are tuned to the user's own writing style versus generic boilerplate. Missing for 10: evidence of voice/tone learning or personalization, hands-on examples showing draft quality matches user's style, independent corroboration of draft usefulness.

   • [claimed-docs] “Quickly compose, reply, and translate messages with AI directly in Missive.”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”

   proof ↗⚑ flag

Ai triage

1. ai-native userAI triages my inbox for me — auto-labeling, categorizing, and surfacing what needs attention — with behavior I can steer and audit

   weight 3 · round to Shortwave
   Shortwave✓fullcommunity7/10

   Shortwave ships custom AI filters that auto-label, star, and archive using plain-English scripts, plus Bundles/Splits to categorize inbox by importance and one-click identification of important emails/todos, directly matching the triage story; community feedback corroborates the bundling/importance-sorting feature as effective ('top shelf'). Steerability is evidenced via the plain-English filter scripts, but missing for 10: explicit audit-trail/log of AI triage decisions and independent verification of filter reliability at scale.

   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
   • [claimed-docs] “They’re a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
   • [claimed-docs] “Splits let you handle different types of emails at different times, so you can stay responsive where it matters most.”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Missive~partialclaimed6/10

   Missive's AI Assistant/MCP integration explicitly supports agent-driven triage ('Let an agent triage new conversations against your CRM before you look at them'), inbox summarization, and rule-based automation (up to 1000 rules), and provides audit trails via action logs and a session tab showing assistant activity, plus permission-scoped access for steering behavior. However, there's no explicit mention of automatic labeling/categorization as a distinct AI feature (only manual rules), and no independent/hands-on evidence confirming triage quality works as advertised. Missing for 10: explicit auto-labeling/categorization feature description, hands-on validation of triage accuracy, and clearer UI for reviewing/adjusting AI triage decisions beyond session logs.

   • [claimed-docs] “Let an agent triage new conversations against your CRM before you look at them”
   • [claimed-docs] “Ask Claude to summarize your inbox and draft replies without leaving the chat”
   • [claimed-docs] “The session tab now shows what the assistant is up to, and a conversation links back to the sessions attached to it.”
   • [claimed-docs] “Long assistant sessions no longer need babysitting. The session tab now shows what the assistant is up to”
   • [claimed-docs] “Every action within Missive is logged, so you know who did what, and when.”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Up to 1000 rules”

   proof ↗⚑ flag

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

   weight 2 · round to Shortwave
   Shortwave~partialclaimed6/10

   Shortwave's custom AI filters ('automatically label, star, archive, and more with scripts you write in plain English') and one-click sweep of non-important emails/todos (docs-15, docs-29) directly support automated actions applied across many inbox items at once, and triggers (docs-1) extend this to organizing threads into todos in bulk. However, there's no explicit documentation of a true multi-select bulk-action UI, batch limits, or independent hands-on confirmation that these AI filters reliably scale across large volumes of email. Missing for 10: explicit bulk-select/apply workflow docs, scale/performance evidence, and independent user corroboration of bulk automation working as advertised.

   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”

   proof ↗⚑ flag

   Missive~partialclaimed3/10

   Missive documents rule-based automation ('Up to 1000 rules') and API/MCP access that could act across many items, plus a bulk auto-archive list feature, but there is no direct evidence of a bulk-select/bulk-action UI or bulk API endpoint for acting on many conversations/contacts at once. Missing for 10: explicit bulk-action UI documentation, bulk API/webhook examples, and independent confirmation of scale-limits for automation across many items.

   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Picking Everyone in a shared account's Auto-archive list covers anyone who joins your organization later, instead of adding each person by h…”
   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”

   proof ↗⚑ flag

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

   weight 3 · round to Shortwave
   Shortwave✓fullclaimed7/10

   Shortwave documents explicit rule/trigger automation: triggers that draft replies when emails arrive, custom AI filters written in plain English that auto-label/star/archive, and Tasklet integration that takes automatic actions on emails as they arrive. This directly matches defining rules that fire on events (email arrival) with automated actions. Missing for 10: independent/hands-on verification that these triggers work reliably in practice, and more detail on rule complexity/limits beyond marketing copy.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”

   proof ↗⚑ flag

   Missive~partialclaimed5/10

   Missive confirms a native Rules feature ("Automate your workflows", "Up to 1000 rules", and documentation referencing 'how to set up a rule') that lets users define automation triggered by events, plus webhooks/API for event-driven actions. However, the evidence pack lacks concrete documentation of what trigger events or actions rules support, no hands-on examples of rule configuration, and no independent corroboration of automation depth or reliability. missing for 10: detailed rule trigger/action catalog, hands-on walkthrough of rule creation, independent user validation of automation reliability.

   • [claimed-docs] “Ask how a feature works, how to set up a rule, or where a setting lives. The answer comes straight from the Missive documentation instead of…”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Shortwave
   Shortwave~partialclaimed4/10

   Shortwave offers event-based 'triggers' (auto-draft replies, add comments, organize todos) and custom AI filters that run automatically in plain English, which are a form of automation, but these are reactive triggers on incoming events rather than true time-based recurring/scheduled jobs — the only scheduling feature documented (Scheduled Send) is a one-time future send, not a recurring workflow. Missing for 10: explicit recurring/cron-style scheduling of AI workflows, documentation of periodic digest or repeat-interval automations, and independent confirmation that triggers can run on a time-based recurring cadence rather than only on email arrival.

   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Scheduled send gives you the ability to send an email at a future time.”
   • [claimed-docs] “Shortwave now integrates with Tasklet to take action on your emails automatically. Drafts appear right in Shortwave—not buried in Gmail.”

   proof ↗⚑ flag

   Missive—none0/10

   Missive documents an AI Assistant, MCP integrations, and an event-triggered 'rules' automation engine (up to 1000 rules) for workflows, but nothing in the evidence describes scheduling recurring/cron-style jobs or timed recurring AI workflows — rules appear to be trigger-based, not time-scheduled. missing for 10: any mention of a scheduler, cron-like recurrence, or time-based recurring job configuration for AI/assistant workflows.

   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Give your Missive AI Assistant access to internal APIs, databases, or custom tooling”
   • [claimed-docs] “With custom MCP, you can connect any MCP-compatible server to Missive's AI Copilot and let AI interact with your internal systems, proprieta…”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Shortwave—none0/10

   Shortwave offers AI filters, triggers, and MCP integrations for automation, but there is no evidence of version history, review workflows, diffs, or rollback capability for these automations.

   ⚑ flag

   Missive—none0/10

   Missive documents rules/automations, an activity log, and AI session tabs, but there is no evidence of any version history, review workflow, or rollback mechanism for automations/rules — no changelog history for rules, no diff/versioning UI, no undo/rollback feature mentioned anywhere.

   ⚑ flag

Calendar

1. power-userSee my calendar, respond to invites, and create events without leaving the email client

   weight 2 · round to Shortwave
   Shortwave~partialclaimed3/10

   Shortwave's AI assistant is documented to 'check your calendar' and integrate with Calendar as one of many connected apps, implying some calendar visibility inside the client, but there is no evidence of responding to invites or creating events without leaving the email client. missing for 10: explicit calendar view/UI, invite RSVP handling, and event-creation workflow evidence.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [claimed-docs] “Connect the AI to your Slack, Calendar, Notion, Asana, Hubspot, and more so you can automate workflows without ever leaving your inbox.”

   proof ↗⚑ flag

   Missive~partialclaimed2/10

   The only calendar-related evidence is indirect: MCP changelog entries note that external AI apps can 'act on your conversations, contacts, calendar, and drafts,' implying Missive holds calendar data, but there is no documentation of an in-app calendar view, RSVP/invite response flow, or event-creation UI comparable to inbox features. Missing for 10: dedicated calendar panel/view docs, invite accept/decline UI, and event creation flow evidence — only an AI-assistant-access mention exists.

   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”
   • [claimed-docs] “External AI apps like Claude, ChatGPT, or Cursor can now connect to Missive through the Model Context Protocol and act on your conversations…”

   proof ↗⚑ flag

2. power-userShare my availability or insert bookable meeting times directly into an email

   weight 1 · round drawn
   Shortwave—none0/10

   Evidence shows Shortwave's AI can 'check your calendar' and connect to Calendar via integrations, but there is no mention of sharing availability or inserting bookable meeting time slots into an email — a distinct calendar-scheduling feature not evidenced anywhere in the pack.

   ⚑ flag

   Missive—none0/10

   The evidence pack shows Missive's MCP integration can 'act on... calendar' generally, but there is no mention of any feature to share availability, generate scheduling links, or insert bookable meeting times into an email — a distinct capability from generic calendar access.

   ⚑ flag

Sending

1. power-userSee whether and when recipients opened my email

   weight 1 · round drawn
   Shortwave—none0/10

   No evidence in the pack mentions read receipts, open tracking, or notifications about recipient email opens; Shortwave's documented features cover AI drafting, snippets, scheduling, undo send, and integrations but nothing about tracking whether/when recipients opened a message.

   ⚑ flag

   Missive—none0/10

   No evidence in the pack mentions read receipts, email open tracking, or notifications about recipient opens/views; the pack covers collaboration, MCP/AI integrations, and admin features but nothing about tracking email opens.

   ⚑ flag

2. power-userSchedule an email to send later and undo a send within a grace window

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave's docs explicitly describe both scheduled send (set a time, write message, move on) and undo send (revert a sent message back to a draft), directly matching the story. Missing for 10: explicit detail on the undo grace-window duration and independent/hands-on corroboration beyond vendor blog.

   • [claimed-docs] “Scheduled send gives you the ability to send an email at a future time.”
   • [claimed-docs] “Undo send staves off the panic you feel when you accidentally send a message that wasn't ready by allowing you to revert a sent message back…”
   • [claimed-docs] “Scheduled send gives you the ability to send an email at a future time. All you have to do is write a message, set a send time, and then mov…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence in the pack mentions scheduled sending or an undo-send grace window; the pack covers MCP integrations, collaboration features, snoozing, and canned responses but nothing about send scheduling or send-delay/undo functionality.

   ⚑ flag

Templates

1. power-userInsert saved snippets or templates — with variables and attachments — instead of retyping the same reply

   weight 2 · round to Missive
   Shortwave~partialclaimed5/10

   Shortwave documents 'AI Snippets' that let users define an email template once and reuse it, available for individual and team use — directly matching the core snippet/template story. However, the evidence never confirms support for variables (dynamic fields) within snippets or attaching files as part of a snippet, both explicitly requested in the story. Missing for 10: documentation of variable/placeholder support in snippets, documentation of attachment bundling with snippets, and independent/hands-on confirmation of the feature working as described.

   • [claimed-docs] “AI Snippets let you define an email template once upfront and then re-use it whenever you need it.”
   • [claimed-docs] “AI Snippets are available both for individual use and for use across your team.”

   proof ↗⚑ flag

   Missive✓fullclaimed8/10

   Missive's canned responses/templates feature explicitly supports saving reusable replies, inserting them via keystrokes/command bar, sharing across teams, and customizing with a variables templating engine (recipient name, etc.), directly matching the story; MCP/API docs also confirm drafts resolve template variables like {{ user.name }}. missing for 10: explicit first-party documentation confirming attachments can be bundled/saved within a canned response/template, and independent hands-on corroboration of the templating workflow.

   • [claimed-docs] “Canned responses (or templates) are pre-written replies to common questions. Instead of typing the same answer repeatedly, you write it once…”
   • [claimed-docs] “You can easily customize your responses or templates with dynamic content like your recipient's name by using our variables templating engin…”
   • [claimed-docs] “Drafts created outside the composer, by the assistant, by a rule, or through the API and MCP server, now resolve {{ user.name }} and {{ user…”
   • [claimed-docs] “Drafts created outside the composer, by the assistant, by a rule, or through the API and MCP server, now resolve {{ user.name }} and {{ user…”

   proof ↗⚑ flag

Offline

1. power-userRead, search, and write email offline, with changes syncing when I reconnect

   weight 2 · round to Shortwave
   Shortwave~partialcommunity3/10

   The founder states Gmail API integration enables 'offline handling' alongside real-time sync, implying some offline capability, but there's no detail on offline search, offline composing, or how changes reconcile on reconnect. missing for 10: documentation of offline read/search functionality, offline draft writing, and sync-conflict resolution behavior.

   • [community] “Founder: We integrate with Gmail's APIs (not IMAP) to enable faster real-time updates, better latency compensation, offline handling, bundle…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence in the pack addresses offline mode, local caching of email data, offline search, or sync-on-reconnect behavior; all citations concern MCP/AI integrations, team collaboration, and pricing features unrelated to offline reliability.

   ⚑ flag

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

   weight 2 · round to Missive
   Shortwave—none0/10

   No evidence of a public API for Shortwave; probes for llms.txt, docs-md, and OpenAPI specs all returned 404, and no documentation mentions programmatic access to core features like AI assistant, triggers, or inbox management outside the UI/MCP integration (which is inbound, not an outbound API for replicating UI actions).

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive~partialprobed4/10

   Missive documents a REST API, webhooks, and an MCP server that can act on conversations, contacts, calendar, and drafts (missive-docs-15, missive-docs-31, missive-docs-45, missive-probe-4), suggesting broad but not explicitly complete UI/API parity — there is no vendor claim of 1:1 feature parity, and the OpenAPI spec could not be located via standard probes (missive-probe-3), making it hard to verify full API surface coverage against UI capabilities like snoozing, canned responses, or command-bar search (missive-docs-supp-1/3/4) which are not mentioned as API-exposed. Missing for 10: an explicit vendor statement of full UI/API parity, a discoverable OpenAPI/schema reference, and evidence that UI-only features (snoozing, canned responses, command bar actions) are also API-accessible.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Drafts created outside the composer, by the assistant, by a rule, or through the API and MCP server, now resolve {{ user.name }} and {{ user…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”
   • [probe] “official MCP server documented at https://missiveapp.com/docs/ai/mcp/server”
   • [claimed-docs] “Snoozing temporarily hides a conversation until a specific time, then brings it back to your Inbox. Use it to defer emails you can't deal wi…”
   • [claimed-docs] “Canned responses (or templates) are pre-written replies to common questions. Instead of typing the same answer repeatedly, you write it once…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Shortwave—none0/10

   No evidence of any data export feature (mailbox, comments, snippets, etc.) in open formats; probes for llms.txt, docs-md, and openapi endpoints all returned 404, and no changelog/blog mentions an export or account-portability capability. Community threads mention deleting the account making it 'low-risk' to switch back to Gmail, but that is because Shortwave uses Gmail as the underlying store, not because Shortwave itself offers a data export mechanism. missing for 10: any documented export/download feature, supported open file formats, or migration/backup tooling.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”
   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”

   proof ↗⚑ flag

   Missive—none0/10

   The evidence pack shows a REST API, webhooks, and MCP integrations for connecting external tools, but nothing documents a bulk data-export feature or open-format (mbox/CSV/JSON) export enabling a user to fully extract their mail, contacts, and conversation history and leave the platform. Probes for docs/API artifacts (llms.txt, openapi) also 404, further indicating no dedicated export-and-leave capability is documented.

   • [claimed-docs] “Use the Rest API to enrich Missive conversations with content from anywhere: commits from GitHub, transactions from Stripe,”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence of any open-source license or public source repository for Shortwave; it is a closed commercial SaaS email client with no mention of open licensing anywhere in the evidence pack.

   ⚑ flag

   Missive—none0/10

   Missive is a closed-source commercial email/collaboration SaaS; no evidence anywhere in the pack of an open-source license or public source repository, and probes for typical openness indicators (llms.txt, docs.md, openapi) all 404. No indication source code is available under any license.

   • [probe] “PROBE llms.txt: HTTP 404 at https://missiveapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://missiveapp.com/docs.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://missiveapp.com/openapi.json, https://missiveapp.com/swagger.json, https://missiveapp.com/api…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Shortwave—none0/10

   Shortwave is a hosted SaaS email client with no evidence of any self-hostable version; it relies on Google servers and its own cloud infrastructure (comm-11), and no self-hosting docs, Docker images, or open-source releases exist in the evidence pack.

   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.shortwave.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.shortwave.com/docs/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.shortwave.com/openapi.json, https://www.shortwave.com/swagger.json, https://www.shortwav…”

   proof ↗⚑ flag

   Missive—none0/10

   Missive is a cloud-hosted SaaS collaboration/email product; evidence shows data routes through Missive's own servers (missive-comm-1) and no docs mention any self-hosting/on-prem deployment option anywhere in the extensive feature/pricing/docs pack.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence anywhere in the pack mentions data residency, region selection, or storage location controls; Shortwave is shown to run on Google servers with no configurable region options, and community comments only raise general privacy/security concerns without any residency feature being offered.

   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence in the pack mentions data residency, region selection, or geographic storage location controls; features like IP restrictions and SSO relate to access control, not data storage location. Missing for 10: any mention of regional data hosting options, residency guarantees, or storage location configuration.

   ⚑ flag

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

   weight 3 · round drawn
   Shortwave—none0/10

   No evidence pack item describes any setting, policy statement, or opt-out mechanism letting users prevent their email/AI data from being used for model training; the only related community evidence (shortwave-comm-7) actually flags that Shortwave's privacy policy permits sharing email content/metadata with third-party vendors, which a user rejected outright rather than confirming a training opt-out exists.

   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”
   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence in the pack addresses any AI-training opt-out, data-usage policy for AI model training, or privacy controls specific to preventing training on user data. The pack covers MCP integrations, AI assistant features, and collaboration tools, but nothing about training data exclusion or a documented privacy commitment on this axis.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Shortwave
   Shortwave~partialcommunity3/10

   The only evidence touching on data deletion is a community anecdote that deleting one's Shortwave account makes it low-risk to switch back to Gmail, implying account-level deletion works, but there is no documented retention policy, granular deletion controls, or data-lifecycle settings; community comments even flag privacy concerns about email content being synced/shared with third-party vendors with no denylist option. missing for 10: documented retention policy, explicit deletion/export controls, first-party privacy/data-handling documentation.

   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence describes any data retention or deletion controls (e.g., configurable retention periods, right-to-delete, data purge options) for Missive or its AI/MCP features; the only related community note concerns data routing through servers via TLS, not retention/deletion policy.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence Shortwave offers any telemetry/usage-tracking opt-out control; documentation focuses on AI features and integrations, and community discussion instead raises concerns about email content being shared with third-party vendors with no denylist option, but nothing addresses telemetry/analytics opt-out specifically.

   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence pack item addresses telemetry/usage-tracking opt-out settings, privacy controls, or data-collection disclosures for Missive; the closest related content (comm-1) merely notes emails route through Missive's servers, which is unrelated to telemetry opt-out. This is an applicable axis for a SaaS product but no supporting evidence exists.

   ⚑ flag

Protection

1. switcherUse aliases or masked addresses so sign-ups and strangers never learn my real address

   weight 1 · round drawn
   Shortwave—none0/10

   No evidence Shortwave offers email aliasing, masked addresses, or similar identity-protection features for sign-ups; the pack only covers AI assistant, integrations, and inbox management features unrelated to address masking.

   ⚑ flag

   Missive—none0/10

   No evidence anywhere in the pack of email aliasing, masked/burner address generation, or similar identity-protection features for switchers; Missive is an email client/collaboration tool, and evidence covers team inboxes, MCP/AI integrations, and SSO, none of which address address masking.

   ⚑ flag

2. switcherThe client protects me from senders' tracking — blocking read pixels by default — and is transparent about what it does with my mail data

   weight 2 · round drawn
   Shortwave—none0/10

   No evidence anywhere in the pack describes Shortwave blocking sender tracking pixels, nor does it detail transparent data-handling practices for mail content; the only related community evidence (comm-6, comm-7) actually raises unaddressed privacy concerns about syncing sensitive mail and sharing content/metadata with third-party vendors. missing for 10: any mention of read-pixel/tracking-pixel blocking, any transparency documentation on mail data handling, and evidence rebutting the third-party data-sharing concerns.

   • [community] “Privacy concern: user worried about syncing sensitive emails (OTPs, bank/SSN emails) to Shortwave's servers and wished for a denylist to exc…”
   • [community] “User quoted privacy policy allowing sharing of email content/metadata with third-party vendors and said 'Hard pass' given business email con…”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence pack item mentions tracking-pixel blocking, image-loading proxying, or a documented privacy policy explaining what Missive does with mail data. The only related community evidence shows a user learning mail routes through Missive's servers and declining ('Thanks, but I pass'), which does not demonstrate a pixel-blocking feature or proactive transparency documentation.

   • [community] “User asked if Gmail/Yahoo emails pass through Missive's servers. After being told TLS is used but data does route through Missive's servers,…”

   proof ↗⚑ flag

Migration

1. switcherImport my complete mail history and contacts from my old provider or client

   weight 1 · round to Shortwave
   Shortwave~partialcommunity4/10

   Shortwave is built directly on Gmail's APIs, so it can pull in an existing Gmail account's aliases and signatures (one user reported it 'imported all my aliases and signatures' during onboarding), but this is only a Gmail-to-Shortwave migration, not import from another provider/client like Outlook or Yahoo — a security-focused user explicitly noted 'it only works with Google servers.' Additionally, a documented free-plan limitation caps historical search import at 90 days, undercutting 'complete mail history.' Missing for 10: evidence of contacts import, support for non-Gmail providers, and confirmation that paid plans truly import full history without gaps.

   • [community] “'I must say I loved it. In 10min I cleared my inbox which I was postponing for a few weeks... it imported all my aliases and signatures.' Us…”
   • [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”
   • [community] “Security-focused user: 'there is no way I could use a web mail client for security reasons (as a security consultant, we use PGP a lot and n…”
   • [community] “User complaint: 'all these apps either want gmail way too many gmail permissions, and/or are hosted... I'm trying to get rid of gmail lol.'”

   proof ↗⚑ flag

   Missive—none0/10

   No evidence in the pack discusses importing mail history or contacts from another provider/client (e.g., Gmail/Outlook migration, IMAP sync, contact import tools). Evidence covers AI/MCP features, collaboration, search filters, and pricing but nothing about onboarding migration or historical data import.

   ⚑ flag

Search

1. power-userSearch is fast and precise — operators, filters, and ranked results across my full mail history

   weight 2 · round to Missive
   Shortwave!disputedcontradicted4/10

   Shortwave's AI assistant is documented to 'search your entire email history' (shortwave-docs-12/28), but community evidence shows the free plan doesn't import emails older than 90 days before signup for search, contradicting the 'full mail history' claim, and no evidence describes search operators, advanced filters, or ranked-result mechanics. Missing for 10: documented search operators/filters syntax, ranking algorithm details, confirmation that paid tiers truly cover unlimited history without caveats.

   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more”
   • [claimed-docs] “it can read threads, write drafts, search your entire email history, check your calendar, and more.”
   • [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”

   proof ↗⚑ flag

   Missive~partialclaimed3/10

   Evidence confirms Missive has search filters (Type: Internal/External, Date range) and a command-bar search that can query across messages, contacts, or a specific label, but there is no documentation of search operators (from:, subject:, boolean, etc.), relevance ranking, or explicit assurance of full-history indexing/performance at scale. Missing for 10: documented search operator syntax, ranked-results behavior, evidence of speed/precision across large mail archives, and independent corroboration of search quality.

   • [claimed-docs] “The Type (Internal / External) and Date range filters in search no longer stay greyed out until you enter a search term.”
   • [claimed-docs] “The Type (Internal / External) and Date range filters in search no longer stay greyed out until you enter a search”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”

   proof ↗⚑ flag

Shortcuts

1. power-userDo everything from the keyboard — comprehensive shortcuts and a command palette — in an interface fast enough to never make me wait

   weight 3 · round to Missive
   Shortwave—none0/10

   The evidence pack contains no mentions of keyboard shortcuts, a command palette, or performance/speed benchmarks — all citations focus on AI features, integrations, and collaboration tools. Absence of evidence for this applicable axis (email clients commonly tout keyboard-driven UX, e.g. Superhuman comparisons appear in community items) yields 'none' rather than 'na'.

   ⚑ flag

   Missive~partialcommunity6/10

   Missive documents a command bar (⌘/Ctrl+K) supporting search, snooze, and other quick commands, plus configurable swipe/keyboard shortcuts, which is direct evidence of keyboard-driven command palette functionality. However, there's no comprehensive shortcut list, no dedicated performance benchmarks, and community comments call the UI 'unintuitive' with 'design flaws' though also 'snappy' — mixed signal on speed/polish. Missing for 10: a full documented shortcut reference covering all major actions, explicit performance/latency claims, and independent hands-on confirmation of speed and keyboard completeness.

   • [claimed-docs] “You can also snooze by swiping a conversation (configurable in Settings > Preferences > Swipes), or by opening the command bar with ⌘/Ctrl +…”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”
   • [community] “"We choose Missive for now because Missive feels like a proper snappy desktop app and is vastly cheaper ($15 vs $50 per user). Front feels l…”
   • [community] “"I fear that we will eventually switch to Front because Missive is unintuitive or (please someone build that) Gmail with collaboration featu…”

   proof ↗⚑ flag

Channels

1. team-leadThe same inbox also handles adjacent customer channels — SMS, WhatsApp, social, or live chat — beside email

   weight 1 · round to Missive
   Shortwave—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Missive~partialclaimed6/10

   Pricing docs explicitly list "Email, SMS, social accounts" as channels handled in the same inbox, and developer docs mention support for "custom channels" via API, confirming Missive unifies email with at least SMS and social channels. However, there is no explicit evidence of native WhatsApp or live-chat channel support, only generic 'custom channels' extensibility. Missing for 10: explicit WhatsApp integration, native live-chat channel, and independent confirmation of multi-channel unification in practice.

   • [claimed-docs] “Email, SMS, social accounts”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webhooks, and custom channels for full customization.”
   • [claimed-docs] “Missive developer tools: REST API, UI integrations, webh”

   proof ↗⚑ flag

Routing

1. team-leadAssign conversations to teammates and route incoming mail with rules so ownership is explicit

   weight 2 · round to Missive
   Shortwave~partialcommunity3/10

   Shortwave offers team comments and @mention to loop teammates into a thread (giving them access to the email) and custom AI filters that can label/archive/star via plain-English rules, but there is no evidence of an explicit 'assign conversation to teammate' ownership feature or rule-based routing of incoming mail to specific team members/inboxes. missing for 10: explicit conversation assignment/ownership feature, mail routing rules tied to teammates, evidence of shared/team inbox queue management.

   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
   • [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Missive✓fullclaimed8/10

   Missive's docs explicitly describe assigning conversations to a team or specific person while maintaining visibility (missive-docs-6), shared inboxes/distribution lists (missive-docs-32, missive-docs-28), and automated routing via rules (up to 1000 rules per missive-docs-11/25/36), directly matching the story's ask for explicit ownership assignment and rule-based routing. Missing for 10: independent/hands-on corroboration of rule-based mail routing in practice, and more detail on how rule conditions/criteria are configured.

   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”
   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other’s toes.”

   proof ↗⚑ flag

Shared inbox

1. team-leadWe can discuss an email in an internal side-thread — comments and @mentions beside the message — instead of forwarding copies around

   weight 2 · round to Shortwave
   Shortwave✓fullclaimed8/10

   Shortwave's Team Comments feature explicitly lets teammates privately discuss an email in-app rather than forwarding, with @mentions that grant the mentioned teammate access to the comment and the email — directly matching the story. Missing for 10: independent/hands-on corroboration of the comment-thread UX beyond vendor blog posts, and detail on comment threading/notification mechanics.

   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
   • [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave”
   • [claimed-docs] “Something special happens when you @mention a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Set up triggers to draft replies when emails arrive, add comments for your team, organize threads into todos, and connect to 3,000+ other ap…”

   proof ↗⚑ flag

   Missive~partialclaimed5/10

   Missive's docs point to team collaboration around conversations — 'collaborate behind the scenes without changing your workflow', 'chat with your team' in groups/spaces, and 'compose emails together, get reviewed in real time' — which align with discussing a message internally rather than forwarding it. However, none of the evidence explicitly names a side-thread comment feature or @mention tagging mechanic attached to a message. missing for 10: explicit documentation of inline comment threads on conversations, explicit @mention functionality, and independent/hands-on confirmation that this replaces forwarding workflows.

   • [claimed-docs] “See what’s going on, know who’s doing what, and collaborate behind the scenes — without changing your workflow.”
   • [claimed-docs] “collaborate behind the scenes — without changing your workflow.”
   • [claimed-docs] “Chat with your team. In groups, dedicated team spaces, or one-on-one.”
   • [claimed-docs] “Chat with your team. In groups, dedicated team sp”
   • [claimed-docs] “Compose emails together, get reviewed in real time, and share attachments.”
   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”

   proof ↗⚑ flag

2. team-leadMy team works shared inboxes together — shared accounts or team channels where everyone sees the same conversation state

   weight 3 · round to Missive
   Shortwave~partialcommunity5/10

   Shortwave offers team comments and @mention that grant teammates access to specific emails/threads (shortwave-docs-10,11,34,37), enabling some shared visibility and discussion. However, community evidence explicitly questions whether Shortwave's 'Bundles'/Workspaces model can replace true shared/team inboxes as found in dedicated tools (shortwave-comm-4), and there is no direct documentation of a shared-account or team-channel inbox where the whole team sees identical conversation state by default. Missing for 10: explicit shared-inbox/team-channel product feature, documentation of multi-user access to a single mailbox, and confirmation that collaboration extends beyond per-email comments to full inbox-level shared state.

   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave, so you can plan how to respond together”
   • [claimed-docs] “Something special happens when you `@mention` a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Something special happens when you @mention a teammate in a comment – they suddenly get access to not just your comment, but the email too”
   • [claimed-docs] “Team comments let you privately discuss an email with your team directly in Shortwave”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Missive✓fullcommunity9/10

   Missive's core product docs directly describe shared/team inboxes with multiple people working the same inbox without conflict, conversation assignment while maintaining visibility, distribution-list-to-shared-inbox mapping, per-action audit logging, and dedicated team spaces/channels — exactly the shared-conversation-state model the story describes (missive-docs-6, missive-docs-9, missive-docs-19, missive-docs-28, missive-docs-32, missive-docs-35, missive-docs-30/48). Independent community commentary corroborates it is used specifically for team email collaboration (missive-comm-3), and no evidence contradicts the shared-inbox mechanics themselves (complaints found are about general UX/bugs, not this capability). Missing for 10: a hands-on third-party account specifically confirming real-time shared conversation-state syncing across users (vs. general collaboration praise).

   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”
   • [claimed-docs] “Every action within Missive is logged, so you know who did what, and when.”
   • [claimed-docs] “Give each team a tailored space so they can seamlessly focus on their work.”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other’s toes.”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Have multiple people work out of the same inbox, without stepping on each other's toes.”
   • [claimed-docs] “See what’s going on, know who’s doing what, and collaborate behind the scenes — without changing your workflow.”
   • [community] “"I love Streak for singleplayer but prefer Missive or Front for collaboration."”

   proof ↗⚑ flag

Followups

1. power-userSnooze conversations and set follow-up reminders that resurface a thread if nobody replies

   weight 2 · round to Missive
   Shortwave~partialcommunity4/10

   Community evidence confirms Shortwave has a snooze feature (comm-10 references 'snoozed emails' behavior), implying threads can be snoozed and resurfaced, but no evidence describes a follow-up reminder that resurfaces a thread specifically when nobody replies. Missing for 10: dedicated docs on follow-up/no-reply reminders, evidence of reminder triggers tied to reply detection, and confirmation of default snooze durations or scheduling UI for this specific workflow.

   • [community] “Free plan limitation noted: emails from more than 90 days before signup aren't imported for search, and snoozed emails past that window won'…”

   proof ↗⚑ flag

   Missive~partialclaimed6/10

   Missive's docs clearly document snoozing a conversation until a specific time so it resurfaces in the Inbox, including quick access via swipe or command bar (missive-docs-supp-1, missive-docs-supp-2). However, there is no evidence of a distinct 'follow-up reminder' feature that resurfaces a thread specifically if nobody replies (as opposed to a fixed snooze time) — the story's reply-tracking trigger is unevidenced. Missing for 10: documentation of a no-reply-triggered follow-up reminder mechanism, and any independent/hands-on confirmation of snooze/reminder reliability.

   • [claimed-docs] “Snoozing temporarily hides a conversation until a specific time, then brings it back to your Inbox. Use it to defer emails you can't deal wi…”
   • [claimed-docs] “You can also snooze by swiping a conversation (configurable in Settings > Preferences > Swipes), or by opening the command bar with ⌘/Ctrl +…”

   proof ↗⚑ flag

Inbox structure

1. power-userSelect many conversations at once and archive, label, or mark them done in one stroke

   weight 1 · round to Shortwave
   Shortwave~partialclaimed4/10

   Shortwave's docs mention bulk-oriented behaviors—custom AI filters that automatically label/star/archive matching emails, and a one-click 'sweep away the rest' declutter action—that imply multi-conversation bulk actions, but there is no explicit mention of manually multi-selecting conversations and applying archive/label/mark-done in one stroke. Missing for 10: explicit multi-select UI documentation, confirmation that labels/archive/done can be applied simultaneously to a manual selection, and independent/hands-on confirmation of this specific workflow.

   • [claimed-docs] “Take control of your inbox with custom AI filters. Automatically label, star, archive, and more with scripts you write in plain English.”
   • [claimed-docs] “Identify important emails & todos with a single click. Sweep away the rest.”

   proof ↗⚑ flag

   Missive—none0/10

   The evidence pack covers command bar search, snoozing, canned responses, MCP/AI assistant integration, and team collaboration features, but nothing documents multi-select bulk actions (archive/label/mark done across many conversations at once). Missing for 10: any docs or changelog entry describing bulk selection UI, keyboard multi-select, or batch archive/label/mark-done operations.

   • [claimed-docs] “You can also snooze by swiping a conversation (configurable in Settings > Preferences > Swipes), or by opening the command bar with ⌘/Ctrl +…”
   • [claimed-docs] “Master the command bar: keyboard shortcuts and quick commands. You can use the following patterns to initiate a search: search searc sear se…”

   proof ↗⚑ flag

2. power-userSplit my inbox into focused streams — important, team, newsletters, calendar invites — so triage happens in priority order, not arrival order

   weight 3 · round to Shortwave
   Shortwave✓fullcommunity8/10

   Shortwave's 'Splits' feature explicitly lets users divide one inbox into multiple focused inboxes by importance/type, each in its own tab, directly matching the triage-by-priority story, and independent community feedback (Front power-user) praised the related 'Bundles' grouping as 'top shelf.' Missing for 10: explicit documentation that the default splits match the exact categories named (team, newsletters, calendar invites) rather than just importance-based tabs, and more independent verification of the feature's real-world triage benefit.

   • [claimed-docs] “They’re a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
   • [claimed-docs] “They're a simple way to divide your one big inbox into multiple smaller, more focused inboxes – each in its own tab.”
   • [claimed-docs] “Splits let you handle different types of emails at different times, so you can stay responsive where it matters most.”
   • [community] “Front power-user praised Shortwave's 'Bundles' grouping feature as 'top shelf,' better than Front's tags/folders, though he found Workspaces…”

   proof ↗⚑ flag

   Missive~partialclaimed4/10

   Missive's docs mention rule automation (up to 1000 rules), team spaces, and shared/team inboxes, which could be used to organize conversations by category, but there is no explicit documentation of a dedicated 'streams' or 'focused inbox' feature that lets a user split a single inbox into priority-ordered views (important, team, newsletters, calendar invites) as described in the story. missing for 10: explicit inbox-view/stream creation feature, priority-based triage ordering, and evidence of calendar-invite handling as a distinct stream.

   • [claimed-docs] “Automate your workflows”
   • [claimed-docs] “Automate your workflows Up to 1000 rules”
   • [claimed-docs] “Up to 1000 rules”
   • [claimed-docs] “Give each team a tailored space so they can seamlessly focus on their work.”
   • [claimed-docs] “From distribution lists to shared inboxes”
   • [claimed-docs] “Assign conversations to a team or specific person, while maintaining visibility. And jump in, if needed.”

   proof ↗⚑ flag