Current User Signature - Sales Insight

[Anonymous]

Is there a way that we can setup our Marketo Sales Insight templates to pull in the Current User's signature regardless of which Contact/Lead we are working with? (Salesforce)

I've attempted using a formula field on the Contact object that pulled in the Current User's info ($User.__field__) but it appears that the information must be pulling from Marketo rather than Salesforce even when sending a Sales Insight email.

Thanks for any help.

[Eric_Salamon1]

Just curious couldn't you make a segmentation based on your sales team, and adjust the signature to display based on the segmentation using the snippets?

As far as I know Marketo can use segmentation and define the area with a snippet, replace snippet if criteria is met.

Please let me know if it isn't possible, because my understanding is that segmentation should allow the system to work that way.

[Sean_Richards]

I am looking to implement this same thing. Can you pretty please provide some insight into the solution? I want to have the signature be the person who initiated the Sales Insight email send?

[Casey_Grimes]

Hi Josh,

The good news: this actually has a solution—and one that I've deployed in the past for current users across multiple sales divisions.

The bad news: the solution is one that's a little more complex than what I can say in a Community post. Feel free to reach out to me and we'll chat on fixing the issue.

[Anonymous]

Courtney Grimes​

It appears that I can only message people that are following me.

[Anonymous]

Hi Josh and Courtney...any chance I could learn what you guys have done here?  I have a similar need where I want to pull into an email a token that displays the person that initiated the Sales Insight "Add to Campaign" feature...so the "current user" and not the lead or contact owner because they are not always the same.  I appreciate any insight and guidance!

-Chris

[Anonymous]

I would love to share with you Chris but unfortunately I have been left without.

I assume this information which was initially offered was later determined private for their company.  But my communication seems to be completely cut without explanation. 

[Casey_Grimes]

Hi Josh (and everyone else here),

Unfortunately I had to take a bit of a break from the Community due to client work (and I sincerely apologize for leaving you high and dry, Josh), but I am definitely available to talk on this particular issue—I recommend just directly emailing me at courtney@demandlab.com (mostly so it's forced to stay on my radar!) for this or anything else you want to discuss in terms of solutions. Thanks!

[Anonymous]

Sounds great!

I'll reach out to you later this week and maybe we can setup a call for the following week.

I appreciate the help.

Thank you

[Lauren_Aquilino]

Hey Josh, Can you share your workarounds? I am able to create lead owner tokened signatures, but have the same team-selling issues as you. When my larges sales team edits the templates by copying and pasting stuff in, they often break they code so badly and don't know how to get out of it.

[Anonymous]

I unfortunately don't have have anything great for a workaround.

For the majority of our email templates we have a rather generic signature block that doesn't make any reference to the individual sending the message.  We do however have a blank template free of any coding that allows our team the ability to send whatever message they would like.

[Anonymous]

Added this over into the Ideas section -

[Justin_Norris1]

Josh Hampleman​, this would be difficult because the MSI emails live in Marketo and the tokens are rendered there, so I don't think they have a concept of logged in user or access to SFDC merge fields in that way.

[Anonymous]

Agreed, but imagine the customization and dynamic ability your MSI emails would be able to have if you had that ability.

All Sales Insight users have information stored inside of Marketo so all that would really be needed is the ability to add some additional fields on the users inside of Marketo, they must link in some way.  Then we could reference the information that is stored inside the system itself rather than inside of SFDC.

Edit - May have confused MSI with the MSI Email Add-in for ease of functionality in my above statement.