Lead conversion in Salesforce is the set of steps a sales rep takes to engage with his prospect when there’s a potential business opportunity.
When you convert a Lead, Salesforce creates an Account, Contact, and optionally an Opportunity, using information from the Lead you’re converting.
This process is usually made manually in Salesforce, and this is where Chili Piper comes in to help automate it and reduce manual effort.
Let's cover this feature in more detail below:
1 - While creating or updating your Distro CRM Flow and adding a new node, you'll see the "Lead Conversion" option:
2 - Once the node is added, you'll see multiple options in the side panel.
First of all, it's important to mention that we’ll prioritize an existing Account in Salesforce if it exists using Distro's Lead to Account Matching Settings to evaluate which Account we should match with.
The scenario mentioned above will not happen If the setting to always create an Account is enabled.
We'll cover each setting, including the one we just mentioned, separately below:
Here you can select what’s the Lead Status that’s converting the Lead. In Salesforce, multiple Lead Status can be the ones that trigger the conversion.
In Salesforce, select the Lead Status(es) to be used and enable them to be used in Distro:
Create an Opportunity
Creating an Opportunity during the Lead Conversion is an optional setting. If enabled, the name of the Opportunity will be the name of the Account Name.
Create an Account
This is also an optional setting, that will always create a new Account in Salesforce for each conversion. If this one is enabled, we'll not check if an Account already has Contacts from the same domain and also run your Lead to Account Matching Settings, we'll always create a new Account.
The new Account Name will have the Company Name filled out on the Lead Record.
3 - When the configuration is done, the new node will be available on the Flow with the selected settings.
If you need to edit any of the node's settings, you can click on it and proceed from there. Note that updates are auto-saved:
When added to the route, the Lead Conversion automatically becomes the end of the Flow, as the Lead record after conversion doesn’t exist anymore since it became a Contact.
Any other tasks like Field(s) Update, SLAs, Assign & Update Ownership would need to be placed before the Lead Conversion node to work as they should.