Feature Requests

Email has a built-in interaction boundary in Missive: the subject line. Each new subject from the same address creates a new conversation. SMS has no equivalent — every message from a phone number lives in one conversation forever. For any business with repeat customers, that's one unbounded thread per contact, growing indefinitely. Three paths — any one solves it: **Accept subject / thread_id / external_id on SMS drafts.** When different from the active thread, open a new conversation for that number. Mirrors email. (Currently silently dropped for SMS — support confirmed it's unsupported.) Add a "Close SMS conversation" action. Next inbound creates a fresh thread; old thread stays searchable on the contact. Expose conversation metadata at draft time that Missive honors as a secondary threading key. Why it matters: CRM and AI over SMS get dramatically cleaner — no prompt contamination, no custom filter layers per integration. Team triage stops being "read six months of history to know what today is about." Heavy SMS accounts are heading toward 10,000+ messages per contact with no archival path. Not a new concept — just SMS catching up to email's threading model.

Please, dear god, have a way to create read-only API keys.

There is a clear and growing shift among EU companies, public institutions, and regulated sectors toward non-US, sovereign software solutions. This trend is only going to accelerate in the coming years as awareness increases and legal, regulatory, and procurement pressure on EU organizations continues to grow. Many organizations are already actively moving away from US-controlled cloud services, even when data is technically hosted in EU regions. As a Canadian company, Missive is in a unique position. Being non-US is already a strong foundation and a real advantage. However, the current infrastructure setup makes it difficult to position Missive as a truly sovereign option for EU customers. From my perspective, the main blockers today are: Infrastructure hosted on AWS As I understand it, Missive is primarily hosted on AWS. Even when AWS regions are located in the EU, the service remains subject to US jurisdiction. For many EU organizations, this alone disqualifies a product. An optional deployment on an EU- or Canada-based cloud provider, owned and operated outside the US, would materially change this. Limited EU-centric email integrations While IMAP is supported, it feels second-class in practice, especially around search reliability and performance. Microsoft and Google are clearly the primary integrations today, which again pushes users toward US-based ecosystems. Supporting at least one EU-based email provider at API level would be a meaningful improvement. Data flowing to AWS even with EU email hosting At the moment, it is possible to host email entirely on EU servers via IMAP, but once Missive is used, message data is still processed and stored on AWS. This defeats the purpose of running EU-only email infrastructure and is a real concern for compliance-driven users. What I am suggesting is an optional “EU sovereign” track, for example: EU-only infrastructure on a non-US cloud provider Clear guarantees around data residency and control This would result in a setup that EU customers can reasonably defend during legal, compliance, and procurement reviews. I believe this would be a strong differentiator for Missive and open the door to customers who currently cannot even consider US-adjacent solutions at all, regardless of features or pricing.

Right now if i need to bring an email or thread in Claude as context, it's a bit of a hassle. Would love to be able to copy the content as markdown.

Auto-select signature based on last teammate reply in shared inbox Hi Missive team, We use Missive with a shared inbox setup where multiple teammates reply from the same alias (e.g. info@company.com ), each with their own personal signature. At the moment, signatures are selected based on the alias itself, not based on which teammate previously handled the conversation. This means we constantly need to manually switch signatures when continuing a thread. It would be extremely useful if Missive could optionally: • remember which teammate last replied in a conversation • automatically apply that teammate’s default signature on the next reply • or offer a setting like: “Use signature of last replying teammate” This would make shared inbox workflows much smoother and reduce mistakes/inconsistencies in communication. I believe this would be valuable for many teams using shared aliases for sales or customer support. Thanks!

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, you can set the internal status to “Away” for another team member (e.g., if they are on sick leave and cannot do so themselves). However, at the moment I cannot enable the automatic out-of-office message for such users (not even as an administrator). https://missiveapp.com/docs/core-features/status-and-out-of-office/personal-auto-response My suggestion is to add an option that allows the admin to add such a message. And even better: if we could define one or more standard out-of-office messages (in our case, in German and English) (i.e., different ones for vacation or sick leave) and have the system generate a dynamic response based on the start and end dates of the absence.

I know that some basic formatting was added, but it presumes the person knows markdown and when pasting it often ends up a mess. Slack-level formatting should be the standard here. We often find that to add a comment to a team member, we generate a PDF or doc and attach it to the comment just because otherwise it looks a mess. Especially when you have AI that can make a summary, and you want to paste that back as a formatted message, we often screenshot and paste that because it preserves the nice formatting

When drafting an email and I use the "Ask AI" feature within the email (not the sidecar, but highlight text in the email, hit ask AI, and start interacting with it). If I get a notification from another app and click into it or even X out the notification - Ask AI disappears and I have to start all over again with the request. It would be nice if when Ask AI is being used and it loses focus, it doesn't yeet the work done into the ether and have to start over again.

When changing a profile picture, it refuses to update if the file is over 500kb or 1024px in height. Respectfully, that's ridiculous for a paid product. Process the image in the app.