@Matthew_Oates - Here are my thoughts:
Of course we’d all prefer that our chosen provider, Asana, handle all incoming modes of communication (email, chats, tweets) and put them into Asana for handling. But the problem isn’t quite as easy as that, because of these considerations:
Email inboxes get marketing email, automated sales solicitations, system alerts and lots of internal email – all non-client communications. They must be intelligently ignored, without requiring users to manually approve/unapprove senders, otherwise your Asana will get flooded, and all you are then doing is moving the problem from email to the Asana inbox.
As you have noted, the reason we want a better “emails and Asana” solution is because of client management requirements. Clients are most certainly not going to want to use Asana because their agency/vendor uses it (with some exceptions).
With client emails there are cc’s to stakeholders both within the client’s organization, and yours. Sub-threads are created with lesser/fewer people. Forwards happen to ensure privacy and discuss sensitive issues. Automatically moving all such emails to Asana can cause privacy problems (people seeing emails they should not be seeing).
Just putting emails into Asana isn’t enough, you have to be able to, after assigning them to people, reply to them. Having to go back to the email app then defeats the purpose of putting these tasks in Asana. So there has to be replies from within Asana, the ability to see who you’re replying to, and synchronization of all replies from the outside to the Asana tasks.
Asana’s core technology is a tracking system, with the first application being task management. But, as the company is going towards larger businesses as well, it’s not feasible to think that Asana will solve all problems that the businesses will demand. Email management is one such area, and there are a number of companies that are focused on that, including ours, Onboardify.
[Now, since you mentioned that you got 50 tasks a day, presumably by using our Dossier app, that’s where the routing comes in. You can choose which clients/senders get ignored, which clients are accepted, and even route emails from specific clients to specific Asana projects. I don’t want to digress too far into how to set up our 3rd party app, but wanted to mention it, so you know the app is designed to help you reduce your email.
For example, we connect to CRMs such as HubSpot and Salesforce – so, if your client already exists there, his/her emails get routed. If they don’t, we don’t put it into Asana. That’s an example of a mid-size to larger enterprise use case].