Sending Mass Emails From Salesforce

  • Create a Email Template
Email Description Field

 Then you either go to the Lead Tab or the Contact Tab and scroll down the page until you see the Mass Email link in the Tools section.
Mass Email Link on Leads Tab
On the first step of the mass email wizard is to create your target list. To do this you have the option of leveraging an existing View that is available on the Leads tab, or you can create a new View from within the wizard. In this example we will create our target list from within the wizard by clicking the Create New View link.
Step One - Create Your View
In my example I’m creating a quick View to grab any Lead that is in the State of California. Notice in Step 2 of the View you can use a Campaign to filter (handy if your Campaign has your target list as Campaign Members!). Remember you have governor limits based on your edition (see paragraph two of this blog posts).
Create Lead View Step 1
If you’re running Professional Edition for example, and your View pulls more than 250 records, you’ll need to add additional filters to your View to reduce the number of results (for example, Last Name starts with "A,B,C,D,E,F"). Notice that I’ve got a few Leads with the same email address. Like I mentioned before, Salesforce does not "de-dupe" or send based on unique email addresses. That email address is going to get four emails if they remain selected. You can use the checkboxes to the right to exclude any records from your View. Then we can click the "Next" button and proceed to step two of the mass email wizard.
Exclude some emails from list
In step two you will navigate to the email folder that has your email, select it, then click "Next."
Step 2 - Pick Your Email Template
In step three you’ll see at the top how many people will receive the mass email. In the Processing Options section you’ll see two checkboxes. The first is to receive a copy of one of the emails (so you know it got sent and how it looked). The second is to tell Salesforce to log a completed activity that a mass email was sent. The Mass Email Namefield just below that is NOT the name used when the activity is logged, but rather the identifier when you look at your mass email queued up in Setup > Administration Setup > Monitoring > Mass Emails.
Monitoring Mass Emails
In the last section, Delivery Options, you have the option to schedule the email or send it right now. If you schedule it for the future, you’ll get an email from Salesforce letting you know when you mass email was sent, and you can monitor it from the aforementioned queue.
Step 3 - Schedule Email for Delivery
If you click "Send," Step 4 of the wizard is simply a confirmation page.
Step 4 - Finished

Comments

Post a Comment

Popular posts from this blog

Approval Process

Image
Salesforce: Approval Process - Who can approve ? To build an approval workflow in Salesforce is simple, since Salesforce provide  Approval Processes . You can find this under  Setup  -  Create  -  Workflow & Approvals  -  Approval Processes . In early blogs, we have discussed about  Serial and Parallel Approval  in Salesforce, in this blog, we would like to discuss in depth option of users can approve? Manager Approval In the approval process  Step 3. Specify Approver Field and Record Editability Properties , there is option to determine next automated approver. Notice that  Next Automated Approver Determined By  is not a mandatory field here. Option available here: Manager   - a standard field in user object and has no relation with Role Hierarchy All custom fields in user object with type = Hierarchy - in above sample: Boss and Sales Director. If you select  Manager  as in above screenshot, when you set up Approval Step, in  Step 3. Select Assigned Approv
Read more

Spring Batch 2.0 -Basic Concepts

There is always a healthy debate when talking Java and batches. When I heard  Spring Batch , I had to try it out.  On a previous project, many eons back, I did some batch processing in Java. What hurt me there (after a lots of optimizations) was a call to another persons module. His module happily loaded up an entity bean. You can guess where that ended. Next release I went through the code and replaced the entity bean calls with ONE update SQL statement. That fixed things. I was processing 200k records in 15-20 minutes, with an extremely small memory footprint. Even this I could reduce further if I tuned another module. But the performance was deemed enough and we moved on. What I personally felt from that experience was the need of a decent Java-based Batch processing framework. Of course having this does not mean use Java for batches. Sometimes for bulk processing doing it in the database may be the right approach. In this blog I want to go over Spring Batch processing. We wi
Read more