Feature Requests

I’d like to have an option for Out of Office auto-replies to be sent as a separate conversation, while keeping the incoming email in its original conversation thread. Current behavior: Incoming email stays in the conversation OOO auto-reply is added to the same conversation thread Desired behavior: Incoming email stays in the original conversation OOO auto-reply is sent as a separate outgoing conversation/message The auto-reply would ideally only appear in Sent, without being added to the original Inbox conversation This would help keep customer conversations clean and avoid mixing automatic absence messages with the actual email thread. A setting such as: “Send Out of Office auto-reply as a separate conversation” would be very useful. I tested possible workarounds using Rules and Move email to new conversation, but as confirmed by Support, rules do not trigger other rules and the incoming email is always moved together with the reply. This could remain optional, with the current behavior kept as the default.

I think the ability to generate a comment using the MCP server would be really helpful.

At the moment when I request a draft, I also sometimes want to create a relevant task to myself, or add summary note. Would be so much easier to do this via AI chat, rather than manually, as certain context can be easily added to the task that way.

Would be great to see the out of office icon, while tagging them in a conversation.

Our team would like labels to be displayed below the subject line or in a different location. Right now, labels compete with the subject line. If there are a lot of labels on an email thread - the subject line gets smaller and smaller until we can no longer decipher what email we are looking at without reading through some of the emails.

My AI assistant adds a triage note to each conversation via POST /v1/posts. It works well, but every post bumps the conversation's last activity and reorders my whole mailbox, and deleting the post doesn't revert the date. A silent: true option that skips the activity bump would make posts usable for annotation-style integrations, not just conversation-driving ones. Related: the notification object is currently required, which forces noise even when none is wanted.

The drafts API can create a draft and delete one, but not change one. So when an AI agent stages a draft and you want a redraft, the only option is to delete it and start over. An endpoint to update a draft's body, subject or recipients by ID would let agents iterate in place instead.

Could you add support for closing/reopening conversations through the MCP connector? This would let automations mark a conversation as done once a reply has been sent, without requiring manual action in the Missive app.

Currently you can schedule an email to send later but it isn't possible to preview the message without editing the draft. It would be great if you had a Preview button so it then removed the semi-transparent overlay to read it without opening it to edit draft.

Today printing is done message by message (menu > Print). There is no way to get an entire conversation in a single document: Cmd+A only selects the last message displayed, and the JSON export of the settings cannot be read or used as an archive. Request: an “Export conversation to PDF” option at the conversation level, generating a single document containing all messages in chronological order, with the headers of each message (From/To/Date/Subject) and a list of attachments. Uses: transmit a complete exchange to a legal department or to an external medium, archive written proof of an exchange, create a dispute file. Bonus: that the AI assistant (or the MCP) can trigger this export. --- EN version --- Export/print a full conversation as a single PDF Printing is currently per-message (menu > Print). There's no way to get a whole thread as one document: Cmd+A only selects the last message, and the JSON export isn't readable as an archive. Requested: an “Export conversation to PDF” action at conversation level, producing one file with every message in chronological order, including per-message headers (From/To/Date/Subject) and the attachment list. Use cases: sending a complete exchange to legal or to an external support team, archiving written proof of a thread, building a dispute file. Bonus: let the AI assistant/MCP trigger that export.