Skip to main content

#Sales Cloud169 人がディスカッション中

I implemented a Salesforce automation to simplify how we handle duplicate Prospect and Customer Accounts. Sharing the approach in case it helps other Salesforce Admins facing a similar scenario.

🔹 The Business Problem

In our process:

  • Sellers manually create Prospect Accounts in Salesforce.
  • Once a prospect becomes a customer, the Customer Account is automatically created in Salesforce through an integration with another system.
  • The original Prospect Account remains in Salesforce.
  • This can result in a Prospect Account and Customer Account representing the same company i.e, duplicate accounts.

Previously, sellers had to identify these duplicates and submit a ticket manually so an Admin could merge the records.

🔹 The Solution

I built an automation that follows this process:

Duplicate identified → Prospect Account flagged → Duplicate Account button + bell notification displayed → Seller clicks the button → Email sent to Service/Admin team → Admin reviews and merges the accounts

🔹 Implementation Steps

1. Create the Matching Rule and Duplicate Rule : A Matching Rule and Duplicate Rule to identify a Prospect Account and Customer Account as duplicates based on our internally defined matching criteria.

2. Create a Record-Triggered Flow: Record-Triggered Flow that runs when a Duplicate Record Set is created or updated.

Within the Flow:

  • Get Duplicate Record Items: Retrieve the Duplicate Record Items associated with the Duplicate Record Set.
  • Loop Through Duplicate Record Items: Loop through the Duplicate Record Items and assign the relevant Account/Company Name to a Flow variable.
  • Find the Matching Account: After the loop, use Get Records on the Account object to find the corresponding Account based on the Account/Company Name stored in the Flow variable.
  • Flag the Prospect Account: When the matching Account is found, update the Prospect Account and set our custom Duplicate Account checkbox field to True.

3. Display the Duplicate Account Button + Bell Notification: Duplicate Account button/action to the Account Lightning Record Page and configured Conditional Visibility based on the Duplicate Account checkbox.

When the checkbox is set to True, the seller sees the Duplicate Account button along with a bell notification. This gives the seller an immediate indication that Salesforce has identified the Account as a duplicate and that the records need to be reviewed/merged.

4. Notify the Admin Team: When the seller clicks the Duplicate Account button, an email is automatically sent to our ticketing system and Admin reviews and merges both Prospect and Customer accounts.

Here are screenshots of the flow:  

  #Salesforce Admin #Flow #Sales Cloud

I implemented a Salesforce automation to simplify how we handle duplicate Prospect and Customer Accounts. Sharing the approach in case it helps other Salesforce Admins facing a similar scenario.

 

Flow 2.png

 

Flow 3.png

2 件のコメント
0/9000

Progress looks different every day, but showing up always counts. ✨🚀

#Trailhead #Sales Cloud
0/9000

