Understanding Vertical Response and Salesforce
At ONE/Northwest we’ve been looking into Vertical Response (VR) as an emailing solution that is integrated with Salesforce.com. We’ve just completed our first implementations, and I wanted to share what we’ve learned about how VR behaves with Salesforce. I’m going to try to lay out what I know in as concise terms as possible. Some of this is already known to many of you, but it was surprisingly hard for me to get my head around. When I get something wrong please comment on this post and I’ll update as necessary!
First, VR for Salesforce.com is best thought of as an individual Salesforce user’s personal application for sending mass emails rather than a shared solution for an organization. Here’s why I say that:
- Each Salesforce.com user has their own VR account, and it is impossible for those accounts to share lists
- If one person starts a send, someone else can’t complete it
- If one person sends an email, they are the ones who will need to pull the stats back to Salesforce
- If a subscriber opts out, they are globally opted out of emails in Salesforce
Now that I’ve said that, let me say that VR accounts can share some important info:
- By creating your email Templates as Email Templates in Salesforce.com, they are available to all Salesforce/VR users.
- Salesforce Campaigns can be used to represent each send, and the stats get pulled back to them, so those are visible to all Salesforce/VR users. They can even be used for segmentation of future sends.
- You can pool send credits ($) between any number of users, you just have to email VR and tell them which users.
