Set Up Product Discovery in Revenue Cloud for Communications
To use product discovery in Revenue Cloud for Communications, configure the product
discovery settings. Sales reps can then select a catalog and browse its products for assignment
to specific locations.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer
Editions with Revenue Cloud for Communications
User Permissions Needed
To set up Product Discovery:
Product Discovery Admin
To update custom flow for browsing and adding products:
Revenue Cloud for Communications Features
OR
CME Sales
Features
Important If you've implemented the product discovery configuration before
Spring `26, we recommend that use the new product discovery flow and context definitions,
the Multi-Recipient: Discover Products flow and
MultiRecipientProductDiscovery context definitions. The
Comms Product Discovery flow and
CommsProductDiscoveryContext are scheduled for depreciation in
Spring `27.
Here are some of the considerations for product discovery:
While the Let users configure products property in the Product Discovery component properties is set to
Yes by default, this setting is not supported for
recipients.
To configure Context Product Discovery Setting, use the same context definition in
Product Discovery Setting, Pricing Procedure, and Qualification Procedure.
From Setup, in the Quick Find box, enter Product Discovery
Settings and select it.
Update the context definition to MultiRecipientProductDiscovery.
If you have extended the default context definition, choose the extended context
definition.
Update the pricing procedure to the extended product discovery pricing procedure.
Update the custom flow for browsing and adding products in Revenue Cloud to
Multi-Recipient: Discover Products.
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
Always Active
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
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
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.