Philippe Lehoux
complete
We improved the UX around archiving, closing, and removing from a label.
See this changelog video for the details: https://youtu.be/3rcbH2K7b38?t=69
Rafael Masson
Merged in a post:
Different icons for Archive and Close
Debra Taylor
Kent Wang
Yes, I would like a button for Close, right next to the Archive button
Jonathan Laukenmann
True, but there is also a benefit of having an archive icon for both. It's so that you don't have to switch your thinking from one mailbox to the other. But I agree, the concept of closing and archiving is hard to understand, and a different icon would help here.
Frank Jing
Jonathan Laukenmann: when should we use close vs achieve in team inbox? my understanding is close is a step further so achieve > close > delete
Philippe Lehoux
Frank Jing: The difference between Archiving and Closing is thoroughly explained in this guide: https://missiveapp.com/help/missive-concepts-explained/what-is-the-difference-between-archiving-and-closing
You can read about more Missive concepts explained in the left navigation bar of that page.
Both closing and archiving will archive emails on your email server (Gmail, Office 365, IMAP). In addition, Closing will add the conversation in the Closed mailbox.
In most case, you can simply, close conversations.
Frank Jing
Philippe Lehoux: Thank you Philippe, I read over the guide before this question but it still not 100% on the two concepts.
For instance, when an email comes to our shared inbox and team member A and B are assigned to it.
If team member A finished the email and the ENTIRE issue is revolves, so team member B does not need to do anything. I think we should CLOSE this email, because close will also close& achieve the email for both A and B?
If team member A partially finishes the email, and B still need to work on it. Team A should achieve, and once team B finishes the entire task, then CLOSE the email.
In summary, achieve when remove inbox only from individual inbox, close when the entire issues is done.
Is this the correct approach?
Philippe Lehoux
Frank Jing: Yes, this is a valid use case.