> A better solution might be to automatically save incoming email to the company CRM and also append outgoing messages to the appropriate contact. That way, no-one has to remember to add records. The next step would be to expose that information directly in the email client so employees don't have to go hunting for info (if they can even be bothered).
We've been working on http://noosbox.com/ to solve exactly this problem. It integrates directly into GMail (on Google Apps) or outlook to allow you to save conversations against a specific contact.
The problem here is that these are fragmented systems, each trying to solve specific needs for the company (tracking sales/prospects, tracking support queries) rather than looking at the customer's perspective.
All incoming and outgoing email should be stored in a way that anyone can easily see the conversation history (and people should be checking it before they respond). As I see it, that's the problem the post is actually describing. Having one email address is a method of trying to achieve this but IMHO it's not how it should be done.
The problem with CRM systems as I see them is that most of them require users to click away from the email to read the full conversation history. Even worse than that, employees usually have to manually add a conversation to the CRM to begin with.
A better solution might be to automatically save incoming email to the company CRM and also append outgoing messages to the appropriate contact. That way, no-one has to remember to add records. The next step would be to expose that information directly in the email client so employees don't have to go hunting for info (if they can even be bothered).
I don't think most customers actually care where their reply comes from (e.g info@, sales@, bob@...) as long as they get a response and their issue is resolved.
Edit: I agree with the post that customers should not have to figure out which address to use from the website. Just give them one