If it is appropriate then set an activity for every email message that is sent out. Don’t forget to BCC yourself just to check out how it looks. The best idea is to choose the email templates from the existing ones that are stored in Salesforce or you can create a new one that suits your business the most. In the first step, when the list of the recipients is final, you need to design an email template. For this purpose, you can use a command to automated the task or simply go through the complete list and remove the people you are not interested in. Here, you will filter the contacts that you actually want to send the email. Once you are sure of the type of recipient, you need to create people view. Some of the available recipient options include – Contacts, Leads, Person Accounts, and the Salesforce users. To take your business to the next-level, the most optimum choice is “ Salesforce Lightning” with interactive user-interface capabilities. You may either choose Salesforce Classic or Salesforce Lightning. You can start by deciding on the type of recipient you want to reach that depends on your business category and Salesforce utility you are working on. This is a perfect tool to send out emails to a selected number of addresses only, but you can extend the number of addresses if you know how to work with Salesforce mass email limit. 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.You probably know Salesforce comes with an attractive mass email solution. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |