Depending on business use cases, capturing product feedback shared by clients and linking it to Salesforce records is valuable. This article describes the steps to capture product feedback and link it with Lead records, then automatically carry that feedback forward to Opportunity records after Lead Conversion.
This article explains how to capture Product Demo Feedback shared by clients on Lead records, and automatically carry that feedback over to the resulting Opportunity after Lead Conversion, using a custom object and Lightning Flow automation.
Create a custom object with the label Product Demo Feedback. Keep the API name of the custom object the same as the default. Within this object, create a custom field that is a Rich Text Area labeled Feedback. This field should contain the product feedback.
Create a Lookup Relationship with Lead, with Product_Demo_Feedback__c being the child object and Lead being the parent object.
Create a Lookup Relationship with Opportunity, with Product_Demo_Feedback__c being the child object and Opportunity being the parent object.
Verify that your data model matches the example image below. Depending on your business use case, you may also need to link the Product Feedback object with the Product object.
Upon Lead Conversion, you can establish a new Account, a new Contact, and a new Opportunity. If the Lead already exists in the form of an Account or Contact, you can skip creating new Account and Contact records and instead associate them with the relevant existing records during the Lead Conversion process.
To associate the Product Feedback Records shared by the Lead with the Opportunity, use Salesforce's automation tool, Lightning Flows.
Salesforce offers various options for creating Lightning Flows, such as Screen Flow, Platform Event-Triggered Flow, and so on. For this use case, select Record-Triggered Flow.
The relevant new or existing Opportunity record is tagged to the Lead record using the standard field ConvertedOpportunityId on the Lead object.
Use the Update Records element in Flow Builder to update and tag the Product Feedback Records with the relevant Opportunity record.
Add a name and description for the Update Records element and set the conditions as below.
Provide a relevant name for the Flow and activate it.
Written by: Meghesh Shenoy | Forum Ambassador
Meghesh Shenoy is a MuleSoft Ambassador and a Salesforce Forum Ambassador. He is a MuleSoft and Salesforce Certified Developer, carrying the knowledge of building automation solutions using Salesforce and MuleSoft. Meghesh is passionate about sharing knowledge and experience and also helping others sharpen and grow their MuleSoft & Salesforce skills together.
Submissions reflect only the opinions of the user who made available the Submission and not the opinions of Salesforce, regardless of whether the user is affiliated with Salesforce, and may contain or constitute products, services, information, data, content and other materials made available by or on behalf of third parties ("Third Party Materials"). Salesforce neither controls nor endorses, nor is Salesforce responsible for, any Third Party Materials, including their accuracy, validity, timeliness, completeness, reliability, integrity, quality, legality, usefulness or safety, or any applicable intellectual property rights. Any Submissions made available through any message board or forum in response to posted questions, or that otherwise purports to answer any questions, including any questions about Salesforce or Programs, are made available for your general knowledge only and should never be relied upon as answers to your specific questions (even if an answer is marked as a "best" answer or with any similar qualifications). You should always contact Salesforce support for answers to your specific questions. Salesforce has no control over Submissions, and is not responsible for any use or misuse (including any distribution) by any third party of Submissions.
If you have questions, tap into the wisdom of our entire Trailblazer Community here: https://trailhead.salesforce.com/trailblazer-community/feed
002575857

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.