What triggers automating lead conversion?+
The team defines the criteria. Common triggers include lead score crossing a threshold, specific behaviours like multiple visits or demo requests, source plus engagement combinations, or qualified replies to outbound campaigns.
Will this override our existing qualification process?+
No. The workflow runs the qualification logic the team agrees on, so if the criteria are not met, the lead stays a lead. Automation replaces the manual click, not the qualification judgment.
How does the converted opportunity get routed to the right rep?+
Routing logic considers territory, availability, expertise, and workload balance. Converted opportunities are handed off in the same step, so the rep picks up a record ready to work.
Does this require Apex or a developer?+
No. Conversion rules are configured declaratively in Salesforce setup, so sales ops or admins can build, adjust, and version them without engineering involvement.
Can we still convert leads manually if we want to?+
Yes. Automation handles the leads that match defined criteria; anything that does not match flows into the regular manual path. Teams typically automate the high-volume cases and leave edge cases for human review.
How does this work with multi-step qualification, like BDR to AE handoff?+
The workflow can be staged. A first step converts MQLs to qualified leads for BDR review; a second step converts qualified leads to opportunities once BDR criteria are met.
Can we use our own LLM provider?+
Yes. Bring-your-own-LLM is supported, so teams running an OpenAI, Anthropic, or Google enterprise contract route AI calls through their own provider, with costs and audit trails on their own bill.
Is conversion data available in standard Salesforce reporting?+
Yes. Every conversion is logged in Salesforce against the originating record with the criteria, the routing decision, and the timestamp, so standard reports pick it up automatically.