Is it possible to re-assign a lead in a flow step after the Marketo and CRM sync has occured.

[Anonymous]

Here is an example scenario of a problem that I am encountering and wondering if anyone has suggestions:

1. John Smith comes to our website and fills out a form with his basic information (first name, last name, email)
2. John Smith gets synced to our Salesforce and gets assigned to Inside Sales
3. The next day John Smith comes back to our website and fills out a progresssive profile form and we capture his company's employee and revenue range. Because the ranges that he provided fit within the ideal prospect of our company, we want to mark the lead as SQL and reassign John Smith to an outside rep.
4. Is it possible to re-assign John Smith thru a flow step in Marketo after the lead has already been created and assigned intially? All my assignment rules in SFDC work, but I cannot seem to get Marketo to reassign the lead twice.

Anyone have any suggestions? Attached are some pictures that show my Marketo Logic.

SMART LIST:

FLOW:

Thanks - Taylor
 

[Anonymous]

Hey Taylor,

You can re-assign. The ideal situation, which I believe I heard you can do but cannot find out how, is un-assign a Lead so that they are a free agent and re-run them through your auto-assignment rules. I would ask support how to do that. Then your flow would be un-assign, then sync to SFDC using the Auto-Assignement rules that take into consideration Revenue and Company size, right?

The much longer version is you could create a trigger campaign that looks at those fields (Revenue and Employees) whenever they are updated. Then, in your flow, you can add the Change Owner flow step and use the contstraints to act like the assignment rules. For example, if you do things geographically, If: State is: CA, AZ, NV, Owner Name: Taylor M. Obviously, the down side to this is that you have to break it down per rep and update if anyone joins/leaves the company manually.

I am pretty sure you can strip a lead of it's acquisition, but I would ask support. In the meantime, I will create a discussion about it to see if anyone else knows because this is bugging me.

[Anonymous]

Taylor

How do your current SQL assignments work? Is it a large team? Round robin?

If so, you can add options to the assign step that allow the lead to be assigned to a specific person based on certain criteria.

[Anonymous]

Taylor

Did you check to see whether the lead can run through the flow more than once? That little gotcha has hindered us a few times.

[Anonymous]

@Jeff @Caleb - Our assignment rules are territorial, but it is divided up based on area code - which would be very tricky to set up in Marketo. For example,California itself is divided up between 4 sales reps based on area codes. We also have some international reps that have assignment rules that are Postal Code based. Kinda messy! It sounds like there isnt a clear cut way to do this, but I am going to start off by seeing if I can strip a lead of its owner and see if I can reassign after. When I talked to support they were pretty confident it would work using the steps that I had in place (which I posted), but I havent been able to get it functioning.

@MikedTurner - that has gotten me too, but I check and double checked to make sure it could run thru more than once.

[Anonymous]

Hey Taylor,

I have been told you cannot strip the Lead of ownership, just switch to a queue, or anther Rep. I am following up on if you can then run the Lead through the rules again and have them apply. I'll let you know what I hear.

[Anonymous]

@Jeff

Thanks for the follow up - I look forward to hearing what you find out!

Thanks,
Taylor

[Anonymous]

Any word on how this was finally accomplished?

[Anonymous · Accepted solution]

I never heard back, but I have found that if you delete the Lead from SFDC, then re-sync via the auto-assigment rules, this has worked. 

[Anonymous]

You can only reassign a lead if you specify who that lead owner will be. You cannot strip the ownership and then reassign a lead based on your active CRM assignment rules.

Thanks,
Taylor