Article
Declarative Deal Registration Tips & Tricks
learnexperiencecloud.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Step 3:Create a process using Process Builder to do the following: “Add the user in the Partner Sales Contact field to the Opportunity Team upon creation of the Opportunity” Approval Notifications
Registering A Deal: The partner registers a deal, which is typically automatically submitted for approval. An internal user or group of users will vet the deal registration, then approve or reject it. “If approved, someone internal will convert it over to an account/contact/opportunity and in the process, will assign an internal salesperson to be the opportunity owner if co-selling alongside the partner.” Approval Notifications: Once approved, notify the partner if it is rejected or approved.
An easy way to achieve this is to use Process Builder to add the partner salesperson to the Opportunity Team at the time of Opportunity creation. To know which partner user to add, you can create a Partner Sales Contact field on the Lead when the deal is registered, map that over to a similarly named field on the Opportunity and use that to set the user when you create an Opportunity Team Member in Process Builder. “Create a user lookup field, let’s call it Partner Sales Contact, on the lead and opportunity objects, and map the lead field to the opportunity field so the value carries over during the lead conversion process.” Step 2:If you use a Global Action for the deal reg form, you can set a predefined field value for Partner Sales Contact by mapping the running user’s record ID into the field. Note: if your partners have a deal registration desk and register deals on behalf of other users, rather that setting this value automatically, you can put the Partner Sales Contact field on the Global Action layout for the Deal Registration Desk user to populate manually.
If a deal is approved, you’ll convert it over to an opportunity (with its own record type for the same reasons you do so on the lead object) so it will appear in your sales pipeline and you can report on your direct and indirect sales pipeline side-by-side. “The partner registers a deal, which is typically automatically submitted for approval.” Converting to An Opportunity: If approved, someone internal will convert it over to an account/contact/opportunity and in the process, will assign an internal salesperson to be the opportunity owner if co-selling alongside the partner. If assigning to an internal salesperson, partners need the ability to view or edit approved Deal Registrations (i.e. Opportunities) owned by internal sales users.
If a deal is approved, you’ll convert it over to an opportunity (with its own record type for the same reasons you do so on the lead object) so it will appear in your sales pipeline and you can report on your direct and indirect sales pipeline side-by-side. “An internal user or group of users will vet the deal registration, then approve or reject it.” Converting to An Opportunity: If approved, someone internal will convert it over to an account/contact/opportunity and in the process, will assign an internal salesperson to be the opportunity owner if co-selling alongside the partner. If assigning to an internal salesperson, partners need the ability to view or edit approved Deal Registrations (i.e. Opportunities) owned by internal sales users.
Unapproved deals are created as leads. These leads have their own Deal Registration record type, so that you can use custom page layouts with fields specific to deal registration, identify the proper lead statuses that fit your deal registration process, and easily separate them from your direct sales leads. “If a deal is rejected, you’ll leave it as a lead. This is just like when a direct sales lead is disqualified, you don’t convert it.” If a deal is approved, you’ll convert it over to an opportunity (with its own record type for the same reasons you do so on the lead object) so it will appear in your sales pipeline and you can report on your direct and indirect sales pipeline side-by-side.
If a deal is rejected, you’ll leave it as a lead. This is just like when a direct sales lead is disqualified, you don’t convert it. “If a deal is approved, you’ll convert it over to an opportunity (with its own record type for the same reasons you do so on the lead object) so it will appear in your sales pipeline and you can report on your direct and indirect sales pipeline side-by-side.” Registering A Deal: The partner registers a deal, which is typically automatically submitted for approval. An internal user or group of users will vet the deal registration, then approve or reject it.
Registering A Deal: The partner registers a deal, which is typically automatically submitted for approval. An internal user or group of users will vet the deal registration, then approve or reject it. “If approved, someone internal will convert it over to an account/contact/opportunity and in the process, will assign an internal salesperson to be the opportunity owner if co-selling alongside the partner.” Approval Notifications: Once approved, notify the partner if it is rejected or approved.
Registering A Deal: The partner registers a deal, which is typically automatically submitted for approval. An internal user or group of users will vet the deal registration, then approve or reject it. “If assigning to an internal salesperson, partners need the ability to view or edit approved Deal Registrations (i.e. Opportunities) owned by internal sales users.” Approval Notifications: Once approved, notify the partner if it is rejected or approved.
Before reading this, I assume you’ve read the Guided Setup for Deal Registration instructions and understand the following concepts: “Unapproved deals are created as leads.” If a deal is rejected, you’ll leave it as a lead. This is just like when a direct sales lead is disqualified, you don’t convert it.
Approval Notifications “However, to notify a partner that a deal registration is approved, I prefer to send it using a process when the Opportunity is created instead of exiting the lead approval process, so that you can include a direct link to the Opportunity in the partner portal.” Expiration Notifications
Converting to An Opportunity “To know which partner user to add, you can create a Partner Sales Contact field on the Lead when the deal is registered, map that over to a similarly named field on the Opportunity and use that to set the user when you create an Opportunity Team Member in Process Builder.” Step 1:Create a user lookup field, let’s call it Partner Sales Contact, on the lead and opportunity objects, and map the lead field to the opportunity field so the value carries over during the lead conversion process.