Has anyone tried multiple automated round robins in SFDC or Marketo based on Lead Source / Campaign? Possible? What solutions are there?
Thanks for the help!
Marketo is not very good at that. The closest it can to on round robin is in fact using a random distribution. See Distribute Your Leads Round Robin or RandomlyYou can use the technique described in this post to create separate smart campaign that will manage the round robins for each of your lead source.
We have a developed a while ago a round robin system in SFDC, but it was quite some work. All the more so as you will soon be requested to have it resilient when a sales rep is on PTO or sick, or to handle various times in the day and days in the week.
And how come Marketo isn't ideal for this, Greg? Is it the time delay?
For the Salesforce route, did you use an app for that? Can't do multiple round robins with SFDC standard LARs, right?
Marketo is not ideal because, there is no capability to remember to whom lead A was assigned so that we can compute to whom lead B should be assigned. And basically, in a round robin, "memory" of what was done previously is a key component. You could do this with a webhook calling a webservice, and the webservice would compute the assignment, then return it to Marketo.
Yes, you are right, SFDC LAR's will not do it either, for roughly the same reason.
In SFDC, we had to create a custom dev. 3 years ago, there was no appropriate app in the appexchange, but that was 3 years ago, so you might want to give a look.
Actually, "Random Sample" as a flow step choice DOES have "memory" when the smart campaign is set up as triggered smart campaign. See my most recent comment on this thread: Re: Using Marketo to Round-Robin Assign Leads & Contacts to BDRs. The "memory" sticks with an individual flow step.
For your particular situation, you'll just want to create separate smart campaigns, each with its own flow step of "Assign lead owner" and the choices using "Random Sample" criteria that's generally even. Imagine that the number starts at 0 and then counts up to 100, where it restarts back at 0.
Edward Unthank | Founder, Etumos
We use Distribution Engine for our routing. One of the reasons we went with them was b/c of the Round Robin piece. Now, however, we are going to be changing to LeanData b/c of their added ABM and dedupe functionality.
One of Distribution Engine's downsides is that they don't deal with Named Account assignments very well b/c you can't copy and paste a list of Company Names, Email Domains, or website addresses into a field; you have to separate each by a comma and then it's hard to update later b/c you have to scroll and scroll to the right of the field if you're data entry isn't at the beginning. For this reason, we do our Named Account routing in Marketo and all territory and Round Robin routing in SFDC with Distribution Engine.