Feature Requests

Please offer a possibility for archiving/pausing memberships. I have an employee who will come back in 2 or 3 years but I dont want to delete all of her comments.

Please build an official MCP (Model Context Protocol) connector for Missive so that external AI agents and tools (Claude, ChatGPT, Cursor, etc.) can interact with Missive data in a secure, structured way. What we're asking for: An official, supported MCP server that exposes Missive resources — conversations, messages, contacts, labels, assignments, and drafts — to any MCP-compatible AI client. Why this matters: MCP is quickly becoming the standard protocol for connecting AI assistants to external tools and data sources. Without an official Missive MCP connector, users are forced to build their own unofficial integrations (some community members have already done this), which are unsupported, fragile, and lack proper auth scoping. With an official MCP connector, Missive users could: Ask an AI agent to summarize open conversations or flag urgent threads Create and send draft replies via an AI agent that has context from multiple tools (CRM, calendar, notes, etc.) Build automations that read Missive data alongside other MCP sources (e.g., Pipedrive, Notion, meeting transcripts) Use Missive as a full participant in multi-agent workflows Suggested capabilities (read + write): Read: list/search conversations, fetch message threads, get contact details, retrieve labels and assignments Write: create drafts, send messages, apply labels, assign conversations, update contact fields Why now: MCP adoption is accelerating rapidly across AI clients (Claude Desktop, Cursor, Windsurf, etc.). Teams that rely on Missive as their communication hub deserve a first-class integration, rather than having to work around the gap with screenshots or DIY solutions. This would be one of the highest-leverage integrations Missive could ship — it opens Missive up to the entire AI agent ecosystem at once.

Currently when you send a message in an old conversation that's deep in your inbox, that conversation doesn't move back to the top of your inbox like it would in any other messaging app. Only when there's an incoming message does it get hoisted. This is a mild nuisance.

We run a commercial real estate brokerage on Missive and are heavy users of rules and labels. Two feature requests, framed from the workflow side: Bidirectional trigger support in a single rule Currently the rule engine scopes each rule to one direction: "Incoming email" or "Outgoing email" as separate trigger types. Any workflow that needs symmetric behavior (label a conversation with a contact regardless of who initiated it) requires creating and maintaining two parallel rules with duplicated conditions and actions. There is no linkage between them, so they drift: the incoming rule gets updated, the outgoing mirror doesn't, and outbound mail silently misses labels and automations. Request: expose direction as a condition within one rule (checkboxes/toggles for Incoming, Outgoing, or Both) rather than as two distinct rule types. Same conditions, same actions, one object to maintain. Label-scoped rule visibility and editing Today rules live in a flat global list, and there's no way to answer "which rules touch this label?" without reading every rule. Request: from any label's settings, surface all rules that reference that label (as a condition or an action) and allow editing them inline from that view. Bonus: when creating a new label, offer rule creation in the same flow so the label and its automation ship together. Same concept would be powerful at the contact level: attach a rule to a saved contact so any conversation to or from that address auto-applies their label, bidirectionally, defined once. The underlying issue is that rule setup is a multi-step, duplicative process from the user's side, and rule management has no association with the objects the rules act on. Consolidating direction into one rule and making rules discoverable from the label would fix both. Happy to walk your product team through our setup as a real-world use case.

For many of us, Snooze isn’t just a way to hide an email until later. It’s how we manage almost every active conversation in our inbox. But right now, Snooze feels disconnected from the rest of Missive. It can’t trigger Rules, it adds extra steps, and conversations can lose important workflow context when the snooze ends. A few thoughtful upgrades could make Snooze one of Missive’s most powerful workflow tools: Trigger Rules when conversations are snoozed or unsnoozed Please add Rule triggers for: - Conversation is snoozed - Conversation is unsnoozed - Conversation snooze ends I originally expected “Conversation is reopened” to trigger when a snoozed conversation returned to the Inbox. Missive Support clarified that Snooze is treated as a separate state, and there’s currently no way to trigger actions when a snooze ends. This means we can automate almost every stage of a conversation except the exact moment it returns for action. These triggers would let teams automatically assign conversations, add or remove labels, send notifications, update statuses, and run other essential actions. Add “Close conversation” to the Snooze window Please add a simple “Close conversation” checkbox when snoozing. For those of us who close every conversation after snoozing it, this would save an extra action on virtually every email we handle. It could also include an optional setting to close the conversation automatically after it has been snoozed for a chosen amount of time. There’s already a separate feature request for this, and the interest from other users shows that this is a real, recurring workflow issue. Keep the current assignee when a snooze ends When “Snooze for everyone” is used on a shared conversation, there should be an option to keep it assigned to the same person when it returns. The assignee is still responsible for the conversation. Snoozing it simply means they’re waiting until the appropriate time to act. Ending the snooze shouldn’t interrupt that ownership. Add “Snooze until Desktop” Sometimes you see an email on your phone but can’t properly handle it until you’re back at a computer. A “Snooze until Desktop” option could return the conversation when the desktop app is next opened, instead of forcing users to guess when they’ll be available. This request already has significant support from other Missive users in another feature request stretching back to 2019. Snooze is already central to how many of us work. These enhancements would transform it from a simple timing feature into a flexible, automation-friendly workflow state. If Snooze is an essential part of how you manage your inbox too, please upvote this request.

An indicator or icon that an email has a private comment attached to it, especially when the email is really long.

Internal team emails don't go back to their inbox unless you are watching them or you are specifically mentioned in them. There's no way to make internal replies reopen a team inbox today.

simply take away the "in progress" option so I don't have to click twice to close a task.

Maybe it's just my ADHD talking but it would be incredibly helpful to have an option to pop out the tasks window for quick visual reference. With multi-monitor setups, there's usually a window arrangement that leaves a small amount of real estate for a subtle small window that you can check back for the next hottest priority. Also, if AI integration is possible, having the tasks be able to auto-update their status based on linked convos and alert user as to changes via convo context would be incredible.

Would love to be able to sort emails being oldest at the top and newest at the bottom (or vice versa)... the way my job works we work in time priority from when something came in first, so having to scroll down to the bottom every time to grab something older is very tedious and annoying.