Per-account Done/Later views

100% agree with this - very strongly! This change has been the single worst update to the UI for us. 

This is particularly annoying when you integrate multiple channels (i.e., SMS, multiple Email accounts, etc).

It is not intuitive to be a list of random SMSs and emails from several different addresses in one long list of ‘Done’ or ‘Later’. Typically you would be looking for ‘SMSs that I have sent’. 

I know this is achievable by filtering ‘Done / Later’ by inbox - but it is so, so, so cumbersome. The existing UI on mobile is actually create - where you have the option of viewing Open, Archived, Snoozed within each inbox easily.

I wish we can see assigned to myself in each inbox, I know i can search but I wish it would be pre filtred for this

I very strongly second this - it has become a real challenge since this change came into force and we often end up back in Gmail. Which has it’s own challenges since Front doesn’t sync read status back to Gmail

Ditto on this! That was the number 1 complaint from all my users. They know which inbox they archived something and can easily locate it before, now they hate scrolling through archive to find it. The search function is great if they remember exactly what they are looking for. But we work in a fast pace high volume environment and switching back and forth between conversations, sometimes conversation gets archived accidentally.

This was a complaint that a few of my power users brought up and i did not experience until this week when i realized how hard it was to filter thru them myself to find accidental archives which was what prompted me to look. 

I’m already overly disappointed with how weak search is with its default presets so i spent much to much time looking for a vital piece of information. 

100% agree with this, which has been raised here as well (in the comments): 

Please bring back the ability to filter for Snoozed/Archived within any folder (without going into complex searches) 🙏

Appreciate the feedback! I hear you on the navigation challenges the redesign brought. We don’t have any plans to roll back the Open, Later, Done structure at this time.

Instead, I’d like to ask you all to try views to solve the problems you’re mentioning in the comments. I’m really curious if you can recreate what you want to see using views, since views retain the status across the top in the conversation list, and will save the filters you apply. If there is friction after that, I’d like to know.

​@bpr when you say “saving filters by Done/Later state” do you mean you want a view that just shows those states? Or just default opens to that state?

​@david_vien are all those channels connected to personal or shared inboxes?

​@Liz I remember your feedback. Are you using views at all today?

​@conniechen Views don’t feel like the right fit for this use case.

We rely on them for high-level monitoring - things like high-priority tickets, Tier 1 customers, SLA breaches/warnings, and load balancing. Trying to use them for individual inbox management, especially across the many folders in our workflows, creates unnecessary complexity.

It also doesn’t feel realistic to expect teams to build and maintain separate “Snoozed” and “Completed” views for every subfolder, just to replicate what should be a straightforward inbox feature

Hi ​@conniechen . Thanks for the response! I actually wasn’t aware the Views still had the status across the top. Odd that it’s been kept there but not in inboxes. In either case, a View cannot be created on Personal inboxes, it can only be created on Shared inboxes. Our use-case for Front was that our staff would all manage multiple personal inboxes across multiple clients, and then use it for @mentioning other team members into emails when help was required. So it was less about shared inboxes, and more about collaboration on emails coming into individuals’ mailboxes. There is no way, with the redesign, for staff to easily see, per-client, the archived/snoozed emails without multiple clicks to apply filters, each and every time.

​@bpr Got it! I understand your use case and the challenge the redesign introduced. Let me share this feedback with my team.