Campaign should have Person Owner as Sender - Duplication required for 600+ sales reps
I was a user of Salesforce for 14 years for another company prior to switching to Pipedrive. We had over 600 sales reps and each was responsible for handling their own book of business and communications, but all contacts were collectively stored and managed in one CRM (Salesforce). Our umbrella company had a marketing team that would create amazing, branded collateral and send email campaigns twice a month on each sales rep's behalf to all Salesforce contacts that were tagged accordingly. The contact owner's email was used as the sender address and our individual email signatures were used as a merge tag in each email.
It was amazing and the marketing team made me and all of our sales reps look like super rockstars to prospects and customers. It also supported a cohesive branding effort on behalf of all the sales reps and the umbrella company. We even had one of the city's highest ratings for company retention among sales reps.
With my new company, we are taking on a similar structure for our outbound marketing correspondence and branding efforts on behalf of our growing sales team. However, when I create campaigns in Pipedrive on behalf of my brand and growing sales team, I have to duplicate that campaign, change the email signature to the corresponding sales rep, and select each sales rep's email as the sender.
What are the chances the Pipedrive team would look into this?
I have a feeling that having a "Person Owner Email" as an option to select in the Campaign Sender field, as well as a merge tag for the user's email signature, would be a time saver and life changer for everyone in the world who sends campaigns on behalf of multiple team members or employees!
Comments
-
Hey, @MichaelATX!
Campaigns and Emails in Pipedrive are indeed sent from the account and email address associated with the user who is logged in and creating the campaign, and this is the only possibility for now. However, there are a few workarounds and configurations that might achieve similar results:
- Shared Mailbox (might not be suitable, but still worth mentioning): Using a shared email address for sending emails. If the team has a shared mailbox that multiple users can access, they can be sent from this shared email address.
- Email Integration: Integrate an email service provider (ESP) that allows sending emails from different email addresses. Tools like Mailchimp or Sendinblue integrated with Pipedrive can be configured to send emails from different addresses, provided they have the appropriate permissions.
- Custom Solutions: Developing a custom solution using Pipedrive's API. In order to send emails on behalf of other users, a developer could use the API to create a custom integration that allows for this functionality.
That said, I will forward the suggestion internally so that it can be considered in future improvements.
Thank you!
0