#Leads2 diskutieren mit

Hi @Teri Curtin great question. For us it is important that a new lead is created even if it is an existing customer, because he/she could be then ready to buy, for example to request a quote of a different product he/she was not buying before.  So from business perspective it is important to track the new lead. You could use a different sales org and org id perhaps to make sure that you still get the lead. 

You're awesome @Dodi Friedenberg! Of course, I've known that since 2017 at JVS!

A couple notes:

1. Users must also have R/E to the Title field. Since we don't use that, I hadn't previously granted access. But thanks to your Github link, I figured it out.
2. Users must have CR access to Opportunities in order for both the Opportunity Name field and the Do not create a new Opportunity upon conversion checkbox field on the conversion page to appear (Opportunity Account appears either way). Previously, those fields appeared regardless of the permissions. However, the conversion will still work without those permissions or the fields being visible. This is fine, as long as the NPSP Setting for Leads is set to the appropriate default. In my case, that's unchecked, which causes the Do not create a new Opportunity upon conversion checkbox field to be checked by default. Since we don't use Opportunities for Leads, it works out just fine that users suddenly don't see a couple fields that they never use. Less clutter is always better!

Hi, @Daniel Walker, does your Org have a Pardot license? If you happens to have Pardot Advanced edition and above you will have access to the OOTB Match Leads LWC. It will list related Leads on an Account page sidebar*, and notifies the user if there is a match between any Lead’s ‘Company’ field and the Account’s name. Users then can "screen" Leads that should be converted into Contacts on this Account. Reference here: https://www.salesforceben.com/salesforce-matched-leads-component-assign-leads-to-an-account/

If you don't have Pardot or the right edition, it's possible to build a custom LWC with Apex Controller for similar functions to pre-filter any potential linked Lead records to the Account record.

It sounds like you've got users who have this Permission

Documentation

Let Users View and Edit Converted Leads

If you remove/revoke the Permission from their Profile or Permission Set, you should be good to go 

Hi @Subramanian Ramakrishnan,

Thank you for the questions! I'm also tagging in @* Sales Cloud - Best Practices * for additional assistance. I'm also in the process of identifying a Salesblazer who can help us! 

We can enable 'History Tracking' and add the 'Lead History' Related List to the page layout.

Set up > Object Manager > Lead > Fields & Relationships > Set History Tracking > Enable Lead Tracking > Select the 'Lead Owner' field > Save

 Set up > Object Manager > Lead > Page Layouts > Lead Layout > Related Lists > Drag and drop 'Lead History' > Save.

@Junie ElieElie

It's great news. Glad was to help you. 

You can mark my helpful answer as a "Accepted Answer" it's similar to "Best Answer". 

Here are approache to manage multiple emails for leads in Salesforce, preventing duplicate leads and ensuring all contact information is captured:

Utilize Duplicate Management Rules and Merge Function

1. Adjust Duplicate Rules: Modify your existing duplicate rules to allow leads with the same name but different emails.
2. Merge Duplicates: After multiple leads are created with the same name and different emails, use the Merge Leads feature. This allows you to combine these leads into a single record, preserving all associated information like emails.
3. Workflow Automation: Consider creating a workflow that automatically merges duplicate leads based on specific criteria (e.g., name and email combination).

Yeah, I think that's the issue:  The "Team Members" no longer own the Leads, and there is no Lead equivalent to the Case Lifecycle Report, where you can track ownership hand-offs throughout the life of the Lead (which would be nice)

Hey @Ken Huelskamp, you can create a record triggered flow on email message object to check for the email and then update the status on the Lead record.

Here is the article providing an example usecase of how to use email message trigger:

https://help.salesforce.com/s/articleView?id=000393845&type=1

You can reference this article to create your own flow and utilize the Subject as a filter criteria as your email template has a static text.