

#SALESFORCE MASS MAILINGS HOW TO#

Bulk Email (for advanced use and users).Multi-Language Support for Lightning Email Templates.Ability to set the ReplyTo email address and the Sender Display Name.

Ability to provide a plain text body, an html body, or both.Ability to toggle on/off the use of the Salesforce per-user email signature.Any combination of the following input sources, for To, CC, and BCC.Email Templates (both Classic and Lightning) with field merge and letterheads.Rich HTML email bodies that can use all of the capabilities of Flow’s Text Templates, including Bold, Italics, Underline, Bullets and Numbers, Left/Center/Right justification, URLs, images, fonts, and text size.It provides easy access to Salesforce’s single and mass email services, taking the place of Flow’s built-in Send Email action, which is currently something of an underachiever. Though ultimately its only dictating how many instances of each you pass in the array to the send email, which ultimately then governs overall what can be sent anyway.Send Better Email is the latest and best email action for Flow, replacing previous versions of Send Rich Email and Send HTML Email. If you scaling above my earlier example of 50 and working with these objects, this is indeed an additional benefit to those I've described above. As you say there are quite a few more features on the SingleEMailMessage, but if you don't need any of those perhaps the MassEmailMessage has a place. So there is arguably a marginal heap and statement benefit as well. Instead of creating 50 SingleEmailMessage instances each setup accordingly (you'll have to pull the email addresses yourself) to achieve the same. So if you had 50 such Contacts to email you need only have a single MassEmailMessage instance and set a list of those Id's into it. What MassEmailMessage appears to give you is a more optimal coding route if you are focusing on sending to Contacts, Leads or Users relating to either Contract, Case, Opportunity or Product objects. So what am I missing? What's the advantage of using a MassEmailMessage for sending out a batch of emails when the SingleEmailMessages have more options? Single and Mass emails have separate limits, but they both have the same limit of 1,000 external email addresses per day.Īnd when it comes to using the ndEmail(), you have pass in an array of messages anyway, so why not send in an array of many Singles instead of an array of one Mass? Mass emails have very limited options for the setWhatIds. If you look at the documentation, Singles have far more options available when it comes object types that can be used in the setWhatId methods, especially since they can accept Custom objects. I'm scoping out a project that will involve sending outbound email messages, and I'm a little confused about why one would use a MassEmailMessage instead of multiple SingleEmailMessages.