Hi, We're working on sending offline conversions from Sales Cloud to Google Ads. I've been tasked with researching best practice so I'm hoping someone out there has done this in a way that works well.    Specifically, I'm wondering how you have gone about populating the GCLID in Salesforce and assigning it to Opportunities.   1. If someone clicks multiple ads do you retain multiple GCLIDs or overwrite the existing GCLID?  2. If a user clicks an ad and there is no immediate conversion, but a conversion occurs 6 weeks later from a non-Google campaign, do you assign the GCLID to the Opportunity or do you only assign to opportunities that result directly from a click?  3. Do you associate GCLIDs with specific campaign members or with contacts generally?    I have my own thoughts on this but have been asked to research best practice, so any feedback as to how other businesses handle this would be much appreciated.    FYI we intend to use opportunity created, opportunity stage changes to 'Sale Recorded' and opportunity stage changes to 'Sale Complete' as conversions. We use Sales Cloud (we don't have Account Engagement or Marketing Cloud).    Thanks!     

 

@* Sales Cloud - Best Practices *  @* Sales Cloud - Getting Started * 

3 件の回答
  1. 8月27日 19:30

     I’d keep the GCLID history tied to the lead/contact and carry the relevant one to the Opportunity. For multiple clicks, keeping the history can make attribution much easier later. 

0/9000

Hi Salesforce Community,

I am working with Tamas Society, an Indian nonprofit organisation. We have received Salesforce Enterprise Edition (10 donated users) through the Salesforce nonprofit programme.

We want to integrate WhatsApp with Salesforce so that we can:

  1.  Capture WhatsApp enquiries as Salesforce Leads/Contacts. 
  2.  Maintain the WhatsApp conversation against the Lead/Contact record. 
  3.  Automatically assign enquiries to the appropriate team member. 
  4.  Send automated/approved WhatsApp messages from Salesforce. 
  5.  Eventually connect WhatsApp enquiries to our Sales/Export pipeline. 

My question: Does our donated Salesforce Enterprise license include the required Messaging / Digital Engagement / WhatsApp functionality, or do we need an additional Salesforce product/license?

If an additional product is required, are there any free or discounted nonprofit options available through the Salesforce nonprofit programme?

I would particularly appreciate guidance on the exact setup path and any additional licenses/entitlements we should request.

Thank you. 

 

#Sales Cloud

0/9000

When exactly is an Opportunity Product created (in regular Sales Cloud)?  Is it when you select/click on the Product in the add Product window or is it when you click Save?   

 

Reason why I'm asking is because we created a custom Discount field that works with a Flow which shows the Discount Amount if the Sales Price (API Name Unit Price) is different from the List Price.  HOWEVER, the field only updates after you click Save (saving it to the Opportunity), then Edit, and then Save again.  I was thinking when I did a Fast Field Update (before Save), the Discount field would quickly calculate when you enter a Sales Price.  But it does not.  The User needs to go in, edit the Sales Price, then the Flow is triggered, clicks Save, and Discount is calculated.   

 

So, does that mean the Opportunity Product is only created after selecting the Product and clicking Save?  Is this because the Opportunity Product is a junction object?  I understand there's CPQ and now Revenue Cloud, but need to get the simple things first and trying to reduce clicks.  Let me know what you know or what you're done in the past.  Thanks! 

3 件の回答
  1. 1月19日 9:56

    Hi @Don Spire

     

     

    An Opportunity Product is created only when you click Save. Selecting a product or entering the Sales Price does not create the record. Since it’s a junction object, before-save logic can’t run until the record exists, which is why the calculation happens only after saving

0/9000

Hi,

 

We are trying to figure out an option that would enable our sales users to send emails to their lists with a pre-built HTML email. Is it possible through sales engagement? How can we execute this?

@* Sales Cloud - Best Practices * 

3 件の回答
  1. 8月25日 19:21

    Hey, you can do this with List Emails in Sales Engagement. Just select your list, choose the HTML template you’ve already built, and send it out from there. Works pretty well for bulk sends to contacts or leads. Let me know if you run into any issues setting it up. 

0/9000

I have been a SFDC since 1999 and have successfully completed multiple Org Swaps for clients that were backed into corners due to poor implementations or layers of Scar Tissue.    

 

In 27 years I have never had an AE forced the client to purchase more than 1 license (of equal level (EE, UE) to provision the new Org.    I have a situation now where a Non Profit Client (On UE NPSP) is being told by AE and his VP that the only way they will support an Org Swap is for the client to purchase 10 additional UE Sales Cloud Licenses in order for Ops to Provision the New Org.   

 

Is this the new Policy at SFDC?    In June, I just completed an Org Swap for another Non Profit and they had no similar requirement.    

 

Looking for other consultants, Partners, or SFDC folks to weigh in here.   Thanks 

 

#Nonprofit   

0/9000
3 件の回答
  1. 8月24日 9:43

    I passed my Salesforce Admin certification by focusing heavily on Trailhead and hands-on practice.  For additional practice questions and mock tests, I also used MyCertsHub, which helped me understand the exam format better.  For discounts, I’d recommend checking official Salesforce promotions and Trailhead events since voucher offers can change.

0/9000

Some of our opportunities were accidentally changed to a different owner and they need to be changed back but some of these users are now inactive.  Is there a way to update the owner to an inactive user?

3 件の回答
0/9000

Hello everyone,

 

I have integrated SharePoint with Salesforce using 

File Connect. Currently, we are using only one SharePoint site, but now we would like to add one or two more SharePoint sites to Salesforce Files.

Should we follow the same process for adding additional SharePoint sites, or is there any other configuration required?

What would be the recommended approach to achieve this? 

 

Thank you in advance for your guidance and suggestions!  

 

#Salesforce Developer #Sales Cloud #Salesforce Admin

2 件の回答
  1. 8月20日 18:51

    Hi Pranav - yes, you can add the extra sites, and the pattern is one External Data Source per SharePoint site rather than reconfiguring the existing one. 

     

    For each new site: 

    1. Setup - External Data Sources - New. Type: 'Files Connect: Microsoft SharePoint Online'. Set the Site URL to that site collection's URL (a sub-site collection URL works too). 

    2. Reuse your existing Authentication Provider - if the new sites are in the same Microsoft 365 tenant you do not need a new Azure AD app, just select the same Auth Provider in the lookup. (A different tenant would need its own Auth Provider.) OAuth is the only supported auth for SharePoint Online. 

    3. Pick the Identity Type per data source: Named Principal (one shared service credential for everyone) or Per User (each user authenticates and inherits their own SharePoint permissions). 

    4. Grant access: add each new External Data Source to the relevant Permission Sets/Profiles so users can see it. 

    5. Save, then validate/sync - users will see the new site alongside the existing one under External sources in Files and can attach from it. 

     

    So it is the same overall process, just a new External Data Source per site, sharing the Auth Provider wherever the tenant is the same. 

     

    If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

0/9000