Feature Requests

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

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.

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!

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.

Sometimes a support question arises in a service delivery thread, it would be good to be able to fork the conversation then so the support team owns a new thread from there, while the original thread continues with the service delivery team. Ideas could be duplicate or fork, or reply in a new conversation the same way you have about forward and resend.

This should be able to pin the Mentions list, like the Comments Tab. This will be convenient and productive to see who mentions you and go over it not just as a notification which you already have.

We want to be able to generate tables in the design editor so that we can present simple things like price lists in a structured way. Similar to what is possible with Thunderbird.

So this request is a little out there, but leaving it here anyway. I would love the option to sort emails from Oldest to Newest. Not all the time, but as an option. When emails are ordered new to old, i end up reacting the the newest emails and ignoring the oldest. I would like to start attending to emails in a less-reactionary, First-In-First out process. Another idea would be to allow the inbox to be filter by date. Essentially, filter out any emails that were received same-day and only show emails that are at least 1 day old. This is taken from Tony Hsieh's "Yesterbox" process: https://yesterbox.com/