Lead routing using Flows: a technical guide (Part 3)

We're continuing on with the custom lead routing setup. Remember, you would build something like this if you're choosing to build instead of buy. More often than not, you’re going to want to buy a solution. Reconfiguring your setup with a purchased solution is going to be much, much easier than going back and paying down your technical debt.

Also, there’s a reason why there’s a term called bells and whistles. We’re not building any bells and whistles here.

But we are saving you between $15K to $50K for the next few months.

So let’s keep bootstrapping with part 3.

Last time we ended with a Decision element. This element searched for accounts with a Get Records element. Then we counted how many records were in the collection that was found. If it’s zero, we execute the default outcome. If it’s one or more, then we need to start looping through the records.

I’m assuming you have a clean database. What I mean by this is that you do not have any duplicate website records in your Salesforce instance. You can accomplish this by creating a scheduled based auto flow which scans for duplicate accounts and merges them. An alternative would be to go get a deduping software. Here are my favorites over the years:

1. RingLead

2. Cloudingo

3. Validity

4. Openprise

I also advise Syncari and they could definitely help you here.

Anyways, enough vendor talk. We’re trying to avoid a vendor with this Flow. So in the spirit of building let’s continue on.

Create a Loop