Jason_L 2008-11-10T11:17:20Z It would also be ideal to be able to embed tracking in the email to be able to see whether or not the workflow email was opened by the lead. This basically allows for simple drip campaigns to be setup using workflow only. cmurph 2008-10-28T15:31:43Z this was a big oversight... we need workflow to trigger email alerts to clients... but those need to be logged of course!! mattiasnordin 2008-10-22T07:58:24Z I agree that the email should be tracked. I would also like to have the choice of a confirmation box asking you if you want to trigger a workflow or not. mattiasnordin 2008-10-22T07:58:20Z I agree that the email should be tracked. I would also like to have the choice of a confirmation box asking you if you want to trigger a workflow or not. jasonc11 2008-07-21T12:21:50Z I would completely agree, what's the use of executing work-flow rules and automating your processes if you can't track these activities in the same manner you can manual data input. Seems like without this the automation is practically useless. curth 2008-06-03T18:54:31Z This is badly needed. This is even more critical to us because we use the existence of an email record to the contact to drive updates to our other on premise systems, and the failure to capture the email details has forced us to develop custom Apex and jump through 10 other hoops that I won't get into right now. As a business, we need a system that we can use to capture all interactions with our external customers. The fact that Salesforce.com would build in workflow to send external emails but not track them is a huge oversight and completely ignores one of the key tenets of a good CRM system. bgross 2008-05-13T12:05:23Z Completely agree, this is a needed feature. Unless some field or task note is created a user has not idea an email was sent to a contact or lead; not to mention being able to read what was actually sent. This is definetly a need. hemm 2008-05-13T12:05:23Z Totally agree. This is a lame workaround, but a decent approach is to use a a task action in the same workflow rule that just says the email was sent. This does not meet your requirements, but at least you'll know the workflow rule fired and have some indication that an email went out (or at least was supposed to have) bbseven 2008-05-13T12:05:15Z When a workflow is created the sends an email to a contact, that email should be logged in the contact as an activity. Something one would expect from any CRM system - a touch of the customer requires tracking. axeleik 2008-05-13T12:01:35Z Would be a great feature, also described in Idea http://ideas.salesforce.com/article/show/78836 mlee 2008-05-13T12:01:33Z My company uses Salesforce heavily for lead management. We have a team dedicated to screening leads and updating their Lead Statuses. Based on the Lead Status values, our workflow rules trigger various auto emails to our leads. However, our team can not tell which emails and when the auto emails were sent to the leads since the emails sent by the workflow rules do not get added to the Activity History section. We also need the emails for troubleshooting purposes. This is a very important feature for us (to add auto emails sent by workflow rules to the Activity History section). natek 2008-05-13T12:01:32Z It would be good also to be able to see whether they have opened it or not, as in an HTML email (i.e. track opens, clickthroughs, etc.) JohnBoy 2008-05-13T12:01:35Z I agree, tracking any changes by workflow, including sent emails would be very useful for auditing purposes msnowden213 2008-05-13T12:01:27Z I would like to see activity history tracking on objects with related workflows. For instance, most of ours are email alerts that are sent out, but occassionally I hear that someone didn't get their emails and I have no way of verifying whether they did or not. This would be helpful to see for trouble shooting. heatherp 2008-05-13T11:59:53Z I guess I agree on the configurable so that admins have the option, but it should be up to the admins, not the users. heatherp 2008-05-13T11:59:51Z I guess I agree on the configurable so that admins have the option, but it should be up to the admins, not the users. CraigAllen 2008-05-13T11:59:50Z This should be configurable so that you indicate whether or not you want the workflow activity logged as an activity on the corresponding record. heatherp 2008-05-13T11:59:48Z Well I think it should be an option that the admin decides; however, for me personally, when an email alert goes out, I want it to automatically add that email as an activity so that I can see that 1. it went out and 2. there's a history of it.. Right now, a user will get an auto email alert and can just delete it -no one will ever know it existed. Scott_Jorgensen 2008-05-13T11:59:53Z The tasks are recorded/logged already. Do you want the logging of email alerts to be configurable or required? heatherp 2008-05-13T11:59:44Z When a workflow is triggered, whether it's an auto task or email alert - the system should log those as activities in the history. axeleik 2008-05-06T02:34:39Z This would be an essential addition in order for the workflow to become a powerful automation engine. We are in a retail market and rely heavily on automated processes. bvass 2008-02-22T09:08:06Z Currently, emails triggered via workflow rules and email alerts are not stored in the activity record for the affected lead/contact/etc. We would like to keep a history of all emails send to a lead/contact, even emails sent via the workflow rules. jim_murphy 2008-01-24T06:10:18Z Just plain essential for us. We send customer's license keys for evaluations via workflow rules combined with outbound messages and ultimately and email alert to a contact. Customer's sometimes call to say they didn't receive their eval key and we can't confirm that the email was sent and have to dig to find their key through other records. We need the complete email trail attached to Contact!!! JABBA 2008-01-22T17:29:09Z We use emails sent by workflow automation for lead nurturing. If the lead owner cannot see which emails have been sent it is very difficult to decide when to contact the lead. This is a great facility but activity tracking would make it more practical to use. regman 2008-01-18T06:35:53Z As reported in this other Idea released in Summer 07, automated emails from a workflow are not listed in the activity history. PLEASE record these emails as history on contact/lead records. It is essential, IMHO. ncurham 2008-01-14T12:41:39Z I'm not sure we need to track all history - just being able to see the initial email in the history would be a start. We have a regulatory compliance requirement to record all email correspondence with clients and this bug casues us to fail our commitments. I was told by a salesforce support team member that Activity History only stores "some" of the activities - can anyone point at documentation of what isn't recorded? aldous 2007-12-06T17:17:45Z It is truly important for some organizations to follow up emails sent by workflow automation. There is an important downside: the activity history might have so many entries that reading them could be very difficult. Therefore, an option to make this work properly could be that any administrator may choose which emails should be shown in activity history and which emails must not. khawkins 2007-12-06T17:17:44Z We use the function to alert other team members to activity and would like to automate the email process - emails sent to contacts when they sign up, 2 weeks after sign up, when they schedule an appointment. It's frustrating when we can't track open rates or even know if an email was sent... A downside? I guess that would depend on how management in some organizations use workflow. Couldn't it be set up to only show emails sent to the contact's email - not to other salesforce users? robcohen 2007-12-06T17:17:44Z I agree with above, but wonder if anyone sees a downside to recording emails sent from workflow in contact activity history. Not knowing the downside makes it seem more like an oversight than a missing feature. khawkins 2007-12-06T17:17:27Z Needs to have the same functionality as the auto-responder in Web-to-Lead. That email appears in the HTML Email Status; all users can see when and which emails a customer has been sent. If we cannot see that, it's almost impossible to talk to customers or answer specific questions.