Feature Requests

Currently, the Missive API does not expose the parent-child relationship between comments — there is no way to determine which comment a given comment is replying to. Additionally, the create post endpoint does not support creating a comment or post as a reply to an existing one. For our bot integration, these features would be extremely valuable for maintaining context and enabling threaded conversations. We’d greatly appreciate support for: 1- Including a parent_id or similar field in the comments API response. 2- Allowing create post to specify a parent_id to create replies programmatically.

Feature to create a break in a contacts Dialpad sms and call thread manually to separate exchanges. Repeat customers have many conversations. Not all need shared the same.

E.g. user creates a deal in Pipedrive integration, show a simple view of the deal in the conversation and by which missive user. E.g. user created a task in the Asana integration, show a simple view of the task in the conversation and by which missive user. E.g. user creates a contact in Hubspot integration, show information about the action taken like "Hubspot contact created" by..... in the conversation.

Currently AI draft reply gives no signature, and no easy button to add to the draft so only option is to copy and paste from another email. And draft new email you cant set or have AI fill in the to and subject line.

It would be helpful to have the ability to pause or snooze mobile notifications until a specific date/time. For example: If I go to lunch, I could snooze notifications until 12:00 PM, at which point they would automatically resume. This would also be useful for meetings, vacations, or any time I step away temporarily. A similar feature exists in the Nextiva VOIP App, where users can set their status to "Do Not Disturb" and specify a return time. Once that time arrives, the app automatically switches the status back to "Available." This functionality would greatly improve flexibility and reduce the need for manual status management.

Can we please have the ability to merge conversation using the JS and API end points. I have many instances where I get emails related to one task from several different groups and I want to be able to keep these all under the same conversation. The built in auto merge function does not work if these emails are not in the same team inbox when a new email is received.

I'd love to be able to create new rules with the JS and API endpoints. I use automations to process lots of conversations and being able to use an automation to create rules on the fly would help alot.